Vuvusport beta reporting

Vuvusport Beta Testing Guide

Thanks for testing Vuvusport. This page walks you through installing the app on each platform and what makes a good bug report.

Where to test

You can test Vuvusport on any combination of these three surfaces. Pick whichever you actually use — there's no need to install all three.

iOS (TestFlight)

  1. Install Apple's TestFlight app from the App Store.
  2. Tap the join link below on your iPhone — it opens TestFlight and installs Vuvusport.
Open TestFlight link

Android (APK sideload)

  1. On your Android phone, download the APK below. You may need to allow installs from your browser ("install unknown apps").
  2. Open the downloaded file → Install.

Latest: 1.0.0 (4) · commit 1139574d

Download latest APK

Web

Open vuvusport.com in any modern browser. Works on desktop and mobile.

Web bug reports must include a Jam recording — install the extension once and you'll capture console logs + network for every report.

How to report

iOS — use TestFlight feedback

Two ways to send feedback, whichever works on your device:

A. From the TestFlight app (most reliable)

  1. Open the TestFlight app on your iPhone.
  2. Tap Vuvusport in the list of beta apps.
  3. Scroll to the bottom and tap Send Beta Feedback.
  4. Pick Screenshot & Feedback (or just Feedback), add a comment, submit.

B. From inside the Vuvusport app (if shake works for you)

  1. Shake the device, or take a screenshot.
  2. If TestFlight prompts you to share feedback, add a comment and submit.

Crashes are submitted automatically without any action on your part. Your iOS report shows up in our triage board within ~30 minutes (we poll Apple's API on a schedule).

Android & Web — use the form on this site

Sign in with your email, click the magic link in your inbox, then file a report. You stay signed in for 7 days, so you can file as many as you like without re-authenticating.

What makes a quality report

  • One issue per report. Don't bundle two unrelated bugs into a single submission — splits the triage and slows fixes.
  • Be specific in the title. "Live blog stops auto-refreshing after 30s on Chrome" beats "Live blog is broken".
  • Show the steps. Walk us through 1-2-3 so we can reproduce. If we can't reproduce, we can't fix it.
  • Tell us what you expected. Sometimes the difference between a bug and "working as intended" is just what you anticipated.
  • Attach evidence. Web: a Jam recording (mandatory). Android: a screenshot or short video. iOS: TestFlight does this automatically.
  • If it's a translation issue, switch to the language first. Tell us which language (English / French / Arabic / Swahili / Hausa) you were in when you saw the wrong text.
  • Check your past reports first via the My reports tab — duplicates slow everyone down.

Which "Type" should I pick?

The form asks you to categorise. Use these definitions:

Bug Something is broken or behaves wrong. The default.
Translation Wrong, awkward, or missing text in a specific language. Tell us the language.
Missing feature Something you reasonably expected to exist but doesn't — e.g. no way to share an article, no way to filter the feed.
Suggestion Wishlist or polish idea. We may or may not act on these, but we read every one.

Which "Severity" should I pick?

Blocker I can't use the app at all — crash on launch, can't sign in, articles never load.
Major A whole feature is broken — predictions don't save, push notifications don't arrive.
Minor Something is off but I can work around it — a button needs two taps, a date is wrong on one card.
Cosmetic Visual only — typo, mis-aligned icon, wrong colour.

When in doubt, lower it by one. We'd rather you flag everything than under-report blockers because you're being polite.

About the tools we use

TestFlight — iOS beta distribution

TestFlight is Apple's official beta-testing app. It's the only way to install pre-release iOS apps without the App Store. Apple handles the install, pushes updates automatically when we cut a new build, and collects your feedback.

First-time setup

  1. Install TestFlight from the App Store (one-time).
  2. On your iPhone, tap our join link: https://testflight.apple.com/join/ZrRNmp7M — TestFlight opens and installs Vuvusport.
  3. Open Vuvusport from the home screen like any other app.

Getting new builds

TestFlight pulls new builds automatically in the background. You can also open the TestFlight app and look for an Update button next to Vuvusport.

Sending feedback

  • From the TestFlight app (recommended): open TestFlight → tap Vuvusport → scroll to the bottom → Send Beta Feedback → pick Screenshot & Feedback or just Feedback → write your note → Submit.
  • From inside Vuvusport: shake the device or take a screenshot. If TestFlight prompts you to share feedback, type a note and submit. (Whether the shake / screenshot gesture is offered depends on your device + iOS version.)
  • Crashes: submitted automatically — no action needed.

Each TestFlight feedback becomes a Trello card on our triage board within ~30 minutes.

Jam — Chrome extension for web bug recordings

Jam is a free Chrome extension that captures exactly what happened when you hit a bug: a short screen-recording video, every JavaScript error from the browser console, and every network request the page made (including failed ones). You share a single link and we replay and inspect everything.

Why we require it for web bugs: "the page froze" tells us nothing. A Jam recording shows the exact click that hung, the JS errors that fired, and the API response we got back. Most web bugs are unfixable without one.

First-time setup

  1. Install Jam from the Chrome Web Store.
  2. Sign in (free tier is enough — no credit card).
  3. Pin the Jam icon to your toolbar so you can reach it quickly (Chrome puzzle-piece menu → pin icon next to Jam).

Recording a bug

  1. Get to the page where the bug happens — but don't trigger it yet.
  2. Click the Jam icon → Start recording → pick This Tab when prompted.
  3. Reproduce the bug. Keep it short — under 60 seconds is best.
  4. Click the Jam icon → Stop. Jam opens a new tab with your recording.
  5. Click Copy link (or copy the URL from the address bar).
  6. Paste that link into the Jam recording URL field on the report form.

Common gotchas

  • By default Jam doesn't see Incognito tabs — if you need to record one, enable Jam in chrome://extensions → Jam → "Allow in Incognito".
  • Stay on a single tab during a recording — Jam captures one tab at a time.
  • Don't worry about file size — Jam compresses long recordings automatically and the link still works.
  • If you forget to record and lose the bug, file it anyway with steps to reproduce. Jam is required where possible but a clear written report still helps.

FAQ

Where do my reports go?
Each one becomes a card on our internal triage board. You see your own reports in the My reports tab once you sign in.
Will you reply to me?
Only if we need clarification — and we'll email the address you signed in with. Otherwise reports flow into the queue silently.
Can I file from any device?
Yes. Sign in once on each device you use. The 7-day session works per device.
I found a security issue.
File it the same way but mark severity Blocker and prefix the title with "[security]". We'll triage immediately.