ProductWindows app
Product Feedback Inbox
Centralize feedback from chat, email, mindmaps, and support tickets. Auto-tag and prioritize so planning meetings start with clarity, not chaos.
The problem
PMs triage hundreds of feedback notes every week — one from chat, one from support, one forwarded from sales. It ends up as sticky notes on a wall. Planning meeting prep is a late-night job.
The solution approach
A local inbox. One card per item with source, raw text, user type. Auto-tag (perf / UX / bug / feature) and assign priority (high / med / low). One click exports a grouped list for planning.
What you will end up with
- Home feed of feedback cards; filter by tag, sort by date or heat (hit count).
- Add: single entry or bulk paste (one per line). Keyword-based auto-tagging.
- Merge similar items; source history preserved.
- Priority matrix view: impact x urgency; drag to adjust.
- One-click export of "this week's discussion list" to Excel or Markdown for planning.
- Local storage; data never leaves your PC.
Ready-to-use prompt
You are a senior engineer experienced with Windows desktop apps. Build a local Windows tool for a product manager. Non-developer user.
[Goal]
Centralize scattered user feedback, auto-tag and prioritize, so weekly planning starts with a clean list.
[Platform & Stack]
- Windows 10/11 desktop app
- Electron + React + TypeScript
- Local SQLite; offline; ship a Windows .exe installer
[Data Model]
Feedback card: id, body, source (chat / email / ticket / sales / internal / other), user type (paid / free / internal), created, tags (multi), priority (high/med/low), impact (1-5), urgency (1-5), status (open / planned / resolved / wontfix), mergedFrom (array).
[Core Features]
1. Home feed: cards with 150-char snippet, tag chips, priority corner, source icon.
2. Filter by tag (multi) / source / user type / status. Sort by date or heat (merged count).
3. Add: single-entry form with source + user type; bulk paste (one line per item) with keyword-based auto-tagging.
4. Auto-tagging via an editable keyword dictionary — tags like perf / UX / bug / feature / copy / compliance. Show confidence; user confirms or corrects.
5. Merge: select cards -> merge into one; preserve source history; increment heat.
6. Priority matrix: x = impact (1-5), y = urgency (1-5); drag cards to adjust.
7. Export: Excel for weekly list; Markdown groups for pasting into Notion / Feishu.
[Visual Style]
- Minimal fresh: white / light-gray / soft card shadows.
- Desaturated tag colors, a consistent palette.
- Follows system dark mode; bilingual toggle.
[Robustness]
- Flag likely duplicates during bulk paste.
- Keyword dictionary import/export as JSON for cross-machine portability.
- Auto-recover DB from last backup.
[Delivery]
1. Structure + wireframes for feed, add, matrix.
2. Phase 1: entry + auto-tag. Phase 2: matrix + merge. Phase 3: export.
3. Package .exe; 500-word user guide.
Start with structure and wireframes.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