Take Over Existing Card Game Client and Deliver Android APK/AAB

Take Over an Existing Online Card/Mahjong Game Client and Deliver Android APK/AAB

We need an experienced game team to take over an existing online card/mahjong game client, restore its development and build environment, complete Android adaptation, and deliver reproducible APK and AAB release builds.

This is an existing casual game using an existing backend protocol. It does NOT include real-money gambling, wagering, cash-out, or financial settlement. Source code, technical documents, test accounts, and private endpoints will be shared with the selected team after confidentiality terms are agreed.

SCOPE
1. Audit source code, resources, plugins, native libraries, build scripts, branches, submodules, and missing dependencies.
2. Document the game engine, JDK, Gradle, Android Gradle Plugin, Android SDK/NDK, Node.js, and package manager versions.
3. Restore the project on a clean machine without hidden dependencies on the previous developer's computer.
4. Fix compilation errors, Gradle conflicts, missing resources, native plugin compatibility, and packaging issues.
5. Configure application ID, versions, environments, permissions, network security, Android 12+ exported components, deep links, safe areas, fullscreen, audio focus, and lifecycle handling.
6. Support arm64-v8a and advise whether legacy armeabi-v7a support is needed.
7. Validate startup, login, resource update, lobby, room creation/joining or matchmaking, gameplay, settlement, next round, and return to lobby.
8. Test Wi-Fi/mobile switching, disconnection, background/foreground, process termination, reconnection, and game-state recovery.
9. Restore existing Android integrations such as login, payment, push, sharing, voice, analytics, or hot update only where already present. Signing keys and credentials remain under our control.
10. Deliver test APK, release-candidate APK/AAB, build scripts, environment templates, build guide, change list, test report, risk list, R8/ProGuard mapping, and native symbols.

ACCEPTANCE
- A clean machine can build APK and AAB using the delivered documentation.
- The app installs, launches, upgrades, and reinstalls on the agreed Android device matrix.
- Existing accounts complete the lobby, room, gameplay, settlement, and return flow against the current backend.
- Network switching, disconnect, backgrounding, and restart follow existing reconnection rules.
- No blocker/critical defect remains in startup, login, gameplay, reconnection, or settlement.
- Release builds contain no test endpoints, debug menus, plaintext secrets, sensitive logs, or undeclared permissions.
- All source, artifacts, mappings, symbols, and audit documents are delivered.

MILESTONES
1. Source/build audit and recovery plan - 15%
2. Reproducible clean build and installable test APK - 25%
3. Android adaptation, core flow, and reconnection acceptance - 35%
4. Final APK/AAB, documentation, test report, and acceptance support - 25%

REQUIRED QUALIFICATIONS
- Proven legacy game client takeover and Android game delivery experience.
- Strong Gradle, SDK/NDK, native plugin, crash analysis, performance, hot update, and real-time networking skills.
- At least two verifiable Android game or multiplayer examples.
- Git delivery with reviewable commits; binary-only delivery is unacceptable.
- Named technical lead and at least 14 days of post-acceptance defect support.

Please answer: relevant takeover cases; assigned team and allocation; first 3-day audit plan; clean-build approach; signing/credential security; timeline, milestone price, and risks; support commitment.

Fixed budget: USD 2,000-4,000. Backend rewrites, new game modes, major UI/art redesign, iOS redevelopment, store account fees, and long-term operations are out of scope unless separately quoted.