Route Subscriptions – DB Streckenagent

The DB Streckenagent app keeps commuters informed with real-time alerts on delays and cancellations for their chosen routes, anywhere in Germany.

Research UX UI

Project Overview

Daily commuting can be stressful and complicated. Frequent travelers rush out early in the morning to get to work, catch flights, or board long-distance trains. Delays, cancellations, and construction work on commuting routes can cause significant frustration and increase travel times. Additionally, public transport users often need to gather information from various sources, such as multiple transit applications or newsletters.

The Solution

The route subscriptions feature allows you to set alerts for frequently traveled routes. If your favorite route is affected by delays, cancellations, or construction work, the app will notify you in advance, ensuring you're informed before you set off.

Client

DB Streckenagent

My role

User research, concept validation, customer feedback documentation, wireframing, visual design and prototyping

Tools

Sketch, InVision, Userlytics, ProtoPie, PhraseApp, Miro

Platform

iOS | Android App

Timeline

2019 - 2021

"If the Bus doesn't comes I start checking on my App for alternatives…”

Ines, sub-urbran commuter

The Process

Understand

Primary and secondary research, along with feature benchmarking

journey

User journey mapping to identify touchpoints, pain points, and opportunities, while defining UX flows for testing.

interview

Conducted onsite and remote user testing sessions to validate UX concepts

pain points

Identified user pain points, revised personas, and mapped opportunities for product development based on research analysis

Wireframe

Iterated on existing concepts based on research analysis, reworked UX flows, and adapted prototypes

Brainstorm

Identified product iterations from user research analysis and proposed changes to roadmap priorities

Test

Tested new concepts, UX flows, and prototypes based on future roadmap priorities

Primary testing

For our initial testing round, it was crucial to understand user expectations. Together with our UX researcher, we conducted onsite moderated sessions to gain insights into:

  • How users perceive the new information architecture of the live navigation bottom sheet
  • How users locate relevant information regarding their public transport commute
  • How users respond to the new design of map components
  • How users perceive our new design language
shout-out to Annie our UX Researcher for the amazing cards idea 🤘

After gathering user feedback during our testing sessions, we analyzed the participants' insights.

"We live in a time where your phone is giving you so much information that I prefer not to get this."

Ines, sub-urbran commuter

Remote unmoderated testing

To streamline user testing efforts, we developed a process that enables designers to conduct their own user research sessions. Using Userlytics, designers can handle approximately 95% of the testing efforts, including:

  • Define the test objective
  • Gather potential questions related to user flow or key screens
  • Create the first draft of the test script and tasks

With the support of our UX Research team, designers ensure the script is free from biased questions and aligned with participant demographics. Designers conduct one to two dry run sessions to test the script and make necessary adjustments, ensuring clarity and understandability.

During the test, users interact with a prototype created in InVision or ProtoPie. The script guides users to specific screens within the prototype flow to address particular topics or questions. Once testing is complete, designers review all sessions to analyze and synthesize the gathered insights.

Initial UX flow

Initial sketches were created to align on the user flow and break it down into potential implementation phases.

User interface

Here are some key feature screens. For more, please download the S-Bahn Berlin Connect app.

And because people like dark mode 🌚…

Conclusion

It was a fun project, though quite tiresome, as accessing delay and cancellation notifications proved challenging. During the development of our MVP, I gained a deeper appreciation for the heavy lifting our backend team undertook to deliver a viable product. Quick and flexible feasibility check-ins with the development and product teams were essential.

Aditional Discussion

Points not covered in this case study but worth discussing in person:

  • User testing & evaluation
  • Visual design & style guides
  • Implementation process