Case study · 04 / 12
Pod
A mobile app engineered to stay fast, online or off
- Year
- 2026
- Focus
- React Native
- Status
- In development
A cross-platform mobile app for iOS and Android, built in React Native and Expo on a Supabase back end: 69 screens across 13 sprints, written in strict TypeScript.
A mobile app is judged in its worst moment: a cold start on a mid-range phone, a long list scrolled fast, a message sent as the signal drops. So I engineered for those moments first. The app is one TypeScript codebase for both platforms. Screens never talk to the database directly: they ask a repository, and the repository can be the real back end or a mock, which let me build and test every screen before the server existed. Animation runs off the JavaScript thread, lists recycle their rows, pictures arrive at the size they are shown, and anything written offline is queued, encrypted and sent once when the connection returns.
What it does
- 01One codebase for iOS and Android, with file-based routing and typed routes
- 02A hand-built component library on a single token theme, in light and dark
- 03Animation and gestures that run on the UI thread
- 04Long lists that recycle their rows, so memory stays flat however far you scroll
- 05An offline cache that keeps the app readable with no connection
- 06A send queue that holds writes made offline and delivers each exactly once
- 07Real-time updates and live audio over WebRTC
- 08A back end where every table is locked by row-level security
How it was solved
- 01Animated only transform and opacity through Reanimated shared values, so no frame waits on layout or on JavaScript
- 02Drew the launch sequence in Skia as a recorded picture per frame, paused whenever the app is in the background to save battery
- 03Used FlashList with typed rows so a recycled cell always matches its content, which keeps fast scrolling free of blank flashes
- 04Resized every upload on the device into a large and a small copy, and asked lists for the small one: less data, faster first paint
- 05Persisted the query cache for 24 hours and paused reads when offline, so a lost signal shows saved data, not errors
- 06Queued offline writes with a client id the server de-duplicates on, so a retry can never post twice
- 07Sealed the saved cache with XChaCha20-Poly1305, with the key in the phone's keychain
- 08Put the database behind functions: the app calls typed procedures and never touches a table, and paging uses keyset cursors, which stay fast at any depth
- 09Held the splash screen until fonts, session and theme were ready, so the first frame is never the wrong one
- 10Built against a repository interface with mock and live implementations, so screens and tests never depend on the network
69 screens built over 13 sprints, backed by 30 database migrations and more than 60 test files, with accessibility labels and reduced-motion handling throughout.
Stack
- Languages
- TypeScript (strict)SQL (PL/pgSQL)
- Mobile
- React Native 0.88Expo SDK 58React 19Expo RouterReact Compiler
- Motion and graphics
- Reanimated 4React Native Skiareact-native-svgExpo Haptics
- Data
- TanStack Query v5Persisted query cacheFlashListExpo ImageZod
- Back-end
- SupabasePostgreSQLRow-level securitySupabase RealtimeSupabase StorageDeno Edge FunctionsLiveKit (WebRTC)
- Security
- XChaCha20-Poly1305Expo SecureStoreKeychain / Keystore
- Testing and delivery
- Jest 30React Native Testing LibraryESLintPrettierEAS Buildpnpm
- #react-native
- #expo
- #typescript
- #supabase
- #offline-first
- #mobile
Not public yet. The link goes here the day it launches.