Android App Final Touches & Launch
Budget: $100 – $300 CAD
My Android project is already coded and running; we are at the “almost-there” stage. What’s left is to weave in the last moving parts so the app can pass Google Play’s review and appear in the store.
The core task is integrating the required payment gateway so the build complies with Google Play policies. Once that is in place I want to open an internal/closed test track, bring in a small group of users to exercise every flow, and then push the final AAB to production.
What you will actually do
• Plug the payment gateway into the existing codebase (Android Studio, standard Kotlin/Java project).
• Resolve any dependency or policy warnings raised by the Play Console.
• Set up the testing track, invite testers and collect their feedback in a concise report.
• Produce a release-ready, signed AAB together with the accompanying screenshots, privacy policy links and store listing details.
• Stay with the project until Google confirms the publication.
Acceptance criteria
1. Payment transactions complete successfully in the sandbox and live environments.
2. No policy, security or compatibility issues flagged by the Play Console.
3. At least 10 real testers submit feedback confirming core features work.
4. Google Play listing is approved and visible to the public.
If you have recent experience taking an app from “feature-complete” to “approved in the store,” let’s wrap this up together.
The core task is integrating the required payment gateway so the build complies with Google Play policies. Once that is in place I want to open an internal/closed test track, bring in a small group of users to exercise every flow, and then push the final AAB to production.
What you will actually do
• Plug the payment gateway into the existing codebase (Android Studio, standard Kotlin/Java project).
• Resolve any dependency or policy warnings raised by the Play Console.
• Set up the testing track, invite testers and collect their feedback in a concise report.
• Produce a release-ready, signed AAB together with the accompanying screenshots, privacy policy links and store listing details.
• Stay with the project until Google confirms the publication.
Acceptance criteria
1. Payment transactions complete successfully in the sandbox and live environments.
2. No policy, security or compatibility issues flagged by the Play Console.
3. At least 10 real testers submit feedback confirming core features work.
4. Google Play listing is approved and visible to the public.
If you have recent experience taking an app from “feature-complete” to “approved in the store,” let’s wrap this up together.