Ravine · ADR 0001

1.A native Swift app on memo's backend.!?

The problem

A map-first guide needs a map that feels like the platform's, and a server that already knows how to be correct.

The options

Expo again, like memo, sharing a client toolchain; a web app; native SwiftUI on the server stack memo already proved.

The move

SwiftUI, for the map and the platform's own materials, on FastAPI, SQLAlchemy and Postgres with the same migration and isolation patterns as memo.

What we accepted

Two client codebases in two languages, and no shared UI with memo. Worth it for an app whose whole surface is a map.

When we would revisit

If an Android version is ever asked for, the answer is a second native app, not a rewrite.

Back to Ravine