← All projects

Prototype Aug — Sep 2026

Meros.ai — offline-first AR + AI heritage guide

43 heritage sites in 5 cities, 5 languages, RAG with citations, LLM vision that is allowed to say 'not sure' — an MVP built solo in 8 weeks, now submitted to UzCombinator.

Role
Solo: product, architecture, backend, mobile, CMS, web, deploy
Stack
Flutter · FastAPI · PostgreSQL + PostGIS + pgvector · Redis · React CMS · Astro · Docker + Caddy · GitHub Actions
sites / cities / languages
43 / 5 / 5
tests (229 backend + 225 mobile)
454
language-switch resync
35 s → 7 s
TTS mispronunciations found in corpus
233
Catalogue: cities, categories, discovery of the day (emulator)
Catalogue: cities, categories, discovery of the day (emulator)
Place page: facts, audio guide, AR entry, story
Place page: facts, audio guide, AR entry, story
AR Scan: live camera, closed-list recognition, past-view chip
AR Scan: live camera, closed-list recognition, past-view chip
Time machine: guidance to the 1911 photographer's spot
Time machine: guidance to the 1911 photographer's spot
Map: nearest place, route, kind filters — works offline
Map: nearest place, route, kind filters — works offline
Trip planner: curated journeys + generated plan
Trip planner: curated journeys + generated plan
Web version (Astro SSR): place page with chapters and map
Web version (Astro SSR): place page with chapters and map
Admin CMS: 43 sites, 5 languages, review status
Admin CMS: 43 sites, 5 languages, review status
Ask the guide: answer from reviewed text with a citation, daily quota
Ask the guide: answer from reviewed text with a citation, daily quota
Audio guide: chapters, scrubber, 'Ask Meros AI'
Audio guide: chapters, scrubber, 'Ask Meros AI'

The problem

A tourist standing in front of the Registan has a phone with no signal and a generic chatbot that will happily invent dates. A guide app for Central Asian heritage needed three things nobody had put together: it must work offline, it must only say what reviewed sources say, and it must work in Uzbek, Russian, English, Indonesian and Arabic.

What I built

Where it stands

After the code was done I did the competitor analysis I should have done first. The state-run tourism platform covers booking, guides and tickets; two apps already promise AR and audio guides. Feature breadth is not a moat, so Meros does not compete there: it sells no bookings or tickets and is offered to tour operators, museums and hotels as a B2B licence — batches of pass codes, their own brand, usage statistics — with a focus on languages where human guides are scarce (Indonesian, Arabic).

Stage: MVP. The product works end to end, but it is not in the stores yet and has not been tested with real users. It is submitted to UzCombinator; the next step is a pilot with one to three tour operators in Samarkand, plus historian review of the content and native-speaker review of the Indonesian and Arabic translations.

What carries over

The offline sync core, the multi-tenant API, the CMS, auth with email codes and biometrics, and the deploy stack — a foundation I now reuse. And a rule: one day of market research before three weeks of code.