Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🎨 Redesign (ideas?) #183

Closed
muety opened this issue Apr 23, 2021 · 7 comments
Closed

🎨 Redesign (ideas?) #183

muety opened this issue Apr 23, 2021 · 7 comments
Milestone

Comments

@muety
Copy link
Owner

muety commented Apr 23, 2021

Any designers or creative devs here?

Sooner or later the web interface needs to be redesigned, especially as new features like #166, #173 and #182 are added. What I personally like about the current UI is the fact that's it's fairly minimalist. However, with these additional features, some kind of navigation and different views need to be introduced.

In principle, I like hakatime's user interface, but it looks somewhat too "standard" to me.

So my wishes regarding a new UI include:

  • Have some kind of navigation between different views
  • Still keep it as simple, stupid and minimalist as possible
  • Dark theme by default
  • No standard Bootstrap or Material UI look
  • Preferably realizable with nothing but Tailwind

If somebody has a cool idea for a new design, feel free to share your thoughts, mock-ups and links to other web apps that could serve as an inspiration! 🦄

@muety muety pinned this issue Apr 23, 2021
@muety muety changed the title Redesign (ideas?) 🎨 Redesign (ideas?) Apr 23, 2021
@MeerBiene
Copy link
Contributor

Maybe use the redesign as opportunity to seperate the coding stats backend and the web interface. I'd suggest going with something lightweight like svelte because it compiles a static "vanilla" webapp that can be serverd with any static file server like nginx.

@muety
Copy link
Owner Author

muety commented Apr 28, 2021

Fair point. I already considered turning Wakapi into a single-page application couple of times. However, this would make things more complex and would introduce quite a bit of development overhead at the interface between backend and frontend. I tend to more and more like the "traditional" approach of server-rendered web apps again – not least because of usually better performance – and only have separate backend and frontend (using tools like Vue or Svelte) if really needed.

@muety
Copy link
Owner Author

muety commented May 17, 2021

May also be inspired by https://codetime.datreks.com

@muety
Copy link
Owner Author

muety commented Jun 28, 2021

I kind of like the UI design of gohornet/hornet

image

@muety
Copy link
Owner Author

muety commented Sep 8, 2021

Definitely wanna go for tabler/tabler.

@MeerBiene
Copy link
Contributor

^ I approve this. If you happen to decide to rewrite the frontend as SPA (and with svelte) I'd be happy to help

@muety
Copy link
Owner Author

muety commented Sep 29, 2021

Another design inspiration from Pirsch Analytics:

image

@muety muety added this to the v2 milestone Oct 13, 2021
@muety muety closed this as completed Jan 3, 2022
@YC YC unpinned this issue Jan 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants