Android AI Chatbot Testing
Budget: $250 – $750 USD
I need fresh eyes on an AI-powered chatbot that lives inside an Android mobile app. Your main task is to talk with the bot as a normal user would, then tell me exactly where it shines, where it hesitates, and where it flat-out fails.
Here’s how the work will flow:
• Install the current APK I provide and register with a throw-away account.
• Run through a set of typical user scenarios I’ll outline (ordering, support queries, small-talk, and a few edge cases you invent on the fly).
• Capture screen recordings or annotated screenshots whenever you spot odd replies, broken UI elements, or latency spikes.
• Summarise findings in a concise report, grouping issues by severity and adding reproduction steps so my devs can trace them quickly.
If you notice smaller glitches—missing data fields, typo-ridden responses, or anything that would worry a first-time user—call them out. I’m aiming for genuine, experience-based feedback rather than automated test logs.
Turnaround: 24–48 hours once you receive the test build. A clear, well-structured issue report is the key deliverable; no lengthy write-ups, just actionable notes and media evidence.
If this first round goes smoothly, I’ll likely have follow-up work on data entry checks, virtual-assistant task validation, and customer-service chat scripts, but right now the Android chatbot test comes first.
Here’s how the work will flow:
• Install the current APK I provide and register with a throw-away account.
• Run through a set of typical user scenarios I’ll outline (ordering, support queries, small-talk, and a few edge cases you invent on the fly).
• Capture screen recordings or annotated screenshots whenever you spot odd replies, broken UI elements, or latency spikes.
• Summarise findings in a concise report, grouping issues by severity and adding reproduction steps so my devs can trace them quickly.
If you notice smaller glitches—missing data fields, typo-ridden responses, or anything that would worry a first-time user—call them out. I’m aiming for genuine, experience-based feedback rather than automated test logs.
Turnaround: 24–48 hours once you receive the test build. A clear, well-structured issue report is the key deliverable; no lengthy write-ups, just actionable notes and media evidence.
If this first round goes smoothly, I’ll likely have follow-up work on data entry checks, virtual-assistant task validation, and customer-service chat scripts, but right now the Android chatbot test comes first.