How okunaorg/okuna-app works
Project type and purpose
• This is a cross-platform mobile client (Flutter) for the Okuna social network that consumes a separate “okuna-api” backend.
• It provides UI pages, widget libraries, services to make HTTP calls, native plugins, localization, and platform‐specific Android/iOS code.
File structure
• Top-level:
• android/ & ios/ — native project files, Gradle, Xcode, Fastlane, platform plugins (OneSignal, image conversion, share).
• lib/ — main Flutter code, subdivided into pages (UI screens), widgets (reusable UI), models (data classes), services (business logic & HTTP clients), plugins (Dart wrappers around native code), delegates (localization), provider.dart (DI).
• assets/ — fonts, images, i18n message files.
• bin/ — build scripts (locale generation).
• configuration: .env, Pipfile, Makefile, pubspec.yaml.
• Architectural patterns:
• UI layer (pages + widgets)
• Domain/data layer (services + models)
• HTTP client (httpie.dart) to talk to backend
• Localization layer (intl + custom delegates)
• Native bridge layer (plugins)
README for additional insights
• Confirms Flutter‐based mobile app
• Depends on external okuna-api server
• Uses flavors (development/production), environment variables (.env.json)
• Integrates OneSignal, Intercom, universal links handlers, push notifications
• Describes locale generation workflow