YesChef’s cooking classes needed a product experience that helped viewers find and return to the lessons they wanted. Shahzaib’s work covered the frontend, onboarding and recommendation surface around that content.
A library can attract attention with its content, but the application still has to help someone decide what to watch. The next useful lesson differs by taste, interest and earlier viewing.
That discovery experience also has to lead smoothly into video playback across devices. Onboarding, recommendations and the player belong to the same journey.
The Next.js and React frontend supported browsing and watching classes across devices. Performance work addressed the experience around the video content.
Onboarding collected taste preferences, and the recommendation surface personalized the next lessons a viewer saw. TypeScript and Cloudflare were part of the supporting application and delivery stack.
The engineering connected the catalog to a more personal discovery and viewing flow. The delivered scope covered what viewers saw before a lesson as well as the interface through which they watched it.
Content products depend on the relationship between catalog metadata, personalization and delivery infrastructure. A replacement team needs to understand those dependencies and the account access behind them. Maintaining that map makes it easier to change the frontend without losing the viewing journey.
Project contribution: Shahzaib. The scope described above identifies the work behind this case.
Editorial review: Ego Eimi · Updated September 6, 2026 · About the team
Your technology
Start with the business
Tell us which system matters, what has changed and who controls it. We will define a reviewable next step. Read Foundation and the commitments and evidence.
