Apps to Test: registration, sync & the Bug Board
Register the apps learners test, sync their schema and repo to unlock walkthroughs, and run the Bug Board.
- Real apps give learners real bug-hunting ground — add as many as you build
- Schema/repo sync turns each app into an architecture and code walkthrough
- The Bug Board turns learner reports into a triaged, assigned, tracked pipeline
Apps to Test, end to end
Register apps — Admin → Apps
Add each app learners will test: name, emoji icon, live URL, repo URL, Supabase project ref, category, description and display order. Set status (active / hidden) and the architecture unlock level (entry / junior / mid — junior, roughly Week 3, is the default).
The sync prerequisite
Registration alone doesn't light up the deep-dive tabs. The app's schema (from its Supabase ref) and repo tree (from its repo URL) must be synced first:
- Until the schema syncs, learners see "Architecture sync pending."
- Until the repo syncs, learners see "Code graph sync pending."
Once synced (the timestamp shows on the app card), eligible learners get a read-only Architecture walkthrough — tables, relationships, RLS policies; the shape only, never data or credentials — and a code graph of the repository.
The Bug Board — Admin → Bugs
Every bug learners file against these apps lands here. Filter by app, status (pending / valid / invalid / duplicate) and assignee; then:
- Assign a bug to a mentor or admin — they're pinged that it's on their plate.
- Step the resolution lifecycle — the fix-status tracked separately from the validity verdict (which happens in the Review Queue).
- Slack digest — a consolidated bug digest posts each morning at 8am, or post it now from the header.
Bugs and staff pickers are fenced to your org; the app catalog itself is shared platform content.
The journey, step by step
| Step | What you do | What you get |
|---|---|---|
| Register | Admin → Apps: add name, URL, repo URL, Supabase ref, description | The app appears in the learners' Apps to Test catalog |
| Sync | Sync the app's schema and repo tree | Architecture and code walkthroughs unlock for eligible learners |
| Gate | Set the architecture unlock level | The walkthrough opens once a learner reaches that level |
| Triage bugs | Admin → Bugs: filter by app, status, assignee | Every learner-reported bug is visible in one board |
| Assign & track | Delegate a bug to staff and step its resolution lifecycle | The assignee is pinged; validity and fix-status are tracked separately |
Frequently asked
Why do learners see 'sync pending'?
Registering an app is not enough — its schema (from the Supabase project ref) and repo tree (from the repo URL) must be synced before the Architecture and Code walkthroughs render. Until then learners see 'Architecture sync pending' or 'Code graph sync pending'. The sync timestamp shows on the app card once done.
What do learners get from a synced app?
A read-only architecture walkthrough — tables and columns, relationships, and RLS policies (the shape only, never data or credentials) — plus a code graph of the repository. It unlocks at the level you set (junior by default, around Week 3).
How is the Bug Board different from the Review Queue?
The Review Queue decides validity (valid/invalid/duplicate, awarding XP). The Bug Board is the operational side: filter, assign to staff, and track the resolution lifecycle — plus a consolidated Slack digest each morning at 8am (or post it now).
Related guides
What lands in each review queue, and what happens when you action it.
ReadCreate cohorts, review applicants and enroll learners — with seat quotas enforced automatically.
ReadConnect Slack and choose, per event type, where notifications go: Slack channel, in-app bell, email.
Read