live
BorderSmart
Preview unavailable The details below still apply. 
Which crossing, which lane, when to leave.
A border-wait planning product for northbound San Ysidro and Otay Mesa crossings. This case study covers the mobile app, and the service and operator tools behind it stay private.
Available on the App Store and Google Play.
Read case study brief · what i owned · key decisions · what shipped · evidence · implementation
The problem
A border wait isn’t one number. Travelers pick between crossings and lane types while the signal keeps changing, and the existing status checks make that comparison hard to read and harder to act on.
What I owned
- I did the product engineering for the mobile workflows shown here: saved lanes, crossing and lane comparison, target alerts, crossing start, and commuter preferences.
Key decisions
- Put every supported crossing and lane on one board, so travelers don’t have to check them one at a time.
- Show a likely range, confidence, freshness, and trend next to the estimate, not a bare wait number on its own.
- Turn watching the wait into something you can act on, with saved lanes, target alerts, crossing start, quiet hours, and optional GPS assistance.
What shipped
- Planning guidance shown with a likely range, confidence, freshness, and trend.
- Saved-lane status, six-way lane comparison, target alerts, crossing start, quiet hours, GPS assistance, and language preferences, all in one app.
Evidence
- Product captures show the My Lane, lane-comparison Board, Alerts, and Settings workflows.
- The Board compares General, Ready, and SENTRI lanes at both supported crossings and points out the fastest option right now.
- Settings show primary-lane preferences, notification controls, quiet hours, GPS assistance, and a choice of English or Spanish.
Implementation
- Expo
- Fastify
- Next.js
- Postgres
- TypeScript
Captures
