Legacy Android APK Build Assistance

@ParasTech7

I have 21 years of experience with software development and native app development with extensive work in c# and database/ I can fix the gradle and build related issues in your device and also syc the FTP connectivity. I can also sign and puslish on google play console.

@kaustubhbawa123

Hi, I am an IIT Grad. I will make it a reality for you. I can efficiently take ownership of the APK generation cycle by utilizing Gradle's incremental build capabilities (Gradle 7+) to automate the process, leveraging Android Studio's built-in APK generation features, and implementing a custom SigningConfig to manage keystores and signing configurations. Kindly click on the chat button so we can discuss and get started. Will share you my prior projects done and my resume too. I have been doing freelancing since 2019 worked at top MNCs in both USA and India. Lets connect

@Ashnasajid

Hi, I can do this. With extensive experience in Android development, I am well-versed in managing mixed Java/Kotlin codebases and legacy Gradle environments. I will pull your repository, address any Gradle-4 issues, and ensure all build variants compile cleanly. My focus will be on producing a signed, installable APK that meets your acceptance criteria, including installation on Android 7–14 devices, proper database population, and successful FTP synchronization. I will provide a concise build log or README to facilitate future builds. My familiarity with SQLite, PHP, and C# utilities will ensure a smooth process. I am ready to start immediately and take full ownership of the APK generation cycle. Looking forward to collaborating on this project. Ashnasajid

@dushyant317

Hello, I’ve carefully reviewed your project requirements and clearly understand the tasks involved. I have 13 years of experience and strong expertise in the exact skills this project requires. I have successfully delivered similar projects before and can share relevant samples if needed. I will complete this within your expected timeline while maintaining quality and clear communication. I look forward to working with you and contributing sincerely to your project’s success.

@Palaksharma1602

Hello, I can take full ownership of your existing Android project and handle the end-to-end APK build process. I’ll pull your repository, resolve any Gradle 4 issues, and produce a signed, installable APK that works across Android 7–14, launches without crashes, shows preloaded SQLite data, and syncs via your FTP/PHP scripts. I’ll also provide a clear build log/README so you can replicate the process easily in the future. Lets deliver a clean, reliable APK that works perfectly and is ready for deployment. Thanks

@zaheermoe

Hi there, I've reviewed your project requirements for a senior-level Android developer to own the APK generation cycle, and I'm confident I can deliver the results you need. With extensive experience in handling legacy build systems, mixed-language projects, and database seeding workflows, I'm well-equipped to tackle the challenges presented in your project. My skills include: 1. Expertise in Android development with Java and Kotlin 2. Proficiency in working with Gradle and NDKs I'd like to suggest streamlining the APK generation process by implementing a CI/CD pipeline. This will ensure efficient and consistent builds for future releases. Let's discuss how we can proceed. I'm available to start immediately. Best, Zaheer Mahomed

@bjorkb

Hi, I saw you run an end-to-end APK generation project, and it caught my eye because I recently finished a similar project where I resolved legacy Gradle build issues to deliver stable, signed APKs compatible with multiple Android versions. I understand the project guidelines and I’ve developed a workflow that ensures deadlines are met without sacrificing the quality of the final output. I run a small creative team and our skill set matches your projects requirements, including expertise in mixed Java/Kotlin codebases, Gradle environments, and signing processes. I’m available to hop on a chat or exchange messages to discuss how we can get started on this immediately. When would be a good time for us to connect? Regards, Bjork Bronkhorst

@vijaykdev25

hi im having 7+ years of experience in android development, working extensively with legacy and modern Android codebases, mixed Java/Kotlin projects, and complex build pipelines. I’m comfortable taking full ownership of the end-to-end APK generation process you described. I’ve worked with offline-first Android apps using SQLite, remote SQL backends, custom sync mechanisms, and non-standard data flows (including FTP and PHP/HTTP scripts), so your setup is well within my comfort zone. Here’s how I’ll handle your scope of work: * Pull and review the existing repository, resolve any Gradle 4–related quirks, and ensure all build variants compile cleanly * Generate a properly signed, installable release APK using your provided keystore and existing configs * Verify installation and runtime behavior across Android 7–14 * Confirm the pre-seeded SQLite database loads correctly on first launch * Validate connectivity and sync with the existing FTP-hosted PHP endpoints * Provide a clear, concise build log or README so you can reliably reproduce the process in future releases * I pay close attention to legacy build systems, signing, SDK/NDK alignment, and reproducibility—no guesswork, no fragile steps. The goal is a clean, repeatable release APK that installs, runs, syncs, and passes Play Console or ADB verification without surprises. I’m ready to step in immediately and get this built end-to-end.

@TravisPM

Legacy Gradle 4 and mixed Java/Kotlin builds can hide tricky pitfalls. The C# pre-seeding step—does it integrate into the build pipeline or remain separate? Also, any quirks you’ve noticed with signing configs or build variant switching? Understanding this will speed up clean APK production and smooth handoff. Gert Smit