Android Test Mission Brief

Thank you for lending your time to shape Shokken. This guide turns the Android testing session into a predictable checklist so every report lands with the details I need.

Who Should Use This Guide

  • Android devices only; the iOS flow lives in a separate briefing.
  • You’ll need a Google account that can join testing groups and access Google Play.
  • Keep shokken.rsvp handy—it is the single source of truth for builds, FAQs, and issue tracking.

Step 1 – Visit shokken.rsvp

  1. Open your browser to https://shokken.rsvp. Bookmark it now so you can return whenever you need updates or build notes.
  2. Review the latest release notes and confirm the Android test is marked “open”. If it’s paused, wait for the next notification before proceeding.

Step 2 – Join the Google Group

  1. From the test page, follow the “Join the Android Testers Google Group” link.
  2. Sign in with the Google account tied to the Play Store on your device.
  3. After you join, give Google a few minutes to propagate the permission. If you see a 404 or access denied screen when you continue, wait 10 minutes and refresh.

Step 3 – Accept the Play Store Invitation

  1. Return to shokken.rsvp and tap the Play Store invitation link.
  2. Hit “Become a tester”, then tap “Download it on Google Play”.
  3. If the Play Store still shows the production listing, close and reopen the Play Store app; the alpha banner should appear once the tester flag sticks.

Step 4 – Install, Launch, and Log In

  1. Install the latest alpha build from the Play Store.
  2. Launch Shokken and enter your email address on the login screen.
  3. Watch your inbox (and spam folder) for the one-time login code. Codes expire quickly, so request a fresh one if the first doesn’t arrive within two minutes.

Step 5 – Run the Host Happy Path

  1. Pretend you’re managing a busy waitlist. Add at least three guests with realistic names, party sizes, and email addresses you control.
  2. Confirm that:
    • A welcome email fires when each guest joins the queue.
    • The “Notify” action sends a second email.
    • Dismissing the guest triggers the final confirmation message.
  3. Note any copy glitches, timing gaps, or UI friction—small paper cuts matter.

Step 6 – Stress the Workflow

  • Mix in edge cases: duplicate emails, excessively long names, odd characters, or more guests than you would reasonably seat.
  • Force quit the app mid-action, reopen it, and verify the queue state reconciles cleanly.
  • Try the waitlist actions offline, then reconnect to see queued operations flush.
  • Document anything that feels inconsistent or confusing.

Step 7 – Probe the Security Surface (Optional)

If you have security testing experience:

  • Inspect network calls to see if sensitive data or API keys leak.
  • Attempt to tamper with requests, impersonate another client, or replay tokens.
  • Keep any discovered secrets private. Share findings directly with me, not in public channels.
  • Remember this environment is pre-production; there’s no live customer data, so experiment responsibly.

Step 8 – Capture Build Details

  • Tap the profile icon in the top-right corner of the app bar.
  • Scroll to the bottom of the profile sheet to locate the build number.
  • Screenshot this view or write the number down so it accompanies your report.

Step 9 – File Your Report

When you’re ready to share results, head back to shokken.rsvp and open the issue tracker.

  • Include your device model, Android version, and the build number.
  • Describe what you observed, the exact steps to reproduce it, and what you expected instead.
  • Attach logs, screenshots, or screen recordings if they clarify the issue.
  • If you’re unsure how to submit or a report feels sensitive, reach out through the direct support contacts listed on the site and we’ll walk through it together.

Step 10 – Stay in the Loop

  • New builds roll out regularly; revisit shokken.rsvp for updated release notes before each session.
  • Share the invite with any hosts—restaurants, dentists, barbers—who would benefit from a smarter waitlist.
  • Keep testing as often as you can. Every data point tightens up the alpha track and helps Shokken earn Google’s sign-off.