Mobimeo
Mobimeo
Mobimeo
Mobimeo, part of the Deutsche Bahn Group, builds travel apps for commuters and cities. Pommer Design led UX for the relaunch of Streckenagent, the app that alerts commuters to delays on their routes, and designed flows and interfaces for Mobimeo’s white-label mobility app.
Mobimeo, part of the Deutsche Bahn Group, builds travel apps for commuters and cities. Pommer Design led UX for the relaunch of Streckenagent, the app that alerts commuters to delays on their routes, and designed flows and interfaces for Mobimeo’s white-label mobility app.
Mobimeo, part of the Deutsche Bahn Group, builds travel apps for commuters and cities. Pommer Design led UX for the relaunch of Streckenagent, the app that alerts commuters to delays on their routes, and designed flows and interfaces for Mobimeo’s white-label mobility app.
Year
2021
Client
Mobimeo
Category
Mobility
Duration
6 months
Objective
Objective
Berlin-based Mobimeo, a startup of Deutsche Bahn, was building a whole new version of Streckenagent, the popular German travel app. The new version was to ship with a new interface and features such as connection alarms and other route subscriptions. Mobimeo was also building a white-label mobility app on its own platform, with one goal: the most pleasant, least intrusive travel experience in the industry.
Role
Role
On Streckenagent, Pommer Design was UX lead: user research, user flows, design concepts, information architecture, interface design and asset delivery. On the white-label app, the work covered user flows, design concepts, visual design, research and data analysis, with a focus on the different modes of transport.
Approach
Approach
Commuters check these apps in a few seconds, on the platform or on the stairs. An alarm therefore leads with the line, the problem and what it means for the trip, and one button opens the alternatives. Alarms cover a single connection or a time frame, such as every weekday from 17:00 for an hour. In the mobility app, public transport, car sharing, e-scooters and walking sit side by side with time and price, so the choice takes one look.
Outcome
Outcome
The client received the first alpha of the new Streckenagent very well, and existing users move to the new app automatically. The white-label app has a steadily growing user base.
Illustrative views. Client work is confidential. We show the real work under NDA, on request.
More work More work
03
//FAQ
Questions
ANSWERS
01
How does a project start?
With a short discovery phase. We agree on goals, constraints and success criteria and put them in writing first.
02
What kinds of organizations do you work with?
Organizations that run on information: banks and insurers, airlines and rail operators, energy, pharma and software companies. Size matters less than the ambition for the product. The common thread is complexity: dense data, several product teams, or expert users with no time to spare. Early-stage companies with a hard problem are welcome too.
03
How do you approach complex digital platforms?
We map the work before we design for it: who decides what, under which business rules, and how the systems depend on each other. That map becomes the frame for every feature and team that follows.
04
How do you keep a large product portfolio consistent?
With a design system that engineering owns as much as design does: shared components, documented decisions and a review process for changes. New teams start from it instead of from scratch, and the portfolio still feels like one product as it grows.
05
How do you measure success?
We test the new product against the old one on the same tasks and compare time, errors and ratings. A project succeeds when the new version wins on all three. After release we measure again, and the work counts as done when the numbers hold in daily use.
06
Who will work on our project?
Programs of six to twelve months run with a core team led by Moritz Pommer, the founder. Specialists in research, interface design and engineering join larger programs.
07
Can we see the real work?
Yes. The views on this site are illustrative, because client work is confidential. In a call under NDA, we walk you through the real projects.
08
Do you work in German?
Yes. Interviews, workshops and documents run in German or English, whichever your teams work in.
09
Which accessibility standard do you design to?
WCAG 2.2 AA, by default. We design and test against it, so accessibility is part of the specs engineering builds from.
03
//FAQ
Questions
ANSWERS
01
How does a project start?
With a short discovery phase. We agree on goals, constraints and success criteria and put them in writing first.
02
What kinds of organizations do you work with?
Organizations that run on information: banks and insurers, airlines and rail operators, energy, pharma and software companies. Size matters less than the ambition for the product. The common thread is complexity: dense data, several product teams, or expert users with no time to spare. Early-stage companies with a hard problem are welcome too.
03
How do you approach complex digital platforms?
We map the work before we design for it: who decides what, under which business rules, and how the systems depend on each other. That map becomes the frame for every feature and team that follows.
04
How do you keep a large product portfolio consistent?
With a design system that engineering owns as much as design does: shared components, documented decisions and a review process for changes. New teams start from it instead of from scratch, and the portfolio still feels like one product as it grows.
05
How do you measure success?
We test the new product against the old one on the same tasks and compare time, errors and ratings. A project succeeds when the new version wins on all three. After release we measure again, and the work counts as done when the numbers hold in daily use.
06
Who will work on our project?
Programs of six to twelve months run with a core team led by Moritz Pommer, the founder. Specialists in research, interface design and engineering join larger programs.
07
Can we see the real work?
Yes. The views on this site are illustrative, because client work is confidential. In a call under NDA, we walk you through the real projects.
08
Do you work in German?
Yes. Interviews, workshops and documents run in German or English, whichever your teams work in.
09
Which accessibility standard do you design to?
WCAG 2.2 AA, by default. We design and test against it, so accessibility is part of the specs engineering builds from.
//FAQ
Questions
ANSWERS
How does a project start?
With a short discovery phase. We agree on goals, constraints and success criteria and put them in writing first.
What kinds of organizations do you work with?
Organizations that run on information: banks and insurers, airlines and rail operators, energy, pharma and software companies. Size matters less than the ambition for the product. The common thread is complexity: dense data, several product teams, or expert users with no time to spare. Early-stage companies with a hard problem are welcome too.
How do you approach complex digital platforms?
We map the work before we design for it: who decides what, under which business rules, and how the systems depend on each other. That map becomes the frame for every feature and team that follows.
How do you keep a large product portfolio consistent?
With a design system that engineering owns as much as design does: shared components, documented decisions and a review process for changes. New teams start from it instead of from scratch, and the portfolio still feels like one product as it grows.
How do you measure success?
We test the new product against the old one on the same tasks and compare time, errors and ratings. A project succeeds when the new version wins on all three. After release we measure again, and the work counts as done when the numbers hold in daily use.
Who will work on our project?
Programs of six to twelve months run with a core team led by Moritz Pommer, the founder. Specialists in research, interface design and engineering join larger programs.
Can we see the real work?
Yes. The views on this site are illustrative, because client work is confidential. In a call under NDA, we walk you through the real projects.
Do you work in German?
Yes. Interviews, workshops and documents run in German or English, whichever your teams work in.
Which accessibility standard do you design to?
WCAG 2.2 AA, by default. We design and test against it, so accessibility is part of the specs engineering builds from.
03
//FAQ
Questions
ANSWERS
01
How does a project start?
With a short discovery phase. We agree on goals, constraints and success criteria and put them in writing first.
02
What kinds of organizations do you work with?
Organizations that run on information: banks and insurers, airlines and rail operators, energy, pharma and software companies. Size matters less than the ambition for the product. The common thread is complexity: dense data, several product teams, or expert users with no time to spare. Early-stage companies with a hard problem are welcome too.
03
How do you approach complex digital platforms?
We map the work before we design for it: who decides what, under which business rules, and how the systems depend on each other. That map becomes the frame for every feature and team that follows.
04
How do you keep a large product portfolio consistent?
With a design system that engineering owns as much as design does: shared components, documented decisions and a review process for changes. New teams start from it instead of from scratch, and the portfolio still feels like one product as it grows.
05
How do you measure success?
We test the new product against the old one on the same tasks and compare time, errors and ratings. A project succeeds when the new version wins on all three. After release we measure again, and the work counts as done when the numbers hold in daily use.
06
Who will work on our project?
Programs of six to twelve months run with a core team led by Moritz Pommer, the founder. Specialists in research, interface design and engineering join larger programs.
07
Can we see the real work?
Yes. The views on this site are illustrative, because client work is confidential. In a call under NDA, we walk you through the real projects.
08
Do you work in German?
Yes. Interviews, workshops and documents run in German or English, whichever your teams work in.
09
Which accessibility standard do you design to?
WCAG 2.2 AA, by default. We design and test against it, so accessibility is part of the specs engineering builds from.
Project inquiries
Frankfurt and London. Operating worldwide
Interaction design for mission-critical software
Product and interaction design for enterprise platforms and apps. Tell us about your project.