Project Foodie
Overview & Architecture
Platform Architecture & Design
Limited Release Beta
Metrics & Iteration
Production Hardening
Public Launch
Cross-Platform Web Expansion
Technical Challenges
Real-Time Multimedia Orchestration
The core challenge was synchronizing high-fidelity video streams with dynamic, context-aware UI elements, all while maintaining sub-second responsiveness for a user standing at a stove with messy hands.
Dynamic Content Scaling
Ingredient quantities needed to scale intelligently across serving sizes, and cooking measurements don't scale linearly. A "pinch" doesn't become two pinches. Tablespoons convert to cups at specific thresholds. We built a measurement engine that understood culinary conventions, with override capabilities for edge cases.
Synchronized Video Architecture
Frame-accurate event triggers coordinated with streaming video content. The system needed to handle network variability, buffer management, and user seeking while maintaining synchronization between video playback and interactive overlays: timers, step indicators, ingredient highlights.
Event-Driven Content System
We architected a Django-based content management system that treats recipes as event timelines rather than static documents. Content editors author experiences by placing triggers on a video timeline, and the system handles the real-time orchestration during playback.
Platform Design
Synchronized Cooking Experience
Every recipe is a multimedia experience with multiple synchronized content streams: video, timers, instructions and ingredients, all coordinated in real-time.
Headless Content Architecture
The backend separates content from presentation entirely. Recipe data, video assets, timing metadata, and measurement rules live independently, and the client applications compose these into experiences. This enabled rapid iteration on the editorial side without app updates.
Tiered Access Control
The platform implements three access tiers with progressive feature unlocking: anonymous browsing for discovery, authenticated free users with favorites and grocery lists, and subscribers with full catalog access plus commerce integrations. Each tier required different caching strategies and content delivery optimizations.
Commerce Integration Layer
Deep integrations with Amazon and Instacart allow users to purchase tools or order ingredients directly from the recipe context. The affiliate layer earns revenue without getting in the way. One tap from "I need this pan" to cart.
Resilient Timer System
Cooking timers persist across app state changes and system interruptions. Background execution, push notification fallbacks, and state recovery ensure users never miss a timing cue, even if they leave the app to answer a call or check another recipe.
Platform Recognition
Who We Built It For, and When
The Intellectual Property Corporation, 2015–2017.
ClearSummit built Project Foodie for the Intellectual Property Corporation, the Emmy-winning production company behind it, working with the platform's creators, producer Eli Holzman and The Meatball Shop's Daniel Holzman.
Work began in 2015. A first iteration went live to a limited group of users in November 2016; the team gathered usage data, and a redesigned version launched in October 2017. When Android demand followed, we built a React web version so that audience could reach the full content library, a deliberate trade against duplicate native development, made to fit the client's budget.
Project Foodie was acquired by Sony, and ClearSummit stayed with the platform: Sony engaged us directly for support work on what we had built.
Build Your Platform
If you are building something like this, tell us what you are trying to do.