Startup Navigation UI

Overview

Designed and developed a fully functional automotive cockpit UI for an early-stage mobility startup, combining open-source mapping with Google Maps integration. The system was prototyped on constrained hardware (Raspberry Pi + Konstag) to simulate real in-vehicle conditions while staying cost-efficient and production-aware.

The objective was to deliver a fast, testable product that could validate both usability and business direction in front of stakeholders and investors.

The Challenge

• Restricted access to Google Maps APIs for small teams, with rising costs and non-enterprise limitations
• Limited hardware performance, requiring smooth UI behavior on low-power devices
• Fragmented user experience across navigation, media, and system controls
• Tight timelines and pressure to deliver a working prototype, not just design concepts

The prototype also needed to feel close to production quality so it could support investor conversations and early user validation.

Approach and Problem Solving

Instead of depending on a single map provider, I designed a hybrid navigation architecture that could switch between map sources based on availability, cost, and performance.

Map Abstraction Layer

Built a flexible layer integrating open-source maps and Google Maps, enabling provider switching without breaking the UI flow. This reduced vendor lock-in and long-term API cost risk.

Performance-First UI Design

Optimized rendering for Raspberry Pi by simplifying animations, minimizing redraw cycles, and prioritizing essential interactions. The interface remained responsive under constrained hardware.

Unified Interaction Model

Combined navigation, media controls (including Spotify integration), and system actions into a single flow to reduce context switching and driver distraction.

Max Touch Mode

Introduced an in-car interaction mode with larger touch targets and simplified gestures for safer and quicker operation.

Prototype-to-Production Thinking

Structured the architecture so engineering teams could scale and extend it, rather than treating it as a throwaway prototype.

Solution

• A fully interactive automotive UI prototype running on Raspberry Pi
• Seamless map switching between providers with minimal latency
• Integrated Spotify media controls within the navigation flow
• A driver-friendly touch interface optimized for real conditions
• A modular architecture ready for production extension

Outcome

• Delivered a testable end-to-end product, not just a concept
• Enabled real usability validation through live interaction
• Strengthened investor presentations with a working prototype and higher product credibility
• Reduced long-term platform risk by avoiding full dependency on a costly single-map ecosystem

Key Takeaways

• Build production-minded prototypes under tight constraints
• Navigate API limits and platform restrictions creatively
• Design complete systems, not isolated screens
• Deliver solutions that are technically viable and business-aware