personalFeatured

STREAMIX – PWA Streaming Platform

Personal

Dec 2025 – Feb 2026 (Ongoing )

Team of 1

Full Stack Engineer

01 Problem

Streaming-style applications require careful handling of authentication, metadata ingestion, content discovery, and watch lifecycle management, even in non-commercial contexts.
Third-party metadata APIs return incomplete and paginated data, making naïve ingestion approaches unreliable.
Embedded video players do not expose reliable playback progress, complicating watch-state tracking.
Portfolio streaming projects are vulnerable to misuse if access is not intentionally restricted.
Supporting mobile, desktop, and large-screen devices introduces additional UX and performance constraints.

Built STREAMIX as a Progressive Web App that mirrors real-world streaming platform architecture rather than a UI-only demo.
Implemented Google OAuth using NextAuth with JWT-based sessions to support Edge-compatible middleware enforcement.
Designed a normalized relational schema for content, genres, seasons, episodes, and watch history using Prisma and PostgreSQL.
Adopted a database-first search strategy with TMDB and IMDb API fallback to reduce external API dependency.
Implemented lazy content enrichment on detail pages to fetch full metadata and genres only when required.
Handled paginated episode ingestion using nextPageToken to ensure complete series data storage.
Replaced unreliable iframe-based progress tracking with explicit watch history and watched-state management.
Implemented middleware-based grace period access control to prevent misuse while allowing legitimate exploration.
Built a responsive Netflix-style UI optimized for mobile, tablet, desktop, and TV-sized screens.
Added Progressive Web App install prompts with standalone detection and one-time user prompting.

01Architected and developed a full-stack streaming platform using Next.js with App Router, focusing on real-world scalability rather than a demo implementation
02Designed and implemented a normalized relational database schema (PostgreSQL) for content, genres, seasons, episodes, and watch history
03Integrated Google OAuth authentication using NextAuth.js with JWT strategy and Edge-compatible middleware validation
04Built a database-first content retrieval strategy with TMDB and IMDb API fallback to minimize external API dependency
05Implemented incremental data ingestion pipelines using paginated APIs (nextPageToken) to ensure complete and reliable dataset storage
06Developed watch history and playback tracking system
07Engineered middleware-based access control system with configurable grace periods to prevent unauthorized usage
08Optimized performance by: Reducing redundant API calls, Implementing lazy metadata enrichment, Ensuring efficient query patterns
09Built a responsive Netflix-style UI optimized for mobile, tablet, desktop, and large-screen devices
10Implemented PWA capabilities, including install prompts, standalone mode detection, and caching strategies
11Ensured clean, maintainable code with modular components, proper typing, and scalable folder structure

Implemented a scalable ingestion pipeline capable of storing 1,000+ titles and 10,000+ episode records without schema changes.
Reduced external API calls by approximately 70% through database-first querying and incremental enrichment.
Achieved sub-200ms average response times for home and browse APIs under local load testing.
Successfully enforced access restrictions after a configurable grace period with zero database lookups in middleware.
Delivered a fully installable PWA with consistent behavior across desktop and mobile environments.
Created a realistic full-stack reference project demonstrating system design, data modeling, and middleware-driven access control.

📈 Reduced external API dependency by ~70% through database-first querying and lazy enrichment

Single-developer project built to explore real-world streaming platform architecture and trade-offs

Next.jsReactTypeScriptProgressive Web App (PWA)

Next.js Route HandlersNextAuth (JWT Strategy)Prisma ORM

PostgreSQL

Vercel

Architecture Notes

Used JWT-based authentication to allow Edge middleware to validate sessions without database access.
Chose database-first search to minimize reliance on third-party APIs and improve response consistency.
Implemented lazy metadata enrichment to avoid ingesting unnecessary data upfront and reduce API cost.
Normalized genres into a separate table to enable efficient filtering, aggregation, and future personalization.
Handled episodic data ingestion using paginated APIs to ensure completeness and idempotency.
Avoided iframe-based progress tracking due to technical limitations, opting for explicit watched-state management.
Used atomic database updates for view counting to ensure correctness under concurrent access.
Introduced middleware-level grace period enforcement as a trade-off between accessibility and abuse prevention.
Designed PWA install prompts as opt-in and single-occurrence to avoid degrading user experience.

Interested in working together?

Let's discuss how I can help with your next project.