Movie discovery, personal profiles, and shared viewing need to feel like one coherent product.
The implementation
What I built
Built the discovery interface and connected profile, recommendation, playback-progress, and watch-party workflows across the frontend and API.
React
FastAPI
MongoDB
Redis
Python
HLS
Features
Browse films by genre and language
Keep profile-specific lists and viewing history
Explore shared-viewing and recommendation workflows
Architecture
React application with profile context and routed discovery screens.
FastAPI services with MongoDB persistence, Redis/Celery work paths, and recommendation modules.
Separate streaming, catalogue, and watch-party integrations.
Engineering decisions
Keep profile state distinct from account identity.
Separate browsing and recommendation concerns from playback and payment actions.
Validation and measured results
Current source contains the routed discovery, profile, recommendation, and shared-viewing interfaces.
The recorded interface capture is preserved whole. Current local catalogue loading did not complete during review; no live playback, payment, or recommendation-quality check was performed.
No user count, revenue result, streaming capacity, or recommender accuracy is inferred from the interface.
Limits and unfinished work
Backend/provider availability determines catalogue, recommendation, and playback behavior.
A watch-party interface is not a measured concurrency result.
Source was not anonymously accessible under the former portfolio URL on 14 October 2026.
