I already have a stable Android code-base written in mixed Java / Kotlin that targets an offline-first workflow (SQLite locally, SQL Server remotely) and exchanges data through FTP-triggered PHP/HTTP scripts. The project sits on a legacy Gradle 4 stack, and I use a separate C# utility to pre-seed the local database before each release. What I need now is a senior-level pair of hands to take full ownership of the end-to-end APK generation cycle. All SDKs, NDKs, keystores, and signing configs are present on my machine; the environment is ready—you simply step in, run the build, and hand back repeatable output. Scope of work • Pull the existing repository, resolve any Gradle-4 quirks, and confirm the build variants compile cleanly. • Produce a signed, installable release APK (no extra white-label customisations this time—just the standard build). • Verify that the packaged app installs, launches, populates its pre-loaded SQLite DB, and can still reach the FTP-hosted PHP endpoints. • Provide a concise build log or short README so I can replicate the process for future clients without surprises. Acceptance criteria The delivered APK must: 1. Install on Android 7–14 devices without runtime crashes. 2. Show offline data from the seeded database on first launch. 3. Successfully sync via the existing FTP/PHP scripts once connectivity is available. 4. Be signed with my provided keystore and pass Play-Console or ADB install verification. If legacy build systems, mixed-language projects, and database seeding workflows are your comfort zone, I’m ready to start straight away.