App prototype testing

In many projects, I would have opted for a quick test on a low-cost bare-bones prototype. However, in this case, I decided to go straight into development to test the two high fidelity flows. The main reason for this decision was a realization that the only way to gauge the feasibility of the solution would be through observation of how users behave in a real-life setting booking actual bikes. Of course, this was risky because the prototype tests might send me back to the drawing table. However, we already had a great part of the technical architecture in place, which meant that building the two prototypes would only take 2-3 days.

In total, I ran approximately 10 tests on the two prototypes with different user segments. The prototype tests indicated that one of the prototypes outperformed the other one across user segments and highlighted a couple of things to change in the final implementation.