ProductWindows app
Beta Tester Tracker
Track every beta tester's feedback, latest status, and next check-in date in one local sheet.
The problem
Recruit 50 testers, then forget who said what. Most quietly churn.
The solution approach
A local sheet: one row per tester with feedback log, activity status, next check-in date; nudges on overdue.
What you will end up with
- Tester list: handle, contact, joined, latest feedback, status, next check-in.
- 14 days silent -> auto-marked "quiet"; reach-out suggested.
- Feedback drawer: timeline; each item tagged "adopted / fixed / to-evaluate".
- Export feedback summary Markdown for product + design.
Ready-to-use prompt
You are a senior engineer building local desktop tools. The user is a PM, non-developer.
[Goal]
Every beta tester gets ongoing follow-up; feedback gets categorized and answered.
[Platform & Stack]
- Windows + macOS; Electron + React + TypeScript; local SQLite
[Core Features]
1. Tester list: handle, contact, source (friend / recruited / customer), joined, status, last feedback, next check-in, notes.
2. Editable activity rules: feedback in 14d = active; 14–30d = quiet; > 30d = lost.
3. Feedback timeline drawer: each item tagged (feature / bug / UX / commercial) with status (to-evaluate / adopted / fixed / declined).
4. Top "Today's check-ins" card.
5. Weekly feedback Markdown export, grouped by type with user notes.
[Visual Style]
- Light background, white cards, radius 16, generous whitespace.
- Primary button muted dark; secondary light gray.
- Follows system dark mode; system fonts.
[Robustness]
- All data stays on the local machine. Offline.
- Autosave; 7-day rolling backups.
- Friendly messages on bad input, never raw stack traces.
[Delivery]
1. Outline project structure + plain-text wireframe first; wait for confirmation.
2. Deliver in modules; run each one for me to see.
3. Package a Windows .exe and macOS .dmg, ship a 500-word plain-language user guide, list known limits.
Start with structure and wireframe.After copying
1
Open Codex Desktop and create a new project
2
Paste the prompt and send
3
Wait for Codex to finish; tweak company names, column names, button text as needed