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
There are pressing UX issues with Gora's UX - in the current sail version, content is irrationally exposed in narrow slots to try and maintain a 'short' page, for instance. In implementing a new #5 Rudder sail version, and hopefully through the grace that only a large shipment of prosciutto can buy from @vcavallo, we should also reconsider the User Experience stories:
• First Open
◦ I can see that I possess or do not possess some/any gorae
◦ I can see that I have created, or have not created some gorae that are still actionable
▪ I.E. that have remaining slots in their Max Holders left
◦ I can see that I have or do not have some incoming requests for gorae that I’ve made
◦ I can see that I have or do not have some incoming offers of gorae to accept or decline
◦ I can, from here, choose to interact with:
▪ my possessed gorae
▪ my created gorae (both those that have remaining space and do not)
• incoming requests for my created gorae (is this a subset of the above?)
▪ those gorae that have been offered to me
▪ base operations like:
• Create a gora
• Turn on and off usps mode
• send a gora
• request a gora
◦ *stretch* I can see that there is a way to browse gorae I’ve heard of through `%pals` and Gossip library integration
• “Possessed Gorae”
◦ Those gorae that I possess are displayed, sortable/filterable/searchable by name, date of receipt (do we have this?), issuing @p and tag
◦ For those gorae where there is a reissue property, I can clearly see that I have the ability to reissue them to my friends, as differentiated from those that do not (if we’re displaying them as cards w/ the circle gorae @ the top, perhaps differentiate by background color)
◦ Those gorae that are chain-letters (have %transfer property) are sufficiently separated from the primary field of vision that they do not distract from more meaningful gorae
▪ Perhaps they are, themselves a sub-window or another interaction away from this base page of possessed gorae
◦ If I both possess and created one of the gorae listed, it should be clear that I can reissue it
◦ I can apply a tag to one or a set of gora(e)
◦ I can set local-public on one or a set of gora(e)
▪ I can differentiate which are currently marked as public and which as private – I should only be able to see/set public on those where the HOST has also marked as public
• OPTION:
• “Created Gorae”
◦ I can see all gorae that I have created, separating %transfer from normal gorae
◦ I can click on a gora, resulting in an option to “send to” as well as a better view of the gora itself
▪ If the gora is already at max users, “send to” should be clearly disabled
◦ Those gorae that I’ve created are displayed (notwithstanding %transfer gorae) in a way that permits me to sort/filter/search by name, date of receipt (do we have this?), the issuer (@p) or tag
• “Base Operations”
◦ I have a helpful dialogue walk me through creating a gora. When I complete that dialogue, I’m taken to the “Created Gorae” page w/ the “send to” dialogue displaying for the gora I’ve just created (described above) – this can be done by query param or somethin.
◦ I can request a gora by ID (or if we have pals and rumors floating them around, we can click to request)
◦ I can send a gora – this will need it’s own page not quite possessed and not quite created, as I may have some exclusive to either category, each of which I can send, properly.
And from all those places... I ... can, uh, get back?
The text was updated successfully, but these errors were encountered:
There are pressing UX issues with Gora's UX - in the current sail version, content is irrationally exposed in narrow slots to try and maintain a 'short' page, for instance. In implementing a new #5 Rudder sail version, and hopefully through the grace that only a large shipment of prosciutto can buy from @vcavallo, we should also reconsider the User Experience stories:
And from all those places... I ... can, uh, get back?
The text was updated successfully, but these errors were encountered: