-
Notifications
You must be signed in to change notification settings - Fork 325
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
GUI refresh: share visual language used by other IPFS apps #273
Comments
Having one GUI that would enable us to reuse it across Extension, WebUI and Station would be fun. However, now I'm not sure how much viable it would be, probably we would end up with custom views anyway. That being said, improving the UX of WebUI, Station and IPFS-Companion should be one of the priorities as these applications will be the face of IPFS for many developers. @lidel if you would like, we can probably bring more people to help you with design and UX :) |
Yup, views will be different, but what I had in mind was to share "style" / "visual language", so that Browser Extension, WebUI and Station each "feels like a part of the same family". @diasdavid Hm.. are there plans to refresh UX of WebUI any time soon? |
Yes there are! :D News incoming soon (later this week) |
Forgive my ignorance: What are the latest proposed visual changes here? I've seen some mocks in issues and the PRs. Are there specific relevant, recent issues to cross-reference here? |
@cvan it is an ongoing effort :) Right now Style Guide and UI Kit are being fleshed out, some initial wireframing work is done for IPFS Desktop app (as it has more UI than this extension) etc. I would not expect any revolutionary changes in browser extension until that work is done, and even then it should be mostly a visual polish ✨ Some references:
|
Closing in favor of ipfs/ipfs-gui#29 - thanks! |
There was a talk some time ago about using the same UI style as in ipfs/station.
Before we start work toward that goal, lets do a quick poll:
Is this still what we want? (vote: 👍 👎)
The text was updated successfully, but these errors were encountered: