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
Notes from my design review of IPFS Desktop (which, of course, largely reflects the Web UI interface), for discussion …
This interface is very well designed; I found no glaring issues in my review. It could be improved here and there, but nothing is terribly awry, imo. That said, below are some comments touching on visual design, heuristics, functionality, and accessibility.
Stepping back from these granular thoughts, I wonder if a fully new concept might be interesting and useful. The app is currently structured much like a website: divided into sections, with global navigation running down the side. It might prove more useful structured as a dashboard, with lots of information surfaced in a compact layout. I’ve wired up one way this could be laid out over in #1003. Doubtless it's too much work for us to take on right now, given our documented priorities, but it’s a conversation starter, at least.
* fix: improve color contrast on buttons
make the add buttons bg-navy and highligh the plus symbol in aquaish
WIP on #1004
License: MIT
Signed-off-by: Oli Evans <oli@tableflip.io>
Notes from my design review of IPFS Desktop (which, of course, largely reflects the Web UI interface), for discussion …
This interface is very well designed; I found no glaring issues in my review. It could be improved here and there, but nothing is terribly awry, imo. That said, below are some comments touching on visual design, heuristics, functionality, and accessibility.
Stepping back from these granular thoughts, I wonder if a fully new concept might be interesting and useful. The app is currently structured much like a website: divided into sections, with global navigation running down the side. It might prove more useful structured as a dashboard, with lots of information surfaced in a compact layout. I’ve wired up one way this could be laid out over in #1003. Doubtless it's too much work for us to take on right now, given our documented priorities, but it’s a conversation starter, at least.
Meanwhile, here are some notes on the current app.
The text was updated successfully, but these errors were encountered: