Entry-Level Android Bug Tester
Budget: $2 – $8 USD
Each time I release a new APK, you’ll install it on a real Android phone, explore every corner of the app, then write down every bug, glitch, crash, or odd behaviour you notice. I rely on these detailed notes to tighten up the code, so clarity and structure matter just as much as finding the issues themselves.
Here’s what the work looks like:
• Install the latest build on an Android phone (physical device—emulators and tablets are a bonus, but the phone test is essential).
• Work through all screens and flows, paying attention to the interface, performance and any unexpected data or security hiccups.
• Capture steps to reproduce, screenshots or short screen-recordings, and your device details.
• Drop the compiled report (Word, Google Doc, or spreadsheet—use what’s easiest for you) into our shared folder so the developer can jump straight into fixes.
I’ll send fresh builds regularly, and you’ll repeat the same cycle. If you’re thorough, organised, and happy doing iterative testing at an entry level, this will be an easy ongoing task.
Here’s what the work looks like:
• Install the latest build on an Android phone (physical device—emulators and tablets are a bonus, but the phone test is essential).
• Work through all screens and flows, paying attention to the interface, performance and any unexpected data or security hiccups.
• Capture steps to reproduce, screenshots or short screen-recordings, and your device details.
• Drop the compiled report (Word, Google Doc, or spreadsheet—use what’s easiest for you) into our shared folder so the developer can jump straight into fixes.
I’ll send fresh builds regularly, and you’ll repeat the same cycle. If you’re thorough, organised, and happy doing iterative testing at an entry level, this will be an easy ongoing task.