Needfinding for Glance app is the first and most important step in UX design. It all starts with the user. Optimally we need 21 potential users but we only had enough resources to take 4 interviews. Still invaluable information to gather all the real needs of the users and more importantly get the reasons, the why, behind those needs. - Needfinding is the art of talking to people and discovering their needs—both those they might explicitly state, and those hidden beneath the surface. It is only in truly understanding people that we can gain meaningful insights to inspire and inform a final, impactful design.
View PDF
View PDF
storyboard 1/2: the first potential story that the user could experience. The storyboard is to share with the shareholders and the rest of the team that these are the situations where the user will find himself into and this is how he feels when the app solves a real problem for him
View PDF
View PDF
chosen storyboard 2/2: More than one storyboards are needed because many needs will come out of the interviews but not all can be addressed in a single app. From the multiple storyboards, one is chosen to be the main story that the user will go through using our app. As you can see it has a happy ending!
View PDF
View PDF
balsamiq prototype 1/2: The first prototype has a tabular layout where the user sees some important info on the home screen and the tabs at the top navigate him to the rest of the screens
View PDF
View PDF
balsamiq prototype 2/2 (chosen): Rapid prototyping continues with the second prototype which has four menu icons at the four corners of the screen that the user can drag diagonally to make the four screens appear, while there is more real estate area for the widgets of the main screen. According to user-testing it was easier and more interesting for users this low fidelity prototype. That is why the high-fidelity prototype is based on this one
View PDF
View PDF
I must admit the first part of the high fidelity prototype was implemented without keeping track of time, thus the empty columns but fortunately it was delivered on the expected date. Furthermore the time to implement the second part was less than the expected which is a very good thing! :)
View PDF
View PDF
This is the plan on how to execute the User Testing process, the evaluation of the previously created high fidelity prototype. The users have to go through a number of tasks and the ux designers have to measure the time and success/failures
View PDF
View PDF
The users are asked to perform a range of tasks and all is needed is a note if they have succeeded or not and a timer to measure how long they needed to perform each task. The result are these quantifiable measures
View PDF
View PDF
By observing the users and listen to their comments we have collected a number of qualitative data
View PDF
View PDF
The design stopped at this iteration because of lack of resources but the user testing process has given us many hints in order to proceed with a number of changes and improve the experience of the user
View PDF
View PDF
gLike
Glance
Information we are receiving everyday, either because we had requested it or not, in addition with information we are actively seeking on a daily basis are data that help us make decisions. My point of view is that most of them like picking a means of transportation or picking the right clothes for the current weather are trivial decisions that a computer can handle in order to give us a stripped view of this data in a simple dashboard that can be processed from our brains in a glance.
Do not forget to check the alternative/modified high fidelity prototype: http://glance-modified.netlify.com/
