[Draft note for Manuel]: mirror of the ES version — backed by the real mobile/ app you built for this very site (Phase 11), zero backend changes required.

I build mobile apps with Expo/React Native when you already have (or are about to have) a backend and a web app, and need a native app without duplicating business logic or maintaining two separate API contracts — the app consumes the same backend, with its own TypeScript client regenerated from the same spec.

This is exactly the pattern I used to build this site's own mobile app: same Java/Spring Boot backend, same three sections, zero backend changes to support the mobile version. If your team already invested in a solid API, you shouldn't have to rebuild it to get an app.

What's typically included:

iOS/Android app with Expo/React Native, built on your existing API (or one we design together).
Native navigation, i18n if your product needs it, and forms/flows with the same validation your backend already enforces.
Third-party integrations when the project calls for them (push notifications, authentication, payments).

What's not included by default: App Store/Play Store publishing (coordinated separately, depending on your developer accounts) or visual design from scratch (I work best from an already-defined design system, or we define one together as part of the scope).

Have a web product you need on mobile without rebuilding everything? Let's talk.