Feedback arrives out of context
Album changes often show up as email paragraphs, screenshots, or vague spread references.
Online album proofing
Album proofing without the email chase.
Upload exported album design files, send one private flip-through proof, and collect precise client comments without account setup or scattered email threads.
Private proof linksPinned spread commentsVersioned revisionsCSV feedback export
Client proof preview
Secure proof link
Tokenized URL for client review.
Pinned comments
Feedback stays on the spread.
Approval record
Decision tied to the version.
Problem
Album review breaks down when feedback leaves the design.
Album Approve keeps every note, revision, and decision connected to the proof your client is reviewing.
Client portals add friction
A proof should be easy to open, review, comment on, and approve without another account setup step.
Approvals need a record
Studios need comments, revisions, approvals, and exports tied back to the album version being reviewed.
Product
A focused review loop from upload to approval.
The app starts after the album design is ready: upload the exported spreads, share the proof, gather exact feedback, and keep a record of what changed.
01
Upload
Add exported JPG, PNG, or PDF album spreads to a project.
02
Share
Create one private proof link for the client review.
03
Comment
Collect pinned notes on the exact spread that needs edits.
04
Approve
Track revisions, resolve notes, and capture the decision.
Use cases
Built around the moments studios repeat.
Album Approve is intentionally narrow: final album proofs, client comments, revision rounds, and production handoff.
Wedding album reviews
Send a polished proof link after the album design is ready and keep feedback tied to each spread.
Client revision rounds
Replace spreads, create new versions, and preserve the review history for the project.
Studio handoff
Export CSV feedback so production notes can move cleanly into the next step of the workflow.
Client experience
One private link. No training required.
Clients move spread by spread, click the part of the layout that needs attention, and submit approval when the album is ready.
Architecture and features
Review features with clear server boundaries.
Server Actions handle mutations, data access is centralized, and external services are isolated behind server modules so the app can run locally and move toward hosted infrastructure.
Versioned proof model
Projects contain album versions, spreads, comments, share links, approvals, and subscription state.
Validated uploads
JPG, PNG, and PDF imports validate file type, extension, size, storage-key safety, and dimensions where available.
Dashboard operations
The studio dashboard handles uploads, replacements, proof links, comment resolution, revision rounds, and CSV export.
Security and trust
Private proofs, scoped access, and auditable decisions.
The security model keeps dashboard users and proof guests separate while avoiding direct exposure of storage keys.
Hashed proof tokens
Share tokens are generated with cryptographic randomness and stored as HMAC hashes.
Signed asset access
Album spreads are served through signed asset routes instead of exposing private storage keys.
Scoped review sessions
Dashboard access uses signed HTTP-only sessions, while proof access is scoped to share tokens and optional proof cookies.
Workflow inputs and service boundaries
Connects where the review workflow actually needs it.
Keep handoff simple with file imports, CSV export, tokenized proof links, and isolated service boundaries for data, billing, email, and private storage.
Design file inputs
JPG, PNG, and PDF imports become reviewable proof spreads.
Feedback export
Project comments can be exported as CSV from the studio dashboard.
Supabase-ready data
A Postgres migration exists for studios, clients, projects, versions, spreads, comments, approvals, and subscriptions.
Billing and email boundaries
Stripe checkout/webhook and Resend email boundaries are isolated behind server modules with local stubs.
Private storage target
The local storage layer is designed to move to Supabase Storage or S3-compatible private object storage.
Client share link
Clients can review, comment, request changes, or approve from a tokenized proof URL.
Studio workspace