Cyprian Aarons

03 · Real-Time Operations

CST Goods-In case study.

A real-time mobile operations platform that cut logistics workflow processing time by 80%.

Senior Full-Stack Developer (Contract)2024Shipped

Project overview

What was built and why it mattered.

A concise project view first, then the longer narrative and implementation notes below.

CST needed a reliable front-desk and goods-in system to replace fragmented visitor, delivery, pass, and device workflows. The challenge was to improve processing speed without creating another disconnected system for staff to maintain.

I built a mobile-first React Native application backed by FastAPI and Supabase, with WebSocket updates, HaloPSA integration, and notifications through Slack and SendGrid. The system centralised visitor check-in, pass availability, deliveries, purchase-order lookup, device intake, and exception handling.

The resulting workflow reduced processing time by 80%; a focused performance pass also improved API response time from 500ms to 200ms. It is evidence of delivery across product workflows, asynchronous backend services, real-time state, integrations, and production operations.

Key systems

The pieces that carried the product.

This is the short implementation map before the fuller markdown write-up.

01

MOBILE_OPERATIONS

React Native and Expo Router deliver quick reception workflows across phone, tablet, and web-ready surfaces.

02

REAL_TIME_STATE

WebSockets, heartbeats, reconnect behavior, and Redux state keep visitor and pass information current during active operations.

03

WORKFLOW_INTEGRATIONS

HaloPSA, Slack, SendGrid, Cloudinary, and FastAPI/Supabase services connect the mobile workflow to existing business systems.

04

MEASURABLE_DELIVERY

Processing time fell 80%, while backend and data-fetching changes brought API response time from 500ms to 200ms.

Detailed notes

Long-form case study

The fuller project narrative, results, and architecture notes from the markdown source.

The problem

CST’s front-desk and goods-in teams were coordinating visitor check-in, passes, deliveries, purchase orders, device intake, and staff notifications across disconnected processes. That slowed down reception work, obscured what was happening on site, and created too much manual follow-up.

My role

As the senior full-stack contractor, I built the mobile application architecture and its service integrations. I focused on turning several time-sensitive workflows into one reliable, mobile-first operating surface while retaining the connections to the company’s existing systems.

The system

What I built

One workflow surface for busy teams

The application combines visitor and contractor check-in, live pass inventory, package registration, purchase-order search, unexpected deliveries, device check-in, and collection status. Staff do not have to move between separate systems to complete routine front-desk work.

Real-time information people can trust

The dashboard tracks current visitors, available passes, and operational activity through WebSocket connections. Heartbeats, reconnect behavior, refresh fallbacks, and centralized state management were included so the live view stays useful when the network is not perfect.

Integrations instead of another data island

HaloPSA, Slack, SendGrid, Cloudinary, and FastAPI/Supabase services connect the front-desk app to the workflows already used by the wider business. Visitors and deliveries can trigger the notifications that matter to staff, rather than adding another manual step.

A reliable mobile client

The React Native and Expo implementation uses TypeScript, Redux Toolkit, a centralized Axios layer, token refresh, retries, request IDs, and limited offline queueing for critical actions. Those details keep the feature screens fast and keep failure modes contained.

Results

  • Cut logistics workflow processing time by 80%.
  • Improved API response time from 500ms to 200ms through backend and data-fetching improvements.
  • Created one practical operations surface for reception, deliveries, passes, and device workflows.

Stack

  • React Native, Expo Router, TypeScript, Redux Toolkit, NativeWind, Gluestack UI.
  • FastAPI, Supabase, WebSockets, REST APIs.
  • HaloPSA, Slack, SendGrid, Cloudinary, and Apple Sign In.

What this case study proves

CST is evidence that I can take ownership beyond an AI layer: map real operational work, build reliable async services and integrations, ship a production-minded mobile experience, and measure the resulting improvement.