Zones, speeds and caps the city draws itself, open anonymised data, orderly yellow/black-stripe parking — then a 90-day pilot before you decide.
Pre-launch preview — no announced partnerships; figures are estimates.
Every rule is enforced on the scooter itself — not left to rider goodwill.
No-ride, no-park and mandatory bays — drawn on the map, live on every scooter within minutes.
Scooters stop at the boundary on their owne.g. 10 km/h on the corniche 4–10 pm, 20 km/h elsewhere.
Enforced by the motor, not the appA ceiling per district — and a floor in under-served areas so the fleet does not pile up downtown.
Rebalanced nightly by juicersPause an area for an event, Friday prayers or road works — in one click.
Nearby riders are notifiedWe use open standards city transport teams already know, so the city needs no DOZ-specific system.
Every ride ends with a photo. The city sees each violation with its photo and location.
The lock will not close outside an allowed zone, and good parking earns XP. Reports reach the nearest juicer with a published deadline.
Rider parking guideDistricts, zones, caps and success KPIs are agreed before a single scooter.
2 weeksBays painted in yellow/black stripe, signs installed, local juicers trained.
4 weeksAbout 150 scooters in two districts, a weekly report and a live city dashboard.
90 daysResults vs the agreed KPIs. The city decides: expand, adjust or stop.
2 weeksThe cities team replies within 5 business days.
No. DOZ funds the fleet and operations. We propose a per-scooter fee that goes to bay upkeep — the city decides.
Not yet. This is a pre-launch preview; the districts and figures here are proposals for discussion.
Scooters are removed within 72 hours and bays restored, with no penalty to the city.
GBFS (MobilityData) for public availability and MDS (Open Mobility Foundation) for city data — two open standards used by many cities.