Product roadmap
We update this roadmap roughly every two weeks. Items move between sections as priorities shift based on what early customers ask for. If something is missing that you'd find useful, email hello@courrex.com — every suggestion is read.
Shipped (4)
Capacitor 7 wrapping the Next.js PWA. Background GPS via @capacitor-community/background-geolocation, native Taptic Engine haptics, APNs + FCM push.
Web-based operator console with live map, route management, driver tracking, in-app chat, inventory, accounting, CSV export.
Driver and operator messages auto-translate via Google Translate. Voice messages transcribed before translation.
Mapbox + Google Routes API integration with traffic-aware routing. Operators can flip the engine per driver.
Now (3)
TestFlight + Google Play Internal Testing for the first 10 driver fleets. Full App Store + Play Store production after ~30 days of stable real-world operation.
Real-time event delivery to operator-configured endpoints for stop.created, stop.completed, driver.online — already drafted in the API docs.
"Your delivery is 8 minutes away" SMS to end customers, sent automatically when the driver is en route. Optional per stop.
Next (4)
TOTP-based 2FA via Supabase Auth. Available on all tiers; required on Enterprise.
Searchable log of every sensitive operator action: driver code regeneration, data export, account deletion. Available to the dashboard's primary admin.
Multiple operator roles per organization: Admin, Dispatcher, Read-only. Replaces today's flat 'every operator can do everything' model.
Public status page powered by automated checks. Replaces today's manually-maintained /status.
Later (5)
Branded /track/<token> URL the Operator can SMS to recipients showing live driver position + ETA.
Driver collects a touch-screen signature at delivery, stored alongside the photo and timestamp.
For pharmacy, alcohol, and other verticals with regulatory requirements at handoff.
SAML / OIDC support for Okta, Azure AD, Google Workspace. Initially gated to Enterprise tier.
Customer notification templates and tracking page in the Operator's brand colors and domain.
Methodology
We don't commit to dates publicly. “Now” is actively in build (typically lands within 4 weeks). “Next” is queued (typically within 12 weeks). “Later” is planned but unscheduled.
We move things to “Now” based on three signals: paying customers explicitly asking, regulatory requirements we've become aware of, or technical foundations needed for downstream features. We do not run a public voting board because the customers who shout loudest are not always the customers with the most acute pain.