Copart, Member Mobile
Over-the-air updates
I built the app and server path for shipping JavaScript fixes to the Copart app without waiting for an app store release.
- Time for a JS fix to reach users
- Minutes
- Role
- Designed and built it
- Built with
- React Native
- OTA (expo-updates)
- Node.js
- CI
- SignedEvery bundle is code-signed, so an update is trusted before it runs.
- StagedUpdates roll out in stages.
- GatedA CI gate rejects any bundle that needs a store release.
- TestedEach release runs end-to-end signature checks and unit tests.
Shipping a JavaScript fix
- CI gateNo native changes, so it can ship over the air.
- SignedThe app checks the signature before it runs the code.
- StagedIt reaches a few people first, then everyone.
- InstalledThe fix is on the phone in minutes.
The store route waits on app review, then on each person updating the app.
Problem
The Copart Member Mobile app needed a way to ship JavaScript fixes without waiting for an app store release. An update had to be trusted before it ran, and changes that needed native code had to stay on the store-release path.
What I built
I built the over-the-air path on both sides: expo-updates in the React Native app, and the Node.js server behind it. Bundles are code-signed and roll out in stages. A CI gate rejects any bundle that needs a store release. Each release runs end-to-end signature checks and unit tests.
Result
JavaScript fixes for the Copart app now reach users in minutes.
I’ve kept this to what my resume says. Ask me for more detail when we talk.