How jsdwrld/airise works
Project type and purpose
• This is a full-stack, mobile-first health & fitness platform with a Kotlin Multiplatform (Compose) frontend (Android & iOS) and a .NET 9 RESTful backend.
• Purpose: Deliver AI-driven coaching, progress tracking, meal planning, social features, and wearable integrations.
File structure
• Frontend
• composeApp (commonMain, androidMain, iosMain) – shared UI, business logic, data layer
• platform-specific modules (Room database on Android, CoreData on iOS)
• network clients, DTOs, repository, cache interfaces and implementations
• generativeAi, notifications, health integrations
• Backend
• Controllers (AuthController, ChallengeController, User/*) – HTTP endpoints
• Services (AuthService, ChallengeService, UserDataService, etc.) – business logic
• Data layer (ChallengeData, ProgramData) & MongoDBService – persistence abstractions
• Models & DTOs
• Config & deployment files: appsettings.json, launchSettings.json, Azure deployment notes
• Tests: xUnit suite for backend, commonTests for frontend business logic
Key architectural insights from README
• Monolithic .NET API hosting multiple resource controllers
• MongoDB Atlas for core data, SupaBase for auth/real-time features
• Kotlin Multiplatform: common UI and domain code, platform adapters for Android/iOS
• External services: Google Gemini AI, Google Fit, Apple Health, email/push notifications