Back to Portfolio

Jollivry

Technical Case Study & System Architecture

The Problem

Localized food delivery lacked accuracy in fee calculation and robust tools for restaurant partners. Jollivry bridges this gap with a location-aware ecosystem tailored for high operational efficiency.

My Role

Lead Mobile Engineer and UI/UX Designer. Designed the interface from scratch and architected the notification and geospatial fee engines.

Key Engineering Decisions

1Reactive Notification Pipeline

Synchronized Firebase/FCM pushes with a localized Zustand store, ensuring restaurant partners receive real-time alerts even when the app is in the background.

2Geospatial Fee Calculation

Developed a custom engine leveraging expo-location and Google Places API to dynamically calculate delivery fees based on real-time distance from the restaurant.

Architecture Deep-Dive

System Design

Reactive mobile architecture powered by React Native and Expo. Leverages Orval for type-safe API synchronization and Zustand for decoupled state logic.

Storage Strategy

Dual-layer persistence strategy: Redis-cached menu queries for speed and localized AsyncStorage/Zustand persistence for offline-first performance.

Auth & Security

Biometric-secured authentication (Facial/Fingerprint) with JWT token rotation and secure session hydration.

Scalability

EAS-managed CI/CD with OTA (Over-The-Air) update capabilities and geospatial indexing for dynamic vendor discovery.

Outcome

"Delivered a production-ready ecosystem for consumers and partners, featuring biometric security and real-time order tracking."

What I Learned

Learned that developer-led design accelerates TTM. By building a reusable component library from day one, I was able to iterate on dual apps in parallel without duplicating logic.

Engineered with

React NativeExpoZustandTypeScriptTanStack QueryNativeWindFirebase