Android Chat MVP
Budget: ₹250,000 – ₹500,000 INR
I’m commissioning a stripped-down, proof-of-concept chat app for Android that works even when the device is offline. The goal of this first milestone is to establish the technical backbone—not visual polish—so I can quickly validate the product idea and iterate later.
Key scope
• Single platform: Android (phone and tablet).
• Data strategy: everything—account details, message threads, pending outbound messages—must persist locally in an encrypted SQLite / Room database and sync automatically once a connection is restored.
• On-boarding & auth: users identify themselves with their phone number only; verification via SMS OTP or similar is acceptable. No email or social login for now.
• Core interaction: one-to-one text messaging. A message typed offline should appear instantly in the UI, queue locally, and push to the server the moment connectivity returns.
Deliverables
1. Android Studio project in Kotlin (Java acceptable if you have stronger justification).
2. Gradle-buildable APK and brief README showing how to run a self-hosted or lightweight cloud back-end (Firebase, Supabase, or your recommended solution) plus any required environment keys.
3. Short walk-through video or GIF proving offline compose, reconnect, and sync flow.
Acceptance criteria
• Registration completes with a verified phone number.
• Messages sent while offline show in the thread immediately and sync automatically when the network is available.
• A newly installed client, after logging in, downloads the full local history from the back-end.
I value clear, well-commented code and incremental commits over fancy UI. If this foundation is solid we’ll expand into group chat, file sharing, and UI refinement in later phases.
Key scope
• Single platform: Android (phone and tablet).
• Data strategy: everything—account details, message threads, pending outbound messages—must persist locally in an encrypted SQLite / Room database and sync automatically once a connection is restored.
• On-boarding & auth: users identify themselves with their phone number only; verification via SMS OTP or similar is acceptable. No email or social login for now.
• Core interaction: one-to-one text messaging. A message typed offline should appear instantly in the UI, queue locally, and push to the server the moment connectivity returns.
Deliverables
1. Android Studio project in Kotlin (Java acceptable if you have stronger justification).
2. Gradle-buildable APK and brief README showing how to run a self-hosted or lightweight cloud back-end (Firebase, Supabase, or your recommended solution) plus any required environment keys.
3. Short walk-through video or GIF proving offline compose, reconnect, and sync flow.
Acceptance criteria
• Registration completes with a verified phone number.
• Messages sent while offline show in the thread immediately and sync automatically when the network is available.
• A newly installed client, after logging in, downloads the full local history from the back-end.
I value clear, well-commented code and incremental commits over fancy UI. If this foundation is solid we’ll expand into group chat, file sharing, and UI refinement in later phases.