Transit accuracy, where it breaks.
Commuters don’t fail because they’re disorganized. They fail because bus and minibus information is incomplete, delayed, or wrong. Dolmapp is building a local-first routing and guidance layer for Istanbul—starting with the minibus network where uncertainty is highest.
People can’t locate buses when it matters.
At the stop, the question is simple: “Is my bus coming, and which one is actually going my way?” Today, commuters stitch together guesses: route names that match but directions that don’t, live maps that lag, and informal lines missing from official feeds.
Dolmapp turns uncertainty into a plan.
We don’t just show lines. We guide the actual decision: which minibus is correct, which stop is best to board, and when to move. The core advantage is route semantics—direction and ordered stops—so suggestions match how minibuses actually run.
A city-scale wedge, then repeatable playbook.
Istanbul is large enough for a city-specific product. The broader opportunity is a repeatable approach: take the hardest local layer (informal routes, weak feeds, messy stop names), build a verified dataset + routing logic, then expand to adjacent cities with similar complexity.
The data layer becomes the product.
The moat isn’t a generic UI. It’s a dataset with ordered stops, direction semantics, and routing heuristics tuned to the reality of how minibuses operate. That unlocks consumer trust, then B2B licensing and operational tools.
The problem is emotional—and measurable.
These are anonymized, illustrative excerpts from commuter interviews. Replace with verified quotes as the product ships at scale.
| Capability | Dolmapp | Moovit | Notes |
|---|---|---|---|
| Purpose-built for Istanbul minibus/dolmuş routing | Dolmapp is optimized for local line behavior and stop ordering; Moovit is multi-city and multi-modal. | ||
| Direction-aware ranking (destination after origin on stop order) | Stop-order logic is central to Dolmapp’s suggestions; other apps may not model informal routes the same way. | ||
| Board / alight guidance (best stop suggestions) | Dolmapp emphasizes where to get on/off, not only which line. | ||
| Fare estimate for informal transit | Dolmapp includes estimates tuned to local tariff logic where available. | ||
| Works when official real-time feeds are missing | Dolmapp can operate on curated stop/route datasets and inference; real-time requires integrations. | ||
| Global coverage and multi-modal trip planning | Moovit is a global incumbent; Dolmapp wins on depth in a single city segment. | ||
| Data layer as a licensable product (API / dashboards) | Both can support B2B offerings; Dolmapp’s differentiation is local accuracy and route semantics. |
Clear use of funds. Clear milestones.
This section is intentionally structured like a memo. Replace placeholders with your current round details and verified traction.
Invest in a calmer commute.
If you’re evaluating mobility infrastructure, consumer transit, or data products, Dolmapp is building a city-level accuracy layer where incumbents stay generic.