Android User Authentication App Development
Budget: $15 – $25 USD
I have an Android app concept ready to move from wireframes to working code, and the first milestone is a solid, secure user-authentication flow. The job is to create a native Android application where new users can sign up, existing users log in, and forgotten passwords are recovered. Social sign-in (Google, Facebook, email/password) would be an added bonus if you’re comfortable wiring it up with Firebase Authentication, AWS Cognito, or another reliable backend.
The design assets and basic screen sequence are finished; what’s missing is production-quality code that follows current Android guidelines, runs smoothly from Android 8 upward, and is easy to maintain. Kotlin or Java are both acceptable—just keep the project cleanly structured (MVVM preferred) and well documented.
Deliverables
• Complete Android Studio project with all source code
• Integrated authentication (signup, login, password reset) connected to the chosen backend
• Simple post-login home screen confirming the active user session
• README detailing build steps and how to swap backend keys
Acceptance criteria
• All authentication flows verified on emulator and physical device
• No plain-text password storage; secure token handling in place
• Code passes lint checks and compiles without warnings
Please include your estimated timeline, preferred authentication service, and links to any similar Android work when you respond.
The design assets and basic screen sequence are finished; what’s missing is production-quality code that follows current Android guidelines, runs smoothly from Android 8 upward, and is easy to maintain. Kotlin or Java are both acceptable—just keep the project cleanly structured (MVVM preferred) and well documented.
Deliverables
• Complete Android Studio project with all source code
• Integrated authentication (signup, login, password reset) connected to the chosen backend
• Simple post-login home screen confirming the active user session
• README detailing build steps and how to swap backend keys
Acceptance criteria
• All authentication flows verified on emulator and physical device
• No plain-text password storage; secure token handling in place
• Code passes lint checks and compiles without warnings
Please include your estimated timeline, preferred authentication service, and links to any similar Android work when you respond.