Contact person: Business Client

Phone:Show

Email:Show

Location: Sonipat, India

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I’m building a mobile application that must run natively on both Android and iOS from a single code-base. The core function is straightforward: once a user verifies their account with a phone number, the app keeps an accurate record of everything they do inside it—specifically each played match, the associated scores, and their complete activity history.

Here’s how I picture the flow: a new user lands on the welcome screen, enters a phone number, receives a one-time code, and, once verified, lands on a clean dashboard that shows past matches, scores, and cumulative statistics. Every new match they play is automatically written to a secure database so that historical data is always available for recall, export, or analysis.

I’m open to React Native, Flutter, Kotlin Multiplatform, or any comparable cross-platform tech as long as I end up with a single maintainable code-base and native-feeling performance. The backend stack is flexible, too—Firebase, Supabase, or a lightweight custom REST/GraphQL service would all work—so choose what lets you ship quickly while keeping the data secure and easy for me to administer later.

Deliverables
• Complete Android & iOS builds ready for the stores
• Source code with clear setup instructions
• Secure phone-number authentication flow
• Data models and endpoints covering: user profile, match records, scores, activity log
• A basic but polished UI that lists matches and allows simple filtering/search

Acceptance criteria
• A new user can register and sign in via phone number within 30 seconds or less
• Starting a match instantly creates a record; finishing it updates the scores and history
• Data persists across reinstall on both platforms
• Builds pass store validation with no critical warnings

If you have examples of similar cross-platform tracking apps or a quick prototype, feel free to share. Let’s keep communication tight so we can push a working beta quickly." (client-provided description)