Zoning, wiframe, mock-ups,... Discover our best practices to offer a seamless intermodal experience to your MaaS application users.
Designing a MaaS solution that allows you to book a VTC, a train ticket, unlock a scooter, validate your bus ticket from your smartphone... It's great! Except that unifying different services means knowing how to skillfully combine different interfaces and user paths. A real headache that we are going to avoid by sharing with you our complete methodology to optimize the intermodal experience on your MaaS solution.
What are the technical specifics for a railway company? A parking ? A electric scooter service? A VTC? Or public transport?
How to best build the skeleton of your MaaS application without forgetting any key step? Is it possible to remove some features?
Concrete work, with the design of 3 complete and different user paths (city dweller, rural dweller & business traveler)
What are the three best practices that must be followed for a truly seamless intermodal experience in your MaaS application?