Case study 06 / 18 · Websites & apps
VisualLabs
Contribution: Landing page, dashboard design and UI
A video review and delivery platform that brings projects, media versions, timestamped feedback, approvals, and shared review links into one workspace. Background processing prepares uploaded media for playback and delivery.
Case study
VisualLabs is a video review and delivery platform with separate web, API and worker applications. My contribution was on the design side: the landing page, the dashboard designs and parts of the interface.
The problem
Uploading media, collecting client feedback, choosing versions, approving and delivering usually happen in different places. VisualLabs keeps all of it attached to the same project and asset records.
What was built
- Project dashboards, versioned uploads, a shared player and background media processing.
- Authenticated review and public share links, with member and guest identities.
- Comments and replies, approvals, client feedback, exports and project reports.
Key decisions
- Media processing runs in a separate worker, away from interactive requests.
- One player surface is reused across project, folder, review and share views.
- Organisation membership controls access, and media is served through signed URLs.
- An asset’s current version and its approval state are tracked separately.
Where it stands
Substantially built, with production deployment procedures documented.
How it was built
Frontend
- Next.js
- React
- TypeScript
- Zustand — Client state
- Socket.IO client — Live review updates
Backend
- NestJS — API for projects, reviews, approvals and sharing
- Prisma
- Socket.IO
- BullMQ — Queue that hands uploads to the media worker
Data
- PostgreSQL
- Redis
- MinIO — S3-compatible media storage served through signed URLs
Integrations
- Adobe Premiere Pro plugin — Brings client feedback onto the editing timeline
Infrastructure
- FFmpeg — Prepares uploaded media for playback and delivery
- Docker Compose
Testing
- Vitest
- Playwright