Jourly
Strategies:
UI/UX Design
Prototyping
Duration:
5 Weeks
Tools used:
Figma
Deliverables:
Research Synthesis
Wireframes
Jourly is a transit wearable app that provides easy and efficient public transportation information to all commuters via haptic technology.
This is a UI/UX accessibility project I worked on in fall 2020.
The Problem
If you have been on the New York City subway, you’ve probably heard this on the train:
“THISIS A h@Dj$a BOUNDTRAINNEXTSTOP $%*@F STREET”
The inspiration for this project comes from my experiences and observations as a commuter living in New York. I wanted to see how I can design a solution that makes people’s commute easier, more accessible, and less confusing.
User Research
I started my research with two main objectives in mind:
1. To understand how people with disabilities navigate the subway.
2. To discover behaviors, patterns, and pain points that have not yet been addressed by current apps & services.
Secondary Research
First, I want to get more contextual knowledge about commuters and their habits on the train. So I looked up some academic articles and studies and found that:
One thing that particularly surprised me is that many commuters don’t always have their phones out when they are on the train. This finding inspired me to think about other ways that I can deliver information without interrupting this habit, such as wearable devices.
User Interviews
To further investigate the challenges commuters with disabilities face on the trains, I talked to three people about their experiences in the subway. I asked them questions that would help me to understand their habits and preferences during their commutes, and I got some insightful responses from them:
These responses suggest that my solution needs to be quick and efficient and it has to be able to deliver audio information like announcements via text and haptics. I decided to design my solution on smartwatches since they can display information right on the wrist and have great support for haptic notifications.
User Persona
Based on all the information collected from my research, I created a user persona that reflects the problems shared by my stakeholders.
Competitive Analysis
Before diving into the design process, I took a look at some current mapping and navigation apps using the capability method to see where my solution needs to stand:
Google maps
Unique Capabilities:
Voice input: allows for hands-free input and offers some levels of accessibility
Explore feature: provides integrated and comprehensive information
Best Capabilities:
Efficient routing
Up-to-date information
Poor Capabilities:
Accessibility: the app may be too complicated for some users, like elders and people who rely on screen readers
Public transportation features such as train arrival times are included but aren’t prioritized
Citymapper
Unique Capabilities:
Citymapper prioritizes public transit features and makes information more comprehensible and easier to access
Best Capabilities:
Great support for wearable devices, which allows users to quickly check directions while commuting
Subway/bus system maps are available offline
Poor Capabilities:
Information isn’t as up-to-date as Google maps
(Again) More accessibility features are needed
Research Synthesis
To sum up, I found that:
Commuters, especially those with hearing impairments, need clear, instant, and accessible information regarding their trip.
My solution should also make sure that contents are displayed for easy access on the go and train announcements are delivered via haptic and visual notifications
Sketches & Paper Prototype
Keeping my research in mind, I drew some interface sketches:
To do some quick usability testing before I jump into finalizing my designs, I made a quick paper prototype using post-it notes and asked my friend to click through each page.
Some important feedbacks that I got:
1. Pages and buttons can be further simplified.
2. Features and information need to be more direct and clear.
Final Solution
Onboarding: zip through it, but also don’t worry about your privacy
The users will be prompted to put in their home and work address when opening up the application for the first time. Alternatively, they also have the option to enter a station closest to their home & office if they don’t want to disclose any private information. Since this is a watch-based app, I wanted to make sure that the onboarding process is as concise as possible.
Dashboard: start your trip instantly
The dashboard provides quick-start options and an overview of train status so that users can directly check on their commute in the morning or before leaving work. The information will come in handy especially during a busy morning. Now that you know when the train is coming, you’ll have more time waiting for your coffee to cool down!
Trip Planning: make an informed decision
The trip planning page will offer different routing options with train arrival time and train status. Users can decide which train to take depending on when they are ready to leave the house and not have to worry about missing their train.
Trip Status: simple directions for seasoned commuters
When users begin their commutes, they will see directions on their watch, which they can always ignore if they know how to get to the station. The trip status page will update once they get on the train and display essential information like their estimated arrival time, the number of stops left, and a mini-map of the current train. Knowing where they are going and when they’ll arrive will alleviate some of their anxieties during their commutes.
Notifications: enjoy your podcast, we’ll keep you in the loop
When a train is approaching the station, users will feel a zigzag-style vibration on their wrists so they will know a train is arriving without even having to check their watch. Service and onboard announcements are notified by a quick double-tap. Users can swipe up for more details on the announcement or simply ignore it.
Arrival notification: nap without worrying about missing your stop
The app will notify users with a continuous long buzz when their train is getting close to or arriving at their destinations. So they will have time to prepare to get off or wake up before they miss their stop.
Next Steps & Reflections
If I get to revisit this project in the future, I would love to explore other types of public transportation like buses or ferries. I would also expand my solution to include not only commutes but also other trips throughout the day. Lastly, because my solution is very specific to the conditions of the New York City subway, I would like to see how I can adapt it to other cities.
I actually never thought about designing an app specifically for Apple Watch when starting the project. I am glad that I have the freedom to embrace unexpected elements and make sure that my solution is backed by the research and the user’s perspective. I also had to adjust to designing for a much smaller screen; knowing that I have limited space to work with, I had to ensure the design components are not only readable but also effective and absolutely necessary.