OUTCOMES
What this Prompt helps you deliver
- The Android app runs on an emulator or device
- Gradle compilation passes
BEFORE YOU START
Before you start
- A compatible JDK and Android SDK are installed
- The backend API is reachable
What AI should inspect first
apps/tabtin-androidAGENTS.mddocs/agent/commands.mdREADY TO RUN
Complete Prompt
Copy the complete Prompt with its execution and acceptance boundaries.
Start the TabTin Android client so I can adapt it into an industry product. Complete the environment audit, Gradle build, backend connection, and device run from the repository’s actual configuration.
Read AGENTS.md, docs/agent/commands.md, mobile rules, and Gradle configuration under apps/tabtin-android. Inspect JDK, Android SDK, Build Tools, Gradle Wrapper, and emulator/device state. Ensure the API is reachable from that target and review cleartext/network-security settings. Do not upgrade the whole Android toolchain to hide one local error.
Identify app modules, build variants, minimum SDK, Compose/UI stack, and environment source. Use the repository Gradle Wrapper to resolve dependencies and build the development variant. Make the smallest fix for compiler, resources, Manifest, Kotlin, or dependency conflicts while preserving user work. Start an emulator or connect a device, install the correct variant, then verify sign-in, Organization entry, navigation, and one core data screen over the real network/state flow.
After each change run the relevant Gradle compile or test task. Inspect application crashes and network failures in adb logcat. Check rotation, back navigation, system permissions, and basic window adaptation. State any push or vendor capability that the current device cannot cover.
Report JDK/SDK, variant, device, backend, Gradle result, screens verified, and remaining limits. Do not change release signing or package name or upload to a store unless requested.