GBKS
commented
9 months ago Going to close this issue, as we discussed the prototype as a group, and you can find it linked from bitcoincore.app. Updates to the prototype can be handled in separate issues related to specific designs, research efforts, etc. I had put together a video overview of the prototype.
The prototyping features that our design tools (Figma) provide are great for testing simple, mostly static flows. Limitations are, for example, a single size rather than responsive layouts, lack of input fields, and they get super complex to work with very quickly since design tools are not made for complex logic.
Web prototypes require custom code, but can fill a gap and allow us to quickly feel out and iterate a more realistic instance of the designs. For example, I put together the block clock prototype some time back, which has complex transitions that are impossible to do in Figma. Since our conversation last week about prototyping, I also built a second prototype (code) that is more about the general application flows. Some features:
It naturally also has some limits. There's no global application state (easy with Pinia), some of the more complex navigation patterns you know from mobile apps aren't supported, etc. Some of this we can add if we feel like it's worthwhile.
My suggestion is that we use this prototype for validating our design decisions and for user testing, next to the more static Figma prototypes. Some things will be easier and quicker to do in Figma, for others we may need the web prototype.
I hope this becomes a useful tool for the project. Let me know what you make of it.