Accepted by James
This makes it easier for a user to navigate with just their thumb.
The buttons on the mobile version of the website will be displayed on the bottom rather than the side or a dropdown.
This will make it easier to navigate but may result in misinputs.
Dropdown
Accepted by Hieu
Simplifying the settings
We want users to be able to access the settings with as few button presses as possible. As a consequence, since we do not have many settings, we can simplify the settings and just make it all in one page in 3 dropdowns so the user will not get lost.
This may make the settings somewhat cluttered but it will result in less button taps for the user which creates less friction.
Navigative through tabs
Accepted for Sprint 2 cleanup
The prototypes use lightweight single-page navigation. Some screens could change content without a durable route, which made browser Back/Forward behavior and active navigation states harder to predict.
Prototype navigation should use simple hash-based routes, keep active navigation states in sync with the visible screen, and provide Back and Home controls on secondary screens.
Users can return to the home screen from key flows, share or reload routed prototype screens, and avoid dead-end states during demos.
Full client-side routing library