Yummly Smart Cooking Platform

Designing connected experiences across smart hardware and mobile app

Designing connected experiences across smart hardware and mobile app

Designing connected experiences across smart hardware and mobile app

Designed end-to-end experiences across smart hardware and mobile apps to improve usability and support cross-selling within Yummly’s ecosystem.

Designed end-to-end experiences across smart hardware and mobile apps to improve usability and support cross-selling within Yummly’s ecosystem.

Designed end-to-end experiences across smart hardware and mobile apps to improve usability and support cross-selling within Yummly’s ecosystem.

Role:

Lead UX Designer

Team:

Product Manager, Engineers, Visual Designer, UX Writer

Duration:

5 months

WHAT'S YUMMLY?

Smart cooking made easier through connected devices


Yummly is a smart-cooking platform offering personalized recipes, guided cooking, grocery delivery, and integrations with connected kitchen devices.

About Yummly:

  • Personalized recipes & meal planning

  • Guided cooking with temperature tracking

  • Integrations with smart kitchen devices

  • Part of the Whirlpool ecosystem


  • 20M+ users

  • 2M+ recipes

  • 2017 acquisition by Whirlpool

PROBLEM

A fragmented cooking flow created friction.


Home cooks using both the thermometer and smart oven expected one seamless experience, but the app’s flow wasn’t designed for multi-device cooking.

Key problems:

  • No full control of oven from app

  • Inconsistent setup flows

  • Doneness selection came too late

  • No contextual guidance across proteins/cuts/appliances

  • Device owners expected more intelligence

    Key Insight: Users didn’t want automation alone — they wanted clear, consistent guidance.

Original Cook Setup Flow

Original Cook Setup Flow
RESEARCH APPROACH

Understanding real cooking workflows from Whirlpool data and user testings


Research Activities:

  • Whirlpool partner research

  • 5 early-concept tests

  • 5 high-fidelity usability tests

WHAT WE LEARNED

Users needed a unified, predictable cooking flow


Four insights that guided the redesign:

  1. Step-by-step > accordion

  1. Big images ≠ better

  1. Consistency builds confidence

  2. Multi-device cooking must feel unified

EARLY EXPLORATIONS

Reorganizing cook setup for multi-device workflows


Guided by research insights around consistency, early decisions, and multi-device clarity.


What we explored:

  • Added “Cook Method” to support oven vs non-oven paths

  • Introduced contextual tips based on protein, cut, and doneness

  • Standardized layouts for protein and cut selection

  • Integrated smart oven controls (mode, cavity, temperature)

FINAL DESIGN - SETUP FLOW

A consistent, guided setup across proteins & appliances



What changed:

  • Earlier doneness selection enables smarter guidance

  • Predictable, repeatable layouts across proteins and devices

  • Clear branching for connected vs non-connected ovens

FINAL DESIGN - COOK SET UP SCREEN

A clear, step-by-step setup with guidance from the start


Setup emphasizes early clarity, then adapts based on available devices — ensuring users feel prepared before cooking begins


FINAL DESIGN - COOK SCREEN

Real-time tracking and oven control without leaving the cook screen

Monitor progress, adjust oven settings, and update doneness in one continuous flow.


IMPACT/ RESULTS

Consistency, collaboration, and structured testing in IoT design



User Impact:

  • Immediate report drafting without document wait

  • Reduced IEP deadline stress

  • Workflow matched real psychologist process

Business Impact:

  • Validated PMF signals through sustained use

  • Strong NASP Conference engagement

  • Removed major workflow blocker

  • Informed roadmap for customization

Key Metrics:

  • WAU ↑ +15% (35% → 50%)

  • Sustained engagement post-Beta

  • High user satisfaction ratings


    Metrics based on Alpha to Beta launch comparison and post-launch analysis.

REFLECTION

Reflection & Learning



What I learned:

  • Engineering partnership early

  • Real-world workflow mapping is essential

What I’d do differently:

  • More structured testing roadmap

  • Plan for complex edge cases earlier

mari.design*

© 2026

mari.design*

© 2026