-
Notifications
You must be signed in to change notification settings - Fork 108
Using the guide via AI #1161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Love this idea. Automate as much as possible. Spread awareness to change culture and expectations. Make wallet builders feel good about this process and that it is helping them do better work. |
I made a screen recording of Claude navigating nosta.me, set up a profile, and write a usability review. Setup, prompt and report are in the video description. Would be cool to make this a one-click thing - type in a URL and get a report with annotated screenshots 15 minutes later. Maybe even a Discord bot in our design review channel. But not sure how realistic that is. |
Big +1 on this. Targeting specific wallets and giving developers reports specific to their own products, with direct insights and clear suggestions on what to improve is more impactful. It’s less work for devs too. Right now they have to read the guide, think on their app’s design, and figure out what to fix. This would streamlines that process. A one-click “get report” flow would be much more useful. |
There's a conversation in Discord, about evaluating bitcoin application usability via AI. Two examples:
Verdict so far seems to be that these evaluations provide a good foundational review, which then allows for deeper looks into specific user flows and other design decisions.
Being able to automate these reviews makes them a no-brainer to integrate into regular design & development workflows.
So how can we push on this further? One idea is to create a page in the guide (maybe under resources?) that provides workflows that people can adopt easily. They could be based on use-cases and include step-by-step instructions, prompts, videos, and tips on evaluating the output. We're still feeling out all these capabilities, so I'd start it simple and iterate as we learn.
What do you think?
The text was updated successfully, but these errors were encountered: