Oter Documentation
Internal documentation for the Oter platform — architecture, feature guides, ops runbooks, and domain references. Rendered by
docs-site/at the internal docs URL (IAP-protected).
Oter is a comprehensive life-management platform built with Kotlin Multiplatform. It runs on Android, iOS, Desktop, Web, and a Ktor server, and features a sophisticated balance-prediction engine for finance forecasting.
How this folder is organized
- overview/ — Product, architecture, domain models, prediction, UI/UX, integrations, testing, roadmap. Start here.
- features/ — Per-feature deep dives (finance, tasks, habits, journal, calendar, study, nutrition, timers, workout, work, books, notifications, dashboard, onboarding).
- architecture/ — Cross-cutting decisions: navigation, design-system conventions, offline/sync, plan patterns.
- design-system/ — Token reconciliation and prototype implementation status.
- integrations/ — External-service wiring (auth refresh tokens, FCM, WebSocket).
- infra/ — GCP / Cloud Run / Cloud SQL / CI runbooks.
- tech-debt/ — Live technical-debt and improvements register.
- agents/ — AI / dashboard agent prompts and reference.
- public/ — Source for the public-facing docs site (
oterapp.com/docs/). Internal readers don’t need this; it’s served by the samedocs-site/app viaDOCS_VARIANT=public.
Build modules
Note (2026-06): the app was consolidated onto a single shared UI. The old per-feature Android modules (
*_domain/*_data/*_presentation) and thecore-data/core-ui/navigation/test-corelibraries were removed — that feature code now lives inshared/.
- shared — Shared code (UI, view models, services) across all platforms
- composeApp — Compose Multiplatform application (Desktop, iOS, Android)
- androidApp — Android entry point (hosts the shared UI)
- server — Backend server implementation (Ktor)
- core — Core Android functionality