Cookidea Brand and UX Development

Cookidea is a social app built around cooking. Not a recipe database, not a food blog. A place where people share what they cook, discover what others are making, and save ideas for later. Think Instagram, but the content is recipes and the community is built around the kitchen.

When I joined, the concept existed but nothing visual did. No brand, no design system, no screens. My job was to take the idea and turn it into a real product: brand identity first, then the full app design.

The audience is home cooks, food lovers, people who scroll through recipes the way others scroll through reels. The brand had to feel warm and approachable (cooking is personal, not corporate) but structured enough to scale as a digital product with complex features.

I built the foundations:

Color palette: warm tones that feel appetizing without being cliché

Typography: readable at small sizes (recipe cards, ingredient lists) but with personality in headlines

Logo: simple enough to work as an app icon, distinctive enough to be remembered

Overall visual direction that bridges social media energy with utility

Every brand decision was filtered through one question: does this feel like something you'd open while cooking dinner?

Once the visual direction was validated, I built the design system. This is where the brand stops being a mood board and becomes infrastructure.

The system includes:

Color tokens mapped to semantic roles (primary, secondary, surface, error, etc.)

Typography hierarchy: 6 levels, tested against real recipe content

Spacing system based on an 8px grid

Reusable components: buttons, cards, inputs, navigation elements

The goal wasn't just visual consistency. It was development speed. When the engineering team picks this up, every component is named, documented, and ready to implement without guessing.

Before building the app, we needed to validate interest. I designed a waitlist landing page with one job: get signups.

I started with the page structure before touching any visuals. The key challenge was communicating that Cookidea is a social platform, not just another recipe site. Every section had to reinforce the community angle.

Once the wireframe was validated, I designed the page using the brand system. Full alignment with the tokens, components, and visual language established earlier. No one-off styles.

This is where the project shifted from brand to product.

I mapped out the full application architecture: what screens exist, how they connect, and what the user does at each step. Feature prioritization was critical here because the team had more ideas than development capacity.

The core flows I designed:

Publishing a recipe: the primary creation flow. Had to be fast enough that someone would use it mid-cooking, but structured enough to produce useful content

Exploring content: browse by category, trending, or people you follow

Saving recipes: one-tap save with personal collections

Creator profiles: see someone's full recipe history, follow them, get notified

Every flow was built in FigJam first as a low-fidelity map, then validated with the team before moving to UI.

This is where the real challenge started.

On the surface, a recipe-sharing app sounds simple. In practice, the product complexity escalated fast. The biggest example: ingredients.

We wanted users to freely add ingredients when posting a recipe. But we also needed:

Content moderation (people will type anything)

Interactive ingredients (tap to check off while cooking)

Future features like linking ingredients to nearby stores

These requirements created back-end questions that directly impacted the UI. How do you design an ingredient input that's freeform but also structured enough for a database? How do you show interactive ingredients without cluttering the recipe view?

Several screens had to be redesigned multiple times as technical constraints evolved. This wasn't scope creep. It was the natural tension between product ambition and engineering reality. My job was to find the interface that satisfied both without compromising the user experience.

Over 2 months, I built Cookidea's entire design foundation:

A complete brand identity system

A production-ready design system with tokens and components

A conversion-focused waitlist page

Full information architecture and user flow maps

The core app UI, iterated through multiple rounds of technical constraints

The project is now in engineering. The design system, screens, and documentation are built to hand off cleanly, so the dev team can implement without ambiguity.