Owner: Engineering Team | Last Updated: 2026-01-30 | Status: Active
The WWAI Mobile App is the cross-platform mobile client for the WWAI platform, built with Flutter and Dart. It provides iOS and Android users with the full suite of AI text humanization and detection tools, document history management, authentication, and subscription payments. The mobile app consumes the same Django REST API backend as all other WWAI frontends, ensuring feature parity and consistent business logic.
Repository: To be confirmed when codebase is provided
Primary Branch: main
Framework: Flutter SDK (Dart)
Platforms: iOS, Android
| Technology | Purpose |
|---|---|
| Flutter SDK | Cross-platform UI framework |
| Dart | Programming language |
| Flutter / Material Design | UI components and theming |
Draft: Full dependency list and version numbers will be documented when the codebase is analyzed.
| Feature | Description | Status |
|---|---|---|
| Humanizer | AI text humanization with configurable readability, purpose, and anti-detection strength | Active |
| Detector | AI content detection across multiple detector engines | Active |
| Document History | View, manage, and search past humanization/detection sessions | Active |
| Authentication | Login/signup with email and social providers (Google, Facebook) | Active |
| Payments | In-app subscription management and plan selection | Active |
| Settings | Account settings, billing, profile management | Active |
Draft: Detailed feature documentation will be created when the mobile codebase is analyzed. Each feature listed above will have its own sub-page with UI flows, state management details, and API integration notes.
Mobile Device (iOS / Android)
|
v
Flutter App
|-- Screens / Pages (UI Layer)
|-- State Management (Provider / Bloc / Riverpod - TBD)
|-- API Service Layer (HTTP Client)
|-- Local Storage (Secure Storage for tokens)
|
v
Django REST API (Backend)
|-- /api/user/* (auth, profile)
|-- /api/feature/* (humanizer, detector, history)
|-- /api/payments/* (checkout, pricing)
Draft: The specific state management approach (Provider, Bloc, Riverpod, or other) and navigation pattern will be documented when the codebase is analyzed.
Draft: This section will be updated when the codebase is provided. Expected topics:
- State management pattern
- Navigation / routing approach
- Dependency injection setup
- Repository pattern for data access
- Error handling strategy
- Offline support (if applicable)
Draft: This section will be updated with project-specific details when the codebase is provided.
| Tool | Purpose |
|---|---|
| Flutter SDK | Framework runtime |
| Dart SDK | Included with Flutter |
| Android Studio | Android development & emulator |
| Xcode (macOS only) | iOS development & simulator |
| VS Code or Android Studio | IDE with Flutter extensions |
# 1. Clone the repository
git clone <repository-url>
cd <mobile-app-directory>
# 2. Install Flutter dependencies
flutter pub get
# 3. Configure environment
# Copy and configure environment files (details TBD)
# 4. Run on device/emulator
flutter run
# 5. Run on specific platform
flutter run -d ios
flutter run -d android
Draft: Environment variable configuration, API base URLs, and build flavors will be documented when the codebase is analyzed.
The mobile app communicates with the same Django REST API backend used by all WWAI frontends. All API calls follow the established conventions:
application/jsonlimit / offset query parameters| Endpoint Pattern | Purpose |
|---|---|
/api/user/login/ |
Authentication |
/api/user/register/ |
User registration |
/api/user/token/refresh/ |
JWT token refresh |
/api/feature/humanizer/ |
Text humanization |
/api/feature/detector/ |
AI detection |
/api/feature/history/ |
Document history |
/api/payments/checkout/ |
Subscription checkout |
/api/payments/pricing/ |
Plan and pricing data |
Draft: Complete API integration mapping with request/response formats will be documented when the codebase is analyzed.
Draft: This section will be updated when the codebase is provided. Expected topics:
- Unit testing strategy (flutter_test)
- Widget testing approach
- Integration testing setup
- Test coverage requirements
- CI test execution
# Run all tests
flutter test
# Run tests with coverage
flutter test --coverage
# Run specific test file
flutter test test/<test_file>_test.dart
Draft: This section will be updated when the codebase and CI/CD pipeline are analyzed. Expected topics:
- Build variants / flavors (dev, staging, production)
- iOS App Store deployment process
- Google Play Store deployment process
- Code signing configuration
- CI/CD pipeline for mobile builds
- Version management and release tagging
| Platform | Distribution | Notes |
|---|---|---|
| iOS | App Store | Requires Apple Developer Account, provisioning profiles |
| Android | Google Play Store | Requires signing key, Play Console access |
Draft: This section will be populated with common issues and solutions as they are identified during codebase analysis and team input.
| Issue | Possible Cause | Resolution |
|---|---|---|
| Build fails on iOS | CocoaPods not installed | Run pod install in ios/ directory |
| Build fails on Android | SDK version mismatch | Check android/build.gradle for SDK requirements |
| API connection fails | Wrong environment URL | Verify API base URL in environment config |
| Auth token expired | JWT refresh not triggered | Check token refresh logic in API service layer |
| Date | Author | Change |
|---|---|---|
| 2026-01-30 | Admin | Initial creation |
Up: WalterWrites