You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Visual and workflow refresh: offering to contribute #263
I recently contributed zoom shortcuts to the desktop wrapper (#2647 on the main repo) and have been using Vikunja daily for a while now. I'd love to help with a visual and workflow pass on the Flutter app.
The app works well functionally, but the UI feels like it could use some love: tighter spacing, better visual hierarchy, smoother transitions, and small workflow improvements that make the day-to-day experience feel more polished.
Before I start prototyping or opening PRs, I wanted to check:
Is there an existing design direction or style guide the app is heading toward?
Are there specific screens or flows you'd most like to see improved?
Any constraints I should know about (Material 3 migration plans, accessibility targets, platform parity requirements)?
Happy to start small with a single screen or component to make sure we're aligned on direction before going wider.
Thanks!
Reacted by Leon
Reacted by RXTX4816, Jakob Hofer and Gustavo Furtado
Our strategy with the UI design of the app can be summed up as "there is no strategy". Improvements are most welcome!
I'm not as deep in the app development as in the web development in general, so the only constraint I would put up is that the app should be recognizable as "the Vikunja app" when it's used by someone who also uses the web app, but nothing more. As far as I understand app design in general, mobile is so different from desktop that you can't just use the same paradigms 1:1 anyway and need to adopt to the platform so there should be plenty of room to make it better.
Activity
kolaente commentedon Apr 22, 2026
Hey 👋
Our strategy with the UI design of the app can be summed up as "there is no strategy". Improvements are most welcome!
I'm not as deep in the app development as in the web development in general, so the only constraint I would put up is that the app should be recognizable as "the Vikunja app" when it's used by someone who also uses the web app, but nothing more. As far as I understand app design in general, mobile is so different from desktop that you can't just use the same paradigms 1:1 anyway and need to adopt to the platform so there should be plenty of room to make it better.