ride.Concept stage

04 / A staged plan

Prove one thing
at a time.

No launch date, service area or app release is promised.

  1. 01
    Current scope

    Explain the concept

    This static website: the model, technical limits, rough costs and open questions. No site accounts, tracking or submission of demo inputs. Hosting providers may process request metadata.

  2. 02
    Future work

    Build a connection proof

    Two Android phones on different networks. Test discovery, duplicate acceptance prevention, expiry, screen-off behavior and reconnects before building a whole app.

  3. 03
    Only after the proof

    Run a closed mock-ride pilot

    Consenting known testers, one small area, no public passengers. Measure delivery, battery use, recovery and costs. A pilot needs its own scope and approval.

  4. 04
    Separate decision

    Assess public operation

    Verify applicable Nepal provincial rules, permissions and insurance. Price verification and support, agree governance and funding, and test safety and incident procedures.

05 / Before real passengers

Trust needs more
than a matching algorithm.

Protect location

Use coarse location before matching. Share exact pickup only with appropriate parties. Don't distribute everyone's locations, identity documents or trip history to random phones.

Verify and support

Driver and vehicle checks, reporting, fraud handling, disputes and incident support need real procedures and resources. An SOS button is not guaranteed rescue.

Check local requirements

Rules and insurance need verification for the intended province and operation. Zero commission or a free app does not establish a legal exemption.