Internet access is necessary. It doesn't make every phone reachable, discoverable or awake.
Experimental path
Phones only
Use participants' devices for discovery and connection support. Worth testing, but not a dependable public-service promise.
Finding unknown nearby drivers still needs a discovery mechanism.
Direct connections need signaling; some network combinations need a relay.
Phones that sleep, disconnect or run out of battery weaken the network.
Best used for a bounded connection experiment.
Recommended direction
Small shared backend
Phones + a small service
Keep most work local. Use a small backend for the jobs that need a reachable, consistent coordinator.
Phones: interface, location permissions, fare negotiation and local history.
Backend: find online drivers, deliver requests and confirm exactly one acceptance.
Rider pays driver directly. No platform fare deduction in the proposed model.
Relaxes "no server", preserves "no per-ride commission".
01Rider requests
Pickup and fare offer
→
02Shared service
Discovery and matching
→
03Driver accepts
One confirmed match
Android permits suitable foreground location activity with the right permissions. Ordinary background location is limited; iOS also restricts background work. Keeping mobile data or Wi-Fi on does not remove these constraints. Community-run nodes are still infrastructure. No blockchain or token is needed for this design.
Architecture explorer
Choose the constraint.
This comparison changes only this page. It does not connect devices.
Distributed roles, fragile availability
Participants provide discovery and connection support. Reachability, sleeping devices and network churn remain the experiment. No dependable public-service claim.