Mobile App Design
Mockup & Prototyping
EN ROUTE is a personalised public transport mobile application that focuses on Sydney’s transport system. The application aims to assist it’s users when travelling on public transport. The goal is create a service that provides a tailored, straight forward and user-friendly experience from when the user begins using the application until they arrive at their desired destination.
This project was developed from end-to-end and was given a timeframe of 12 weeks. With the feedback given, this has been one of my most proud projects to date as it felt rewarding to create a service that could provide convenience to the one's public transport routine.
Note: En Route was designed within a 'perfect world.' To attain real-time data for this mobile app to reach full functionality will require further and legal permissions, which was disregarded for this project.
As this project was personal, I had complete control of direction with the planning and processes throughout the development of the application.
The project underwent an end-to-end process within the given timeline of 12 weeks. The design-thinking process are as follows:
Five competitors were selected for analysis, each source gave a great range of heuristic to compare to. Three national services: TripView (Mobile only), Opal Planner (Mobile only) and Trip Planner and two international services: Trip Go and City Mapper.
Three competitors intend to provide their service to the same primary audience, individuals who needs information on the best and efficient route to their desired location. Tripview and Opal Travel chose to aim to the same public transport (PT) demographic however with a different goals. TripView aims to provide information to individuals who want to know the timing of their preferred mode of transport to a specific bus stop/station/wharf. Opal Travel have a different priority as they are the source of payment for PT, providing a service to manage one’s Opal cards that is connected with an account. Overall City Mapper provided the best experience as it offered more options for users to choose from, a cleaner information architecture despite the large amount of content that can presented.
The following heuristics were explored: look and feel, audience, primary and secondary content, navigation, information required from the user, information returned to the user, options of transport provided, use of tracking data (real time updates and location tracking), Opal sync, mobile performance (notifications) and rating and social presence.
To diversify against it's competitors, the MVP must have:
Five extensive face-to-face user interviews were conducted over a week and a half period. Participants included: two University students, two work full timer and one casual freelancer, all of who, catch public transport during their day-to-day routine and use their mobiles regularly.
The interviews consisted of open-ended questions to understand each individual's routine and behaviours when catching public transport and to depict pain-points during their journeys.
In no particular order, assumptions made were the following:
All interviews were recorderd and trascribed. From the qualitative data gathered, I was able to map, organise and group the data into behavioural, attitudinal, goals and demographic themes to create my personas.
The interviews confirmed 6 of the 8 assumptions to be true, the remaining two were disregarded from further research as they proven to be false, no one has ever found themselves lost when findng their way to a new location and no one blamed their app for being late.
Smaller gaps were indentified during the interviews which were then testing through the use of a survey:
40 candidates and 24 results were returned. The findings include:
These results were mostly proven true except one however the opportunities mentioned earlier stay the same.
Two personas were created from the key segments established through behavioural, attitudinal and goal themes to represent the archetypes explored:
The user journey maps gave me a greater understanding of each defined user and allowed me to distinguish the persona's pain points and highlight their joys in their public transport routine.
Using the insights gathered from the research and the journey maps, I was able to solidify the solutions and features my application needed. I established the information architecture and displayed the structure and hierchary visually to assist with assigning each screen with the necessary features.
Through the information architecture - user flows were mapped out. These include:
I roughly sketched pages and the potentional navigation of the application (shown on the right), whilst writing small comments as they come by.
I took the sketches and digitally reproduced them using Axure RP. With the outline of the information architecture, I made sure the each feature accomodated with the user flows.
An extremely rough sketch...
...into something more clear to read.
Through revision and feedback, the wireframes were then converted into a functioning prototype. The purpose of the protype were test the flow and the desired features of the app.
The prototype underwent usability testing to record the behaviours of users when asked to complete certain tasks. These tasks include:
Collected from the four usability tests, all candidates were given 6 tasks to complete.
The overall design of the mobile app was good, clean and mostly straight forward. Most features included were favoured however some were either being disregarded and were hard to understand at first glance. A number of amendments are recommended to improve the quality of ease and experience of the app.
All tasks that were conducted were successfully completely by all users which indicates that the app is easy to use.
A number of minor technical issues were identified during the dry user test, which included, spacing, missing back buttons and a broken home button. All were fixed for the final user testings.
Key recommendation identified are the following:
This application is nowhere near to its potential however it's on the right direction. There's definitely a lot of room for improvement in all areas of layout, features and flow overall. The next step would be considering the recommendations from the usability testing and plan which features are a priority for the next set of testing. Ideally, establishing a more real time feedback and notification for the user to test would provide more data that improve the app considerably however it would require a lot more help and production time.
As mentioned earlier, this is one of my most proudest work to date. Overall I enjoyed the end-to-end experience and it ended up being more insight than I thought. As a regular commuter on public transport, I had my own pain-points however to be able to bring myself out of the subject and to listen and observe other people's experience, there were a lot more behaviours that I normally don't consider.