Rydex

01 · Overview

About the project

Rydex is a ride-hailing platform built around reliability and safety for both riders and drivers. The product delivers smooth booking flows, live trip tracking and a driver experience designed around actual on-road ergonomics rather than back-office assumptions.

The system pairs rider and driver mobile apps with backend services that manage dispatch, state transitions, authentication and live location streams across active trips.

02 · Problem

What we set out to solve

Existing ride-hailing experiences often leave riders uncertain about driver arrivals, ETAs and trip progress while on the road. Drivers face distracting interfaces with poor one-hand usability, unclear earnings breakdowns and suboptimal routing during active jobs.

Safety concerns compound these issues — both sides need verifiable identity, clear sharing of trip information with contacts and predictable escalation flows when something goes wrong.

03 · My Role

What I worked on

Full stack engineering across the rider and driver mobile applications, mapping integrations and backend trip state pipelines. I handled the React Native app architecture, map SDK integrations, realtime tracking channels and secure authentication flows for both user roles.

04 · Technologies

Stack and how each piece is used

React Native Cross-platform mobile applications for iOS and Android, separate rider and driver app variants with role-tailored UX.

Maps Map SDK integration for address search, route display, pick-up/drop-off pinning and live driver position rendering on the rider map.

Realtime tracking Continuous driver location streaming and trip progress updates to the rider client through realtime channels.

Secure Authentication Role-aware authentication with token-based sessions, identity verification and protected access to trip and profile endpoints.

05 · Architecture & Technical Approach

How the system is structured

Rydex follows a layered REST-native architecture where backend services own trip lifecycle, pricing and dispatch state, exposed through authenticated APIs consumed by the React Native rider and driver apps. Authentication middleware gates all role-specific endpoints and ensures driver sessions can only mutate their own trip and availability records.

Realtime tracking is handled via dedicated streaming channels feeding location updates into the live trip views, with the mapping SDK handling route geometry, ETA calculations and on-map annotations for both the rider and driver experiences.

06 · Key Features

What the product delivers

Smooth booking flows with address search, ride type selection and upfront pricing
Clear realtime trip tracking with driver position and ETA updates
Role-specific mobile apps for riders and drivers with optimized ergonomics
Secure authentication and identity verification for both parties
Integrated mapping for pick-up, route visualization and drop-off
Reliability and safety-focused product design across the booking lifecycle

07 · Engineering Challenges

Hard problems we had to solve

Realtime location update performance across spotty mobile networks and varied GPS accuracy
Mobile UX for drivers requiring one-handed operation, glanceable information and minimal in-trip distraction
Map SDK rendering performance with frequent marker redraws and route polyline updates
Secure authentication patterns that stay ergonomic for daily driver logins and quick rider access
Offline resilience for trip state so drivers don't lose accepted work during network dropouts

08 · Solutions

How we addressed them

Clean architecture with clear separation between transport layer (location streaming), trip state model and UI rendering
Map SDK integration patterns with throttled updates, batched redraws and viewport-aware marker management
Standardized secure authentication flows with token refresh, role-based scopes and session resilience on app restart
Local persistence and resumable upload patterns on the mobile clients for offline trip state recovery
Background notification and location frameworks wired in to keep trip state synchronized outside the foreground app

09 · Outcome

What was delivered

Built and shipped the Rydex ride-hailing platform with end-to-end rider and driver flows, realtime trip tracking and secure role-based access. The product applies clean mobile architecture, sensible map SDK usage and authentication patterns that let riders and drivers complete trips with confidence.

10 · Lessons Learned

What I'd do differently next time

Driver UX is a different discipline from rider UX — decisions that feel fine in a passenger seat often fail the one-hand, low-attention test of actually driving.
Reliability in mobility products means designing for network failure as the default, not the exception; trip state must reconcile gracefully.
Mapping integrations benefit from early, real-world performance testing — simulators hide the jitter, GPS drift and viewport churn of actual city usage.

Back to all projects Talk about a similar project