Publish a tested, branded customer portal using your organization’s Google Play developer account. The app’s package name must match the application identity you intend to maintain.
Create the app in Play Console, complete the listing and required app-content declarations, and upload the signed AAB to a testing track. Follow the Play Console setup guide and the account-specific tasks shown in your console.
For Flutex, prepare screenshots of your actual configured app, a public privacy policy, support contact details, and customer test credentials for review. Describe the customer portal accurately; do not imply that it offers staff administration or payment processing that your release does not implement.
Install through the selected test track. Check that the production CRM is reachable, the test contact has appropriate records, and Firebase messages reach that installed build. Keep the review account active and avoid maintenance windows during review.
Complete any required testing and production-access steps for your developer account. Review current target API and policy requirements in Play Console instead of relying on fixed values from an older tutorial.
When ready, submit the production release and monitor its review status. Resolve reported issues against the exact submitted build. Publication timing and approval are controlled by Google, not by the Flutex source-code purchase.