Test Android Social Media App
Budget: ₹600 – ₹1,500 INR
I have an Android-only social media application that is ready for a thorough shake-down before the next release. I need fresh eyes to hunt for anything—from a misaligned icon to a performance hiccup—and document it clearly so my dev team can replicate and fix the problems fast.
Scope of the test
• User interface: check every screen, button, gesture, dark/light mode, and different screen sizes for layout breaks, visual glitches, and navigation dead-ends.
• App performance: measure launch time, scrolling smoothness, memory/CPU usage, battery impact, and behaviour on weak networks (3G/Edge) or with background apps running.
Devices & environment
Please use at least two Android OS versions (one recent, one older) and, if possible, a mix of chipset brands (Qualcomm/MediaTek/Exynos). Emulator insights are welcome, but real-device results carry more weight.
Deliverables
1. A structured bug report (spreadsheet or Jira/CSV export) detailing steps to reproduce, expected vs. actual result, device/OS used, severity level, and attachments.
2. Screen recordings or screenshots for all visual or UI issues.
3. Performance metrics summary with any throttling logs (ADB, Android Studio profiler, or comparable tools).
4. A brief final memo highlighting the top three issues you believe should be prioritised.
Acceptance criteria
A bug is counted as resolved when your reproduction steps consistently trigger the issue on my side. Payment milestones will align with verified reports.
If you enjoy poking holes in apps and can start within the next 24 hours, let’s make this social platform rock-solid together.
Scope of the test
• User interface: check every screen, button, gesture, dark/light mode, and different screen sizes for layout breaks, visual glitches, and navigation dead-ends.
• App performance: measure launch time, scrolling smoothness, memory/CPU usage, battery impact, and behaviour on weak networks (3G/Edge) or with background apps running.
Devices & environment
Please use at least two Android OS versions (one recent, one older) and, if possible, a mix of chipset brands (Qualcomm/MediaTek/Exynos). Emulator insights are welcome, but real-device results carry more weight.
Deliverables
1. A structured bug report (spreadsheet or Jira/CSV export) detailing steps to reproduce, expected vs. actual result, device/OS used, severity level, and attachments.
2. Screen recordings or screenshots for all visual or UI issues.
3. Performance metrics summary with any throttling logs (ADB, Android Studio profiler, or comparable tools).
4. A brief final memo highlighting the top three issues you believe should be prioritised.
Acceptance criteria
A bug is counted as resolved when your reproduction steps consistently trigger the issue on my side. Payment milestones will align with verified reports.
If you enjoy poking holes in apps and can start within the next 24 hours, let’s make this social platform rock-solid together.