Pulak Singh

RideMate

One app for a club motorcycle ride: the plan, the money and the pack on the road.

Type
App UX and UI
Role
Art direction
Deliverables
Research, personas, flows, wireframes, design system, 14 screens plus 3 in Sunlight mode, clickable prototype
Tools
Figma
Typefaces
Barlow
Year
2026

Concept project — art directed by Pulak

A wall of RideMate app screens on a near-black ground, with lime buttons and a route map

The brief

RideMate is a concept app for motorcycle riding clubs. I run one, Motor Masters Riding Club in Bahraich, so the app is designed around a real ride: three days from Bahraich to Lohaghat in the Kumaon hills, 418 km each way, with 18 riders.

The problem

Today a ride like that runs on nine tools: a WhatsApp group, Google Forms and Sheets, UPI apps and five small web tools the club built. Plans get buried in chat and money is chased one transfer at a time. On the road nobody knows a rider has stopped until they are missing at the next regroup.

The nine tools a club ride runs on today: a WhatsApp group, Google Form, Google Sheets, UPI apps and five tools the club built itself

Research

The research is my own experience running the club’s rides, an audit of the tools we use and a scan of five apps riders already use, compared from each app’s own website in November 2026. Ride apps show riders on a map and bill-splitting apps split bills. None handles the money and the road together.

Three personas: the captain, the regular rider and the new rider
User flows for three journeys: joining a ride, ride day and the captain
Grey-box wireframes of the key screens

Plan and pay

From the club’s invite to a paid seat in four screens. The fee is split line by line before payment, club fund included: riders accept a margin they can see and distrust one they discover.

Welcome screen opening from the club’s invite
Home screen with the next ride and a ready check
Ride page with the route map and the plan by day
Check and pay screen with the fee split line by line
Confirmation screen with the ride pass
Ride board with one-way updates from the captain

Ride day

The pack is one line on the map. When a rider drops too far behind, the gap turns amber and the sweep is told first. SOS needs a three-second hold, so a pocket cannot press it.

Buttons are 64 pt on ride-day screens for gloved hands, and nothing on ride day needs typing. Hill roads drop signal, so every position shows when it was last updated.

Live map with the pack as one line
Gap alert: a rider is 2.1 km behind the sweep
Hold for SOS screen
SOS sent, with the nearest hospital
After the ride: everyone’s home

Sunlight mode

Every colour is a Figma variable with a Dark and a Sunlight value, so the map, the route and the interface switch together. In Sunlight the route turns black with a lime edge, because lime disappears on a pale map in direct sun.

Live map in Dark modeLive map in Sunlight mode

The captain

Collections, reminders and a live ledger replace the form, the sheet and the screenshots. Net balance is collected minus spent, the same sum the club’s expense sheet already uses.

Create ride screen with regroup points
Collections: who has paid and who has not
Ride ledger: spent against budget

Design system

Type is Barlow, a typeface that draws on road signs and number plates. A near-black base suits dawn starts and night riding. Hi-vis lime marks primary actions and the route, amber means attention, and red means SOS and nothing else. The icon set is 52 custom icons on a 24 pt grid.

The design system: colour variables, Barlow type scale, icons and components

Prototype

The Figma file holds a clickable prototype with three flows and 26 connections. The Sunlight switch runs on variable modes, and screens are built from shared components with auto layout. Map data © OpenStreetMap contributors.

More from RideMate