Illustrative example — your review is generated from your submission. Scores and feedback below are fictional but match the real review layout.
72/100
Competent
Solid MVP framing; tighten NFRs and security before mock-ready
Per-step breakdown
Requirements
15/20
Architecture
15/20
Data model
15/20
Interface & sync
17/20
Optimizations
14/20
Tradeoffs
16/20
Strengths
Clear functional scope (compose, thread list, search) with sensible MVP vs stretch split.
Architecture diagram shows client store, sync worker, and API boundary with a single source of truth.
Offline queue and conflict strategy (LWW + user prompt on body edits) are named explicitly.
Gaps
Non-functional requirements are thin — no targets for initial load, search latency, or attachment limits.
Data model omits draft vs sent states and how thread ordering stays stable under pagination.
Security section misses XSS surfaces in HTML compose and token storage choices on shared devices.
Illustrative — Email Client (fictional submission)