StudioFlow
An independent capability project using fictional agencies, clients, projects, proofs and invoices. V3 offers a read-only Sample and a separate private 24-hour demo space. In your own space, submit a proof as Agency, switch to Client to comment or request changes, then prepare and approve a new version while retaining the earlier feedback. Files and project records are protected by server-side role and workspace authorization. No real payments or email delivery are configured.
01
Understand
Bring the delivery loop into one workspace.
The Agency Delivery Workspace keeps the current proof, delivery stage, milestones and recent activity together. Agency and Client views share the project record while presenting different responsibilities. Visitors can inspect a finished fictional Sample or open their own isolated space to work through a delivery.
02
Trust
Keep private files and review history accountable.
Private proof files are retrieved through authorized, short-lived downloads. Agency, assigned Team and Client permissions apply on the server to projects, files and decisions; changing the interface view does not bypass those checks. Each new deliverable version retains the previous proof and its feedback so that a later approval does not erase earlier review.
03
Act
Submit, revise and approve a real demo workflow.
In a private space, submit V1 from the Agency view, comment or request changes as Client, then upload a new proof, create V2 and approve the latest version. Activity and in-app notifications reflect those recorded actions. The shared Sample stays read-only; the personal workflow is bounded by quotas and a 24-hour expiry.
04 / Visual screens
a closer look.
A real 8 October 2026 HTTPS capture of the finished read-only Sample. The Agency workspace brings the project stage, current proof and approved version into one delivery view.
A real HTTPS screenshot from the completed 8 October 2026 V3 release acceptance. It shows the Client perspective of the same fictional delivery, with the authorized proof loaded and the shared Sample marked read-only.
A real 8 October 2026 HTTPS capture of the finished read-only Sample. The Agency workspace brings the project stage, current proof and approved version into one delivery view.
05 / Build notes
behind
the pages.
- Next.js and TypeScript interface, Java 17 / Spring Boot API, PostgreSQL with Flyway, and private S3-compatible object storage. The delivery workspace runs against the real backend rather than simulated browser-only success states.
- Spring Security object authorization combines Agency, assigned Team and Client roles with the visitor demo-space boundary. Server-side JDBC sessions, same-origin CSRF checks and authorized file downloads protect the workflow.
- Deliverables retain separate version records. Transactional feedback, change requests and latest-version approval preserve prior reviews and record project activity and in-app notifications.
- Uploads are bounded and validated for type and content; private objects are exposed only through authorized short-lived URLs. The public demo has no malware-scanning service, real payment processing or email delivery.
- The Portfolio Demo control layer separates the immutable Sample from private 24-hour spaces. Admission and action quotas, expiry and restricted cleanup limit the temporary fictional workflow.
- The frontend began with the MIT-licensed Kiranism next-shadcn-dashboard-starter foundation. Jon adapted that foundation and implemented StudioFlow's domain, security, workflow, integration and interface; the project does not claim every UI primitive was written from scratch.
Explore the finished read-only Sample, or try the Agency → Client review → new version → approval workflow in your own private 24-hour fictional space. No real payments or email delivery.
View demo ↗