The project was developed by six different teams, each exploring a different direction — from taxi and car-sharing services to family-oriented experiences. Our team took a different approach: instead of designing for a single use case, we built a more universal driver application that could become the foundation for the wider ecosystem. I designed the product from the ground up, working within a small team and focusing on the overall experience, information architecture and interaction model. The challenge was the sheer amount of functionality. Beyond basic vehicle controls such as locking doors, opening the trunk, controlling windows and folding mirrors, the application had to handle trips, multiple drivers, documents, charging stations, navigation, media and other connected services. The key was to make all of this feel like one product rather than a collection of unrelated features. I structured the experience around the driver's relationship with the car, keeping the most important actions immediately accessible while organizing deeper functionality into clear, contextual areas. Because the product was designed as a universal foundation rather than a single-purpose application, the architecture could accommodate different scenarios without having to redesign the experience from scratch. This approach allowed our team to move unusually fast. Within a few months, we were able to demonstrate a level of product maturity that other teams were still working toward after much longer development cycles. The application eventually became the foundation for further development of the Atom ecosystem, providing a common product language and architecture that could be extended across different services and use cases. The result was a complex but coherent driver experience that connected vehicle controls, mobility services and everyday digital needs in a single interface — turning a huge set of capabilities into something that could still feel simple and approachable.