Package type visualisation (improvements) #831
Replies: 3 comments 16 replies
-
|
Agreed 💯 |
Beta Was this translation helpful? Give feedback.
-
|
Hey! How is it going? @anasereijo and I have been exploring for a few days different ideas on how to display the packages when we only have one. One of the options we've explored, and the one we've finally settled on for the proposal, is the idea that @Feichtmeier proposed at the time. While it may also lead to think that it is clickable or not, we think it is the way that best maintains visual consistency between applications with only one package and applications with both. There are different design systems that account for this type of chips, where the left side corresponds to a "larger category" than the right side, which is usually clickable. So we think that, given the circumstances, this option is plausible and could work. As for the use of typography and colours, although we have basically followed Yaru's guide for this, we have tried to highlight a little one button over the other with the weight of the typography and the shade of grey used in each element. This is the proposal explored:
Thanks for everything! 😊 |
Beta Was this translation helpful? Give feedback.
-
|
I see this will soon become a never ending discussion (😅), which is absolutely fine (and part of the process), but I am becoming a bit worried about the deadline. sooo, hear me out – what if we do the following: We can go with @madsrh's proposal of having the package icon on top of the app icon, and test it with users. Don't change the segmented button to rounded corner, and we can then do the typography improvements @Zoospora proposed for the segmented button We can always see how this goes with user interviews, and overall feedback, and later on we can continue iterating on this if needed? Is this okay? |
Beta Was this translation helpful? Give feedback.
-
I see what you mean. Let's NOT change all buttons 😅 We have to keep the style that fits the desktop ofc. It was just an idea, because I think the selected Snap toggle looks IMO a bit like the disabled Update button (I know the text color is different). I'm sure it's not an issue, I was just exploring if there was a clear/legible/more obvious solution. |
Beta Was this translation helpful? Give feedback.
-
yeah, makes sense! I still think we should hide the update button from there, though. If there are no updates available, no need to show it. @Zoospora and I looked at the yaru library, and seems that the disabled colour is also the same as the active colour for segmented buttons? Hard to tell because it's not clickable. We could propose something else in regards to colour
|
Beta Was this translation helpful? Give feedback.
-
Is there a deadline? 😮
Sorry, that is my fault. I like this solution, I just feel it's not 100% the best solution, but if everyone else is perfectly happy with this 👍 Let's go with that!! We can still explore other options in the future. EDIT:
I just meant, it looks like a disabled button 😉 |
Beta Was this translation helpful? Give feedback.
-
|
What if we go with your proposal @madsrh of having the package icon on top of the app icon? We are now focused on the explore page, but we will post here a mock-up asap! |
Beta Was this translation helpful? Give feedback.
-
|
what about the wide layout with snap/deb + channels + permissions? |
Beta Was this translation helpful? Give feedback.
-
|
@Feichtmeier You would properly want the channel list close to the snap/deb button, right? 🤷♂️ Meh |
Beta Was this translation helpful? Give feedback.
-
|
I have abs. no idea honestly. so many buttons |
Beta Was this translation helpful? Give feedback.
-
|
maybe we should unify instll and channel dropdown to a combobox button |
Beta Was this translation helpful? Give feedback.
-
@Zoospora is working on the following:
Beta Was this translation helpful? Give feedback.
All reactions