da9172e594
Build a separate driver app from the same codebase: APP_VARIANT=driver (app.config.ts) sets its name, bundle ID and scheme, eas.json gets driver build profiles, and Stack.Protected keeps each app to its own screens. metro.config.js keys Metro's cache by variant so switching apps never serves the other's baked-in config. Drivers get ride requests only in driving mode. While driving they see a waiting animation or, on a ride, turn-by-turn directions; requests slide up over either without disturbing it. Accepting mid-ride queues the ride (one in progress plus one queued). Going offline or online mid-round leaves or joins it. Simulated phones no longer touch the location API: each sits at a mocked position from its URL (default downtown San Francisco). Phone specs in sim.html move to named key=value options. Scenarios cover driving mode, interruptions, the ride queue and mocked location, each with a slow version. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
34 lines
723 B
JSON
34 lines
723 B
JSON
{
|
|
"cli": {
|
|
"appVersionSource": "remote"
|
|
},
|
|
"build": {
|
|
"development": {
|
|
"developmentClient": true,
|
|
"distribution": "internal",
|
|
"env": { "APP_VARIANT": "rider" }
|
|
},
|
|
"preview": {
|
|
"distribution": "internal",
|
|
"env": { "APP_VARIANT": "rider" }
|
|
},
|
|
"production": {
|
|
"env": { "APP_VARIANT": "rider" }
|
|
},
|
|
"driver-development": {
|
|
"extends": "development",
|
|
"env": { "APP_VARIANT": "driver" }
|
|
},
|
|
"driver-preview": {
|
|
"extends": "preview",
|
|
"env": { "APP_VARIANT": "driver" }
|
|
},
|
|
"driver-production": {
|
|
"extends": "production",
|
|
"env": { "APP_VARIANT": "driver" }
|
|
}
|
|
},
|
|
"submit": {
|
|
"production": {}
|
|
}
|
|
}
|