Neuron Micromobility leader · rider + operator apps · SE Asia + AU

How an embedded design team helped a mobility leader ship across rider and operator apps.

Outcome Extension, not replacement, embedded with the in-house team across rider + operator apps. Two apps, one design language, daily scrums and sprint cadence. The fleet-management credential that later won Lity.
Neuron. Singapore-born micromobility leader, rider + operator apps

Imagine extending an in-house design team without replacing it.

Neuron is a Singapore-born micromobility leader, e-scooters and e-bikes across cities in SE Asia and Australia, certified carbon-neutral, designing and manufacturing their own vehicles for safety and sharing. They had a real product, a real customer base, and an in-house design team that already understood the system. What they didn’t have was enough designer-hours to keep up with feature growth. The brief: extension, not replacement.

01Scaling consumer + B2B platform. Two apps live on top of the same fleet, a rider app for end-users and an operator app for local service partners. Both needed capacity, not a takeover.
02Embed alongside the team that’s already there. Daily scrums, sprint meetings, strategy sessions. Pick up flows in the sprint queue alongside the in-house designers; don’t take them over.
03One vocabulary, two audiences. Hold the same Material-aligned bar across consumer and operator surfaces so the system scales as new cities and vehicle types come online.
Scope Both apps Rider + operator, simultaneously. Pin vocabulary, input fields, feedback patterns designed once, used twice.
System Material-aligned Industry-standard primitives. Input fields, snackbars, feedback, built to scale with the platform.
Model Embedded One designer, slotted into the team. Daily scrums, sprint cadence, extension, not replacement.
Signal Cross-app One vocabulary, two audiences. MapView pins designed once, deployed across rider + operator with role-aware variations.
The story

Extension, not replacement. One embedded designer across the rider and operator apps.

Neuron is a Singapore-born micromobility leader operating fleets of e-scooters and e-bikes across cities, certified carbon-neutral, fast-expanding into new geographies. They had a real product, a real customer base, and an in-house design team that already understood the system. What they didn't have was enough designer-hours to keep up with feature growth. The brief was specific: extension, not replacement. Embed alongside the existing team, pick up flows in the sprint queue, hold the same Material-aligned bar across the rider app and the operator app.

One product designer slotted into Neuron's in-house team from day one, daily scrums, sprint meetings, strategy sessions, picking up flows alongside the in-house designers rather than taking them over. Inconsistent input fields and feedback patterns were a system problem, so we built Material-aligned primitives instead of inventing a new system. Snackbars replaced static banners with severity-tiered, dismissable, non-blocking feedback. Rider and operator apps both render the same fleet on a map, so we rebuilt the pin layer as a single visual vocabulary, vehicle type, battery level, status, with role-aware variations. One system, two audiences, faster incident triage on both sides.

ClientNeuron · micromobility leader
RegionSingapore-born · SEA, Australia, UK, Canada
DurationEmbedded designer · daily scrums
StatusLive across rider + operator
What we walked into

The audit named four heaviest costs.

Both apps had been built fast as Neuron expanded across cities. The system kept up; the design didn’t. Each app accumulated patterns from a different sprint and a different deadline. The audit named four: a cluttered home map where the rider’s 5-second jobs (locate, ride) were buried in competing UI; three different input patterns across forms, with different validation and accessibility regressions; static banners that blocked the ride, critical messages caught in the dismissal reflex; and an operator app that fell behind the fleet, with status hard to read at a glance.

Chapter 01

The home map: a floating panel that respects both jobs.

The rider’s home has two jobs in five seconds, show me where the vehicles are, and let me start riding one. The MVP filled the surface with competing UI. We replaced it with a floating panel that sits over the map and contains only the action affordances the rider needs in the moment. Tap a vehicle; the panel updates with the detail. Expand for a richer view; collapse back to a quiet bottom strip when scanning. Same surface, different focus depending on the moment.

neuron app · rider · home
Neuron rider app, three phones showing the home map with a scooter selected, the vehicle detail bottom sheet, and an alternate detail layout for ride start
Rider app Home map · floating panel · vehicle detail → ride start Rider’s first surface
Chapter 02

System primitives: input fields, snackbars, the scaffolding everything else stands on.

A consumer app feels consistent because of primitives, not just screens. We built two primitive layers Neuron didn’t have a strong system for, input fields and snackbar feedback, both grounded in Material Design. Industry-standard, accessibility-proven, engineers and designers already fluent in the conventions. Critical messages still earn the user’s attention; everyday messages stop interrupting the ride.

neuron app · payment · method
Neuron input fields. Material-design-aligned input components shown across four Add Payment Method screens, demonstrating consistent label, validation, and entry patterns
Input fields Material-aligned · consistent labels, validation, accessibility Form primitives
neuron app · feedback · snackbar
Neuron snackbar feedback, floating message at the bottom of the rider home map screen, non-intrusive with an explicit close affordance
Snackbar Floating · severity-tiered · dismissable · non-blocking Feedback layer
Chapter 03

MapView pins: one vocabulary, two audiences.

Rider and operator apps both render the same fleet on a map. The MVP had two different pin systems that didn’t encode the same information. We rebuilt the pin layer as a single visual vocabulary, vehicle type via icon, battery level via fill, status via color, with role-aware additions. The rider app surfaces ride-readiness; the operator app uses the same pins plus maintenance overlays. Both audiences read the same map and infer the same things.

neuron · pin system · rider + operator
Neuron MapView pin system, full grids showing the rider app pin variants on the left and the operator app pin variants on the right, with vehicle-type icons, battery-level fill, and status colors
MapView pins Vehicle type · battery level · status · rider + operator One vocabulary
Chapter 04

The operator app: clearer data, faster decisions.

Local service partners use the operator app for the unglamorous half of micromobility, battery checks, maintenance triage, vehicle relocation. We introduced a clean component-based layout with intuitive data viz, distinct vehicle-type icons, battery levels, and key status indicators visible without drilling in. The vehicle detail bottom sheet went through multiple structured iterations testing density vs. action prominence; the version that shipped balances both, and the surface holds up as fleets scale into the thousands.

neuron app · operator · fleet
Neuron operator app, three phones showing the dense fleet map view with operator-specific pins, the vehicle detail with maintenance actions, and an alternate operator detail layout
Operator app Fleet map · vehicle detail · maintenance triage Backend ops
neuron app · vehicle detail · iterations
Neuron vehicle detail bottom-sheet explorations, three layout variants tested for content prioritization, action prominence, and information density before the final version was selected
Bottom sheet explorations Iteration culture · tested layouts · chosen variant How decisions get made
Outcome · one system · both apps · embedded extension

In-house team intact. System consolidated.

Neuron kept their in-house designers; we extended their capacity. The rider app got a floating-panel home, Material-aligned input fields, a snackbar feedback layer, and a redesigned vehicle detail; the operator app got the same primitives plus a clearer fleet view; and a shared MapView pin vocabulary tied both apps together. Two apps, one design language, one team that didn’t have to grow to keep up.

Book a free sprint
Pilot week · on us

In-house team that needs more hands, not a replacement? Start with the same free week we ran for Neuron.

Five working days, a senior product designer who slots into your existing process, daily scrums, sprint queue, the tools you already use. If it doesn’t click, keep every file we ship.

  • Capped at 4 sprints / month
  • No card · NDA on request
Next case study → Case 10 · Lity · 2023–24

Mobile UX overhaul that cut drop-off from 51% to 14%.

A German EV-adoption mobile app, the designer Lity picked had prior fleet-management chops from this Neuron engagement. Verified Clutch 5.0, follow-on funding secured.

51→14% Drop-off cut
5.0 ★ Clutch verified
Mobility · Mobile UX · ClimateTech Read →