How this app maps to your workflow
Every screen exists for a reason in the rapid prototyping cycle — not as ticket overhead.
Project
Client engagement container.
One project per client or product. Holds all features and deployment history.
Feature
Business capability.
Purchase Request, Leave Application, etc. Includes problem statement and current status.
Prototype Version ★
The most important record.
v1, v2, v3… each with URL, screenshot, summary. Never overwritten.
Approval
Per-version sign-off.
Pending, Approved, or Rejected — with who, when, and remarks.
Change Request
Scope change log.
"Can we also add…" — Proposed, Accepted, Rejected, or Implemented.
Deployment
What actually shipped.
Links each release to the exact prototype version per feature.
Process → App action
| Process step | What to do in the app | Where |
|---|---|---|
| Understand | Create feature with problem statement | Project → New Feature |
| Prototype | Add prototype version with URL / screenshot | Feature → New Prototype Version |
| Review | Add comments during client walkthrough | Feature or Prototype details |
| Approve | Record approval (yes/no + remarks) | Prototype → Record Approval |
| Build | Update feature status to Built | Feature → Edit |
| Deploy | Record release with feature + version links | Project → Record Deployment |
| Feedback | Log change request, create new prototype version | Feature → New Change Request |
Folder structure
Tracker/
├── App.db ← all records
├── TrackerCode/ ← this app
├── Attachments/ ← supporting files
├── Screenshots/ ← approval screenshots
└── Prototypes/ ← exported HTML / assets
Feature Details — Purchase Request
Purchase Request
Approved
v3 Added finance approval
Approved by Jane · 15 May
v2 Added manager approval
Rejected "Need finance step"
↑ This is your Feature Details page — the full prototype story in one view.
Your daily loop:
Understand workflow → Generate prototype → Client approve → AI builds → Deploy → Client requests changes → Update prototype → Approve → Build.