SaaS School & Gym Android

I’m launching two white-label Android products—SmartEducationSoft for schools and SmartGymSoft for fitness centres—and I need a single multi-tenant SaaS backbone that lets both apps coexist under one codebase while serving completely separate client databases.

The core platform must include:

• Secure, role-based login that recognises School Admin, Gym Admin and End Users (students or gym members)

• Subscription management capable of charging Credit/Debit Cards and handling Bank Transfers, with automatic licence enforcement per tenant

• Push notifications and WhatsApp messaging hooks so each organisation can reach its own users without crossing data boundaries

• CI/CD workflow that compiles two branded Android builds, signs them, and walks them through Google Play submission until they are live

I’ll consider the project complete when both apps are accepted in the Play Store, tenants can onboard themselves, payments flow into my gateway accounts, and I receive full source code plus deployment documentation detailed enough for an AWS or GCP hand-off. If you’ve already delivered SaaS Android solutions at scale, let’s talk timelines and tech stack preferences right away.