Mockups and Prototypes

App product teams need mockups to present their vision and views of the final product and that is why here, in NaviGap, we use top tools to present best UI solutions.

In this post, we will present our mobile screen mockups to show the basic functions of our outlined scope.

Why prototype

No secret, that there is no perfect User Interface which will be explicit, intuitive and efficient for all users. However, close to perfect is possible and achievable with countless efforts, many hours of work and constant improvement. Thinking and interacting with your app just like your user is the key. A prototype is not a final product, it is the field for improvement and work. It starts with simple sketches and gets augmented by adding features, links, interactions, design improvements on its way to perfection. Prototypes allow prototypes allow us to test the feasibility and usability of our designs before we actually begin writing code. They allow to actually test and play with various user interactions scenarios.

Imagine

Sketching an app helps to ‘feel’ the actual thing and maximise ideas if only on the paper. Various techniques from pencil sketches to post-it notes dashboard can be used. We used a simple sketch to get the whole picture and then moved to available prototype tools to implement click-throughs interaction.

mock

Figure 1. A sketch of what we wanted

Click-Throughs

Then, we used JustinMind software to build our prototype and show our user interactions with it.

Here is the basic interaction map:

Picture1

Figure 2. Interaction map

Figures 3-6 show the initial set of Navigap screens simulated on iOS. Interactions are listed according to user action and marked with blue circles.

   Picture2

Figure 3. ‘Main_screen_feed’. Main screen with latest expert feed

Interactions:

4 on Click:   goes to ‘Q&A_with_experts’ with effect: pop

5 on Toggle:   goes to ‘Location_on_map’

6 on Click:   goes to ‘Expert_story’

7 on Click:   goes to ‘Expert_story’

8 on Toggle:   goes to ‘Location_on_map’

9 on Click:   goes to ‘Q&A_with_experts’ with effect: pop

Picture4

Figure 4. Q&A_with_experts. Interaction with expert users

Interactions:

2 on Click:   goes to ‘Main_screen_feed’

 

Picture5

Figure 5. Expert_story. Extended travel story of an expert user

Interactions:

1 on Click:   goes to ‘Main_screen_feed’

Picture3

Figure 5. Location_on_map. Extended map of chosen destination

Interactions:

1 on Click:   goes to ‘Main_screen_feed’

The interactive simulation can be accessed via the link: https://www.justinmind.com/usernote/tests/25458829/25462335/25465092/index.html

Final thoughts

We understand that our highest priority is the user and making their experience pleasant and fun in lines with our goals is a challenge. However, using different approaches, tools and techniques to reach the ultimate App prototype is something we take seriously within our team.

NaviGap UML diagrams

In this part, we will talk about our development model views described in Unified Modelling Language. UML is a language which we will apply to describe use cases meaning the interactions of an actor (user) and a system to achieve certain goals. This is an in-between process: after we gathered all requirements and shaped our agenda and before we actually started coding.

Our app users

In previous posts, we identified our user personas. Now we can proceed and implement those personas into our interaction use cases. It helps us to identify the functionalities we want to offer to them. We don’t have to cover now the scenario of a registered or authenticated user, but we will treat as a seperate diagram.

Our app functionalities

Now we identify general functional blocks we offer for the actors (personas) aligned with activities they perform.

The First Persona is identified as a novice who comes for social value and expert advice. is clearly interested in

The Second Persona is an expert who was a novice at the beginning, but after a certain amount of contribution (posts, advice, photos etc.) became an expert (high degree of centrality) and can provide help/advice/guidance to novices.

Finally, the Third Persona is a commercial partner type of user who is interested in business add-on value.

Three iterations are needed to reach the outlined use case scope.

Figure 1. Use Case Diagram: NaviGap interaction

At this point, we can augment the Persona 1 case by expanding each functionality. For example, ‘Seek travel inspiration’ functionality:

Figure 2. Use Case Diagram: Augmented functionality

Through each augmentation iteration, we ask ourselves: is it enough? have we listed all possible functionalities that we can release? Step by step we will augment our UML layout and add blocks to each functionality. After each functionality has a detailed list of sub-functionalities we can look at it critically and think of additional features that will give us a competitive edge.

Our app communication diagram

As an example of UML communication diagram, we show the scenario when a user wants to login into their account. That provides a model-view-controller perspective of interaction.

 

Figure 3. Communication Diagram: Login

Our app state diagram

State diagrams can be seen as the essence of object-oriented programming (OOP). Those diagrams are good when we want to describe the behavior of a single object. In general, those diagrams define various states of an object during its life cycle.

A state diagram represents the actual changes in state, not the particular processes/commands creating those changes.

Figure 4. State Diagram: Novice User object

 

Why we need all those diagrams?

We assume that our team should have a clear understanding how the users interact with the App, what functionalities we are planning to offer to them and in what way they can access them. Overall, each diagram builds up a clear understanding of what is expected from the app, what role the users and other actors play in it, and helps to shape the outline of the UI design.

 

Personas

33214467092_6b7ddb717a_o

We have outlined in detail our goals and incentives, and especially mentioned our focus on the user, so now it is reasonable to prepare persona portraits to encapsulate our typical audience representatives.

In any platform development and design, it is necessary to think about who, how and why will use your product. Taking into account habits, wishes, concerns of our personas will drive the design vision and functionality of our app. We take into consideration the ‘use activity’ in order to compile our development requirements.

Behind our user interface is the understanding of real-life interfaces to support the process of traveling. We believe in a niche targeted approach so that best suitable scenarios fit a prefixed user group of a certain type.

In their academic research Viana G., Robert JM. (2016) give a definition for personas: they “are “hypothetical archetypes of actual users through which designers can develop a precise description of [the] user and what he wishes to accomplish”. In their paper, they conclude that building personas is helpful for designers to visualise and summarise functionalities and features of a product that is to be developed. Although, they note that it should be done in conjunction with real user usability testing. That said, our persona portraits represent a concentrated view from different angles of our potential users.

Our personas were generated from the thorough review of forums and related social networks followed by classification and critical analysis.

First, we brainstormed persona types and came up with three portraits: an undergraduate first-year student (18-22), a mature student (22-25) and a commercial partner. Our user experience team talked to representatives of these user groups (at university, book stores) acquiring tons of data and identifying motivations, worries, past experience, characteristics, and needs.

Second, our team collectively gathered, sorted out, systemised and classified all the data to produce objective portraits with a rich description of each persona.

Here are the results:

Screen Shot 2017-03-18 at 15.00.56 Screen Shot 2017-03-18 at 15.03.22 Screen Shot 2017-03-18 at 15.04.03

We hope that such user-centric design will elevate our product value to the highest level.

All images are used under CC license.