CREATIVE PRODUCTION / LOCAL-FIRST APPLICATION
CLCKD — Clicked. Clocked. Done.
Keep the work moving. Keep the context together.
A connected production desk for independent videographers, photographers and small studios—from the agreed brief to the final handover.
01 / PROBLEM & VALUE
One production. Less scattered context.
The brief, shoot times, client feedback and payment reminders live in different tools. It becomes hard to see the next agreed step and what is holding it up.
Connect the client, project scope, shoot, tasks, output versions and external payment schedule inside one local workspace.
Make handovers and dependencies easier to follow. Keep approval, delivery and payment separate, with retained versions and recorded decisions rather than overwritten context.
02 / WORKFLOW
From first brief to final handover.
Implemented in the local application. This portfolio page is a visual case study, not a live application or client portal.
Clients & projects
Contact records, linked productions, guided project creation, a named approver and agreed output scope.
Production planning
Shoot dates, local call times, IANA timezones, locations and crew notes stay attached to the project.
Actionable tasks
Project-based work with priorities, deadlines and status updates, surfaced alongside upcoming production.
Versioned reviews
HTTPS review links, revision history and operator-recorded approvals or change requests. Earlier versions and feedback are retained.
Delivery records
Record external handover for a specific approved version. A project can wrap only when all active outputs are delivered.
External payment tracking
50/50, 30/30/40 or custom milestones. Manually recorded external receipts can gate production, editing or delivery; no money moves through CLCKD.
03 / SCREENSHOTS
Real screens. Fictional productions.
Explore the production workflow with fictional clients, projects and payment records.
A fictional 30/30/40 schedule with operator-recorded receipts—not bank verification or payment processing.
A second version awaiting review, with earlier feedback retained. The example links do not demonstrate film playback.
The owner’s preview of client-facing progress, not an authenticated guest session or a public client portal.
04 / WALKTHROUGH
See a production move from brief to delivery.
A recorded walkthrough of the local application: dashboard, scope, shoot planning, revisions, delivery, external payment milestones and the owner’s client preview. Demonstration data; no payments are processed by CLCKD.
05 / ARCHITECTURE
One application. Local relational storage.
The CLCKD application is separate from this portfolio website. No application database, session or owner credential is connected to this page.
Write path: browser → Server Action → access checks → validation and repository → SQLite. Pages read through server-side access checks and repositories.
- Interface
- Next.js App Router, React and CSS Modules: rendered pages and contextual production controls.
- Application logic
- Strict TypeScript and Server Actions: requests enter server-side access checks before mutations.
- Validation
- Zod schemas and domain repositories: validate input and enforce workflow transitions.
- Persistence
- SQLite via better-sqlite3: parameterized SQL, foreign keys and transactional, versioned migrations.
- Verification
- Vitest integration/unit tests with isolated databases; TypeScript, ESLint and production build checks.
06 / PRODUCT SCOPE