Wednesday, 4 November 2015

First prototype

We built the first prototype in the recommended program Flinto (desktop version), which was not very clever. The desktop version can only export the file with .flinto extension, which means we can't share the prototype in the Flinto online version (it doesn't import). To view our prototype you can either watch the screen cast, or download the desktop/iOS/Android version of Flinto.

Here is the link to the Flinto file (since this is a course-recommended application we assume that the examiner can use this file):
https://drive.google.com/file/d/0B_8uNNylE9zSWEQtSVZWajZjWWM/view?usp=sharing

The screen cast is doing the following steps:

1. Tapping login
2. Tapping on the statistics
3. Tapping in the same place again to get back
4. Tapping "Buy Ticket"
5. Tapping the blue top border
6. Tapping the white settings icon (with gray background)
7. Tapping Logout

Note that I press beside the tapping area to get the app to show with a blue flash which areas that are interactive (this is a Flinto prototype feature, not intended to be a feature in our app).


This is the very first high-fidelity prototype that among others will clarify vague requirements, think aloud evaluation with a user and check that the app just seems to be in the right direction to solve our problem. Since we don't write any code ourselves (which we actually are more than capable to do) this would not be considered a very expensive thing to do, even though in general the high-fidelity prototype would be.

Here we did have to compromise a lot with the features to get the app to seem easy to use. It got very clear that some features that we though would be needed in this app actually did not solve the key issues that we had. This was easier to understand when we were prototyping this first interactive version of the app. It also got very clear when we thought about what functions the will perform, the app should get people to save money and make the payment easier.

No comments:

Post a Comment