Phase 1 centres on a native Android app written in Kotlin that allows travellers to buy and manage eSIM data plans. The core workflow is simple—users create an account, pick a country and plan, pay, and instantly receive the eSIM profile pushed to their device. I am using the eSIM provider’s API for provisioning, Stripe and SSLCOMMZ for all card payments, and Firebase (Analytics SDK) to capture usage metrics and anonymised behaviour events so we can refine the product after launch. Functional scope • Auth: email-based signup / login, plus “forgot password” firebase OTP verification • Dashboard: active plans list, data balance and renewal dates • Storefront: country & plan catalogue with search / filter / reagion / • Purchase & top-up: Stripe/SSLCOMMZ card flow, promo-code support later • eSIM activation: call to API, show installation QR or automatic download, sent the QR code to email • Push notifications: FCM for successful activation, low-balance and promo messages • Profile: basic details, saved cards, transaction history Technical notes - Kotlin + Jetpack (MVVM, Coroutines, Navigation) on a clean architecture. - Straight-forward Material Design 3 components with light branding colours; no heavy custom widgets. - Backend of your choice (Node, Django, Go, etc.) exposing REST/JSON endpoints. - A very simple web-based admin panel is welcome but optional; it only needs to list users, plans sold, and allow manual top-ups. - Stripe Webhooks handled server-side for payment confirmation. - Firebase Analytics events for screen views, plan purchases, and retention funnels. Deliverables 1. APK / AAB ready for Google Play internal testing 2. Source code for Android app, backend and admin (Git repo) 3. Minimal setup & API documentation so another dev can run the stack locally 4. Up to three months of post-launch bug-fix support (critical and reproducible issues) 5. Agents can change the company name and use their own logo at settings. 6. Split the payments into commission and vendor to pay instant using Stripe 7. Able to setup the commission for agents at admin backend when create an agent. Acceptance will be based on: compilation without errors, successful eSIM profile purchase in sandbox, any payment captured and reflected in dashboard, and analytics events visible in Firebase. Any questions on the workflow, APIs, or timeline—let me know so we can keep Phase 1 lean and launch-ready.