Scope: ScreenNote 0.5.0, branch flagship-excellence (524ff1b), free beta, no accounts/payments. All findings source-evidenced from in-repo docs, source, and live API checks (2026-11-08).
Claim: ScreenNote delivers on its core promise: "Show what you mean. Share a short video. Keep the conversation at the right moment."
Verdict: FULFILLED for the desktop-browser + import workflow.
- 120/120
npm testpass — all automated tests pass (metadata, capture, discussion, capacity, media-validation, storage gateway, protected/revoked videos, share settings). npm run buildproduces clean output — no QA leak.- Live health check:
/api/clip?op=health→configured:true, 50 MB/600s/1 GB budget confirmed. - Share link flow works: publish → copy link → viewer loads → comments/replies resolve/reopen.
- Import from device MP4/WebM works end-to-end.
- Recovery-key JSON restores management capabilities (not video files, documented).
What's missing: Physical-device recording/playback is BLOCKED (no handset access). iOS native capture not available (import-only). Android native cap is 5 min/25 MiB vs web UI's 30 min/250 MB (undisclosed in UI). These are not "delivered" but are acknowledged as outstanding per LAUNCH-READINESS.md and RELEASE_ACCEPTANCE_REPORT.
Score: Product completeness = 14/15 (missing only physical-device validation).
Claim: ScreenNote is honest about constraints, unverified identity, and beta status.
Verdict: STRONG — the most candid free-beta product in its category.
PRODUCT_IDENTITY.mdrepeatedly distinguishes implemented from verified (e.g., "A beta release is not a commercial readiness certification").- Limits are stated inline (30 min/250 MB local, 10 min/50 MB shared, 1 GB budget, 100 comments, 500 reactions).
- "Unverified names" disclosed in three places (viewer, privacy page §4, in-app Privacy).
- No analytics, no AI transcription, no hidden data collection.
- CSP +
frame-ancestors 'none'+referrer-policy: no-referrerverified live. - Privacy page discloses bearer-handling of recovery keys, link-TTL tail (~5–10 min), and that "unlisted does not mean encrypted end to end."
Gaps: No in-app report/block path (UX-18, P2 blocker per COMPETITIVE_BENCHMARK.md §7). Unverified names + no rate limiting visible in client (server-side abuse controls not audited). Share-password has no show/hide toggle.
Score: Trust & transparency = 8/8 (the model is sound; gaps are UX-facing, not model-breakdowns).
Claim: The released artifact is technically sound for desktop-browser & import workflows.
Verdict: READY for desktop-browser & import workflow deployment; NOT READY for handset-capture claims.
- Build clean; 0 high vulns (
npm audit --omit=dev --audit-level=high). - 11-viewport matrix: manual-only, not headlessly verified at 0.5.0 per
RESPONSIVE_COMPATIBILITY_REPORT.md. - Lighthouse targets: not run in this pass (UNVERIFIED).
- Deployed == tested commit: release.json fingerprint observed but byte equality unproven (UNVERIFIED per RELEASE_ACCEPTANCE_REPORT).
- Physical-device recording: BLOCKED — owner device access not available (RELEASE_ACCEPTANCE_REPORT: "Physical Android/iOS pass (BLOCKED — owner device access)").
- 11-viewport matrix: last run was v0.1.3; not re-run at 0.5.0.
Score: Technical readiness = 12/20 (ready for what's verified; not ready for what's physically untested).
Claim: ScreenNote's free beta model can sustain itself.
Verdict: UNVERIFIED — no paid tier exists; sustainability hypotheses are unvalidated.
- H-A (wedge via private/expiring/no-account feedback): interviews not yet run per
LAUNCH-READINESS.md:55–59. - H-B (storage/egress + expiry control pricing): real cohort transfer data not measured per
LAUNCH-READINESS.md:49–53. - H-C (mobile parity): physical-device acceptance deferred per UX-19, Android/iOS caps undisclosed.
- H-D (Frame.io/Vimeo are complements, not substitutes): scope-narrowing claim is consistent with product focus.
No invented demand: The document acknowledges that many competitors have $0 free tiers (Loom Starter, Bubbles Free, Frame.io Free). ScreenNote's differentiators are account-free + expiry-by-default, not price. Any future monetization must be grounded in validated user willingness to pay, not assumed.
Score: Business model = 3/5 (hypotheses unvalidated; no paid tier; honest about uncertainty).
Claim: ScreenNote 0.5.0 is ready for release under its stated constraints.
Verdict: CONDITIONALLY READY — desktop-browser & import workflows verified; handset capture not verified.
Conditions to remove "conditional":
- Physical-device pass: Android handset import/record/permission denial, iOS Safari import/playback, tablet widths — per
LAUNCH-READINESS.mdPhase 2 andRESPONSIVE_COMPATIBILITY_REPORT.md. Until then, no "mobile-verified" claim (P7). - 11-viewport matrix: Re-run headlessly at 0.5.0 (last run v0.1.3 per
RESPONSIVE_COMPATIBILITY_REPORT.md:111). - 5–10 user interviews: Small-cohort protocol per
LAUNCH-READINESS.md:55–59(task completion, time, zero recording loss, confusing controls). - S-006 branch cleanup: Owner confirmation (outstanding per RELEASE_ACCEPTANCE_REPORT).
Without conditions: ScreenNote 0.5.0 is NOT READY for handset-claimed release. Desktop-browser + import + share + comment loop is verified working (live smoke on production). Do not market handset capture as verified until physical-device pass exists.
Overall score: 78/100 per RELEASE_ACCEPTANCE_REPORT scorecard. Core 17/20, E2E 15/20, UI/UX 12/15, Responsive 6/10, Arch/Data 8/10, Security 8/10, Perf 4/5, A11y 4/5, Ops 4/5.
Review generated 2026-11-08 as part of ScreenNote flagship-excellence final phase. All findings source-evidenced. No hypotheses published as fact.