Onboarding Wizard #421
Labels
No labels
Blocked
Bug
Documentation
Duplicate
Enhancement
Good first issue
Help wanted
Idea
In progress
Invalid
Major feature set
Packaging
Question
Soon
UI/UX
Upstream
You're dreamin'
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nostr/gossip#421
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
[EDITED]
Create the onboarding wizard.
@mikedilger this is a first raw review of the partial wizard branch [9fa268ca].
At this stage I don't offer any design suggestions, just basic advice to make it more usable. We can review the UI later, maybe with @bu5hm4nn's help.
Welcome
The default DPI does not match the system value; I'm using a 144dpi display but the default is set to 72, if I apply this value the interface is resized by 50%. Would be nice to set it correctly.Moved to https://github.com/mikedilger/gossip/issues/511Import keys
Import a private key
Import > Read your nostr configuration data
Using my real key all the data is "Missing".
"Fetch from this relay" is unimplemented.
So I'm blocked here.
Create a new account
Create > Read your nostr configuration data
All the data is "Missing", of course. I suppose this wizard should be completely different.
So I'm blocked here.
General consideration
Probably I would move the three "Import.." buttons of the "Import keys" section and the create keys form in the first welcome step, creating two horizontal sections:
I would remove the status bar, it is not not the right places for blocking error messages and in a wizard the user should focus just the main are following the instructions, without watching around.
Legend:
◻️ Low low priority
◾️ Normal priority
📍 High priority
❓ Need more analysis
The default DPI issue is, if broken, a pre-existing problem that is independent of the wizard. I think that egui/winit are sometimes unable to determine it. I get 72 too, which is also wrong for my system. Let's remove that from this issue and make a separate issue. #511
I disagree with B3. If you type it twice, you can't be sure which one was mistyped. Clear them both.
You are right, but in my experience usually is the repeated input that is wrong.
If the user is no sure about the first input can wipe it himself.
However it is not a big issue.
The wizard isn't ready for review. It is still changing a lot. I just wanted high-level thoughts on it. But I'll take all that feedback into consideration.
@mikedilger
Yes I got it, mine was just some thought I wrote down while I was testing it.
Would you like I propose a design/UX, so you can validate it, develop the tech part and maybe the @bu5hm4nn step in with the egui work?
I'd like to finish it functionally before I rearrange and style it. That has required me to make changes to the code that aren't directly wizard related on the unstable branch. Hopefully I can finish soon without too many more sidetracks.
I have pushed an updated 'wizard' branch. There are still some small functionality issues I need to work out, and more tests to run.
I tested the update, nice and really improved!
New account
If it is a new account creation could make sense to add also 2+2 random relays for inbox and outbox? New users probably cannot evaluate which relay choose, so we save them time and energy with a good default. If they know what they want with max 4 clicks they can remove the pre-set and choose something different.
About the UI to add the relays to the 3 list I would do it a little different:
A select at the top of each column; each time the user click an item it is added to the list below. The select include a first field "Input custom -->". If the user choose this value the select is replaced by a input and a small "+" button; the input can be used to add custom values to the list. (we should add a way to switch back to the select).
The labeling option with/without publishing in every step could be a little confusing.
I would simply use a "Continue".
Then add a last step the ask the user if he want to publish the new profile, maybe with some checkbox if we want to give this sort of granularity (profile, relays, contact list).
I wold put the followed list below the form.
Why do you use the term "DNS ID" instead of NIP-05?
I would then review some text and small details, but nothing really important.
Login with private key
Instead of showing this page with the three failed checks, why don't immediately try to fetch from the proposed relay (purplepages.es)? It is fastest and offer a "just work" flow.
Both "Fetch from this relay" and the next screen "Next >" should have the accent color.
I forgot: starting a new account, I had to reboot to make the relays operational; unlucky the bug is still here
I opened a dedicated issue for the "create new account" flow: https://github.com/mikedilger/gossip/issues/675
Superseded by #671 for 0.10 and #675 for 0.11 release