Do you mind clarifying the UI issues? Then I can add to the feature request list.
Discussion
gifs. pretty please
It's incredibly cluttered. It's trying to show me everything everywhere at once.
Too many colors, too much info, too few dropdowns, popups, tooltips and other methods to cleanup the UI. Also too many features with no proper introduction as to where am I supposed to look for it or what it does. (especially streams)
Instead of criticizing every little detail. let me propose solutions instead:
- Notifications should primarily show what happened and only secondarily if at all current status.
- There should only be one place where new public stuff happens - They should be under the same button on the appbar and only in that view should you choose what it is you are looking for. (however if it were up to me. I'd have separate apps for both live streams and groupchats as they will inevitabbly clutter the UI)
- Anything thst doesn't neccessarily have to be shown right away should be hidden up to two clicks away. (For instance relay badges on notes in the feed, or notification options in create note view)
- It should be possible to turn off translations
There is a lot more that I'd say, but these hurt me the most I'd say. If you were interested, I could sketch up wireframes/prototypes with proposed modifications, because I will never be able to describe it as clearly as I see it in my head.
Thanks! I would love to get your wireframes.
The things you describe generally were placed there for a reason. For instance, the notification options were added as a specific request to get users to stop citing everyone, all the time. The user should review who he/she wants to notify at every new message. Otherwise, we just keep bugging everyone and it's very annoying for the other people, especially if they use new clients that are not filtering notifications yet.
Similar case for relay badges. The hope was to get users to pay attention to their relay set of choice. It was never fully implemented, but I think you get the idea. It doesn't need to be there in that way, but displaying where the message is coming from is a necessity in Nostr. Otherwise, we would just be slaves of relays.
The Notification doesn't show status. It's just groups the reactions without caring for a time-based feed, like twitter does. I am not sure if it is the best design and I am happy to change if it's not. But that's how we got here :)
I'll get to it and hit you up once I have anything presentable. :)
No need to solve everything at once. Specific recommendations for given flows or even placements in the UI are super welcome. We got no UI/UX designer in the team, so, blue ocean for you :)
Element-spacing, grouping and balancing can go a long way, even if no UI designer is at hand. #plebstr app does it beautifully, but also other #foss app like #glider.
Can you send me a screen shot when you see the spacing issues? Sometimes I need to adjust for certain phones
Not "issues" per-se. But check out said choice of spacing, grouping and balancing (plus use of font sizes and colors) on my sub-6" device screen.
#plebstr vs #amethyst


My small screen looks less cluttered because all the elements have more space to "breathe" on #plebstr. its not only about the choice of what to show, but also the choice of what NOT to show.
I have sent you a DM with a link to Figma where I outlined some recommendations for notifications.
A case in point to illustrate what I am saying. In the screenshot you can see (hopefully) the same notification in Plebstr and in Amethyst.
In Plebstr it just tells who did what where, which is exactly what I want to know and it did it on I'd guess ca 6rem vertically?
In Amethyst I don't even know what the notification is about until I scroll down, because the notification takes a screen and a half. It shows me a lot of what I don't need to know and I have to try quite hard to find what it is actually trying to convey to me, because there is too much going on at once and I cant quickly figure out what is the important part of that notification.



My bad, this is the actual two part notification.

