Writing codeShipping productsWeb & mobileReact NativeNext.jsVueSupabaseAI-driven workflowsProduct thinkingLeading teamsBreaking codeFixing codeOpen to roles
r.saseun
Back to Work

Operations platform · Transportation · 2025

CrewsLink.

A real-time platform connecting flight crew journeys with dispatch operations and driver workflows.

Role
Software Engineer
Scope
Product, frontend, backend and mobile
Year
2025
Team
Built with the team at Tempo Labs
CrewsLink interface

In short.

Project
A real-time platform connecting dispatch operations, drivers and airline crew journeys.
Problem
CrewsLink relied on a paid third-party system and wanted a platform it owned, with control over its operational data.
What I did
Working with the team at Tempo Labs, I built the driver mobile app, dispatcher operations application and crew-facing trip updates, contributing across the frontend and backend.
Result
A driver app available on the App Store, a dispatch dashboard used to manage more than 500 drivers and crew members across multiple international flights, and a new customer-facing website.

Chapter 01

An owned platform for crew transportation

CrewsLink coordinates ground transportation for airline crews. Dispatchers manage the trips, drivers carry them out, and crew members need clear pickup information and updates as their journeys change.

The company was using an existing SaaS product to run these operations. It wanted to bring that capability into a system of its own, with control over its data and where it was stored, rather than depending on the existing provider.

I worked on the project as a software engineer at Tempo Labs, alongside other team members. My contribution covered the driver mobile application, the dispatcher operations application and crew-facing trip updates, with work across the frontend and backend.

Chapter 02

From a third-party service to an owned product

The starting point was an operational system that CrewsLink was already paying to use. The goal was to build the capabilities the business needed into a platform it could own and develop around its operations.

Ownership of the product and its data

CrewsLink wanted control over its operational data and the ability to store it on its own servers. Replacing the existing SaaS service meant bringing the dispatch and driver workflows into the new product.

Connected dispatch and driver experiences

The dispatcher dashboard and driver app had to support the same transport operation. Dispatchers needed to manage crew trips, while the mobile application and crew-facing updates connected those trips to the people carrying them out and travelling on them.

Support for more than one company

We built the platform as a multi-tenant system. Alongside CrewsLink, other transport companies working with it or running similar operations could use the dashboard for their own businesses.

Chapter 03

Building across web, backend and mobile

I worked across the frontend and backend using React and Supabase, and built the mobile application with React Native. This let us prototype quickly while developing one mobile codebase for both iOS and Android. I used AI-assisted workflows throughout development.

Resend handled email, and Vercel hosted the web application.

The dispatcher operations application gave the team a place to manage crew transportation. The driver app supported the driver side of those trips, with crew-facing updates completing the connection between dispatch and the journey.

The delivered product included a driver app available on the App Store, the dispatch dashboard and a new customer-facing website. The dashboard was used to manage more than 500 drivers and crew members across multiple international flights. Development continued as an ongoing project.

The web application

CrewsLink Connect web sign-in with Google and email options
The sign-in experience for the CrewsLink Connect operations platform.

The driver mobile app

CrewsLink driver app welcome screen with email and password sign-in
Sign in to the driver app.
Driver app showing an assigned trip with pickup, destination, time and passenger count
See assigned trips and pickup information.
Driver trip details with a route map, booking information and a swipe-to-start control
View the route, trip details and current status.
Driver profile with on-duty and off-duty controls, vehicle details and contact settings
Manage availability, vehicle and profile settings.

Chapter 04

A consistent component system

The designer established the design system. I followed that system when building the React and React Native interfaces, creating reusable components and documenting them for the team.

On the web, we used shadcn/ui and established React accessibility patterns to support accessible components. Across web and mobile, the work focused on translating the designer's system into consistent interfaces and documented components that the team could build on.

Credits

Software engineering
Richard Saseun, alongside the team at Tempo Labs
Design system
Created by the project designer

Keep exploring