UI/UX Designer — Hamburg

Interfaces that make complex products feel simple.

I design mobile apps and web platforms — starting from user flows and information architecture, ending in interactive Figma prototypes and consistent interfaces.

Tools
Figma, FigJam, Framer
Portrait of Hedieh Farhumand

Selected Work

Three projects, three product challenges — mobile UX systems, a responsive redesign, and e-commerce personalization.

01 — Main Case Study

Cooksy

Personalized meal planning app

A mobile app that turns weekly meal planning into a short guided flow — from dietary preferences and pantry constraints to a ready shopping list. Designed end-to-end in Figma, from early concept screens through a refined final flow.

UX/UI Mobile App Prototyping Figma
View case study
02 — Completed

Yoga with Deni

Responsive booking experience redesign

A responsive redesign of a yoga studio's website, focused on clearer class discovery, simpler booking, and a calmer visual hierarchy across devices.

Responsive Web Information Architecture UX/UI
View case study
In development
Interface preview — final screens landing soon
03 — Work in Progress

Violet Diamond

Personalized fashion e-commerce

A concept that pairs a traditional fashion shop with a "Get Styled" recommendation flow — helping shoppers move from browsing to a confident outfit decision.

UI Design E-Commerce Personalization
Coming soon
About

I'm a UI/UX designer with an analytical background and a focus on turning complex problems into clear digital experiences. My Master's in Organic Chemistry shaped the structured way I approach systems, information and problem-solving — a mindset I now bring into product design.

Skills

Focused on what's directly relevant to UI-led product design roles.

Interface Design

  • UI Design
  • Visual Hierarchy
  • Responsive Design

UX

  • User Flows
  • Information Architecture
  • Interaction Design

Systems

  • UI Consistency
  • Prototyping

Tools

  • Figma
  • FigJam
  • Framer

Let's talk.

Cooksy

A personalized meal planning app

Role
UX/UI Design, Research, Prototyping
Timeline
4 weeks
Tools
Figma, FigJam, Maze
Cooksy groceries screen
Cooksy meal plan start screen
Cooksy build a meal plan screen
The challenge

Planning meals for a full week means repeating the same decisions.

Decision overload

Repeated meal choices make everyday planning demanding.

Starting over each week

Planning repeatedly from scratch creates unnecessary work.

Forgotten ingredients

Meal decisions and required ingredients can become disconnected.

Disorganized shopping

Without a connected plan, grocery preparation becomes fragmented.

Personalization before planning

Cooksy asks a few questions before planning begins.

Diet, allergies, dislikes and household size are captured upfront, shaping the planning experience that follows.

Pick your diet screen

Diet — dietary style

Allergies screen

Allergies — items to exclude

Dislikes screen

Dislikes — personal preference

Servings screen

Servings — household size

Core product flow

One connected path, not a set of separate screens.

Preferences
→
Planning scope
→
Build plan
→
Review
→
Groceries
Designing the meal-planning logic

Scope is defined before a single meal is chosen.

Before building the plan, the person defines whether to plan the whole week or tailor it to selected days or meals. The build step then gives meals a specific place in that structure, and the review step lets the resulting plan be checked before it's confirmed.

01 — Planning scope
Planning scope screen, one original screen showing shopping list and scope choice

Whole week, or tailored.

The shopping-list area and the scope choice — full week or specific days and meals — live on this one screen.

02 — Build plan
Build a meal plan screen, Monday, with Confirm Plan visible

Meals get a place in the week.

Each day is broken into breakfast, lunch and dinner, filled to match the scope just defined.

03 — Review
Plan review screen, Monday's full breakfast, lunch and dinner

One last check before confirming.

Every day's meals and portions are listed for a final look before the plan moves forward.

Key design iteration

From recipe selection to actual meal planning

The earliest concept treated meal planning as recipe browsing. The revised product treats it as building a structured week — this is a change in product logic, not a visual redesign.

Before
Before: Build a meal plan, recipe browsing screen, with Preview plan visible

Recipes could be browsed and selected freely, but this created no real weekly schedule — each day still had to be decided individually.

→
After
After: Build a meal plan, structured weekly screen, with Confirm Plan visible

Recipe selection now happens inside a defined weekly structure, organized by day and meal type.

The change wasn't visual polish — it was turning recipe browsing into structured weekly planning.

From meal plan to groceries

Planning doesn't end at the plan. It continues into shopping.

Plan transition confirmation screen

Plan transition

Groceries list screen

Grocery list, generated from the plan

Grocery additions screen

Frequently bought items

Add shopping item screen

Adding an item manually

Interface states

One recipe, three views.

Nutrition facts, ingredients and instructions are three states of the same recipe detail screen, switched with a shared tab pattern.

Recipe nutrition facts screen

Nutrition facts

Recipe ingredients screen

Ingredients

Recipe instructions screen

Instructions

Interface consistency

Recurring patterns hold the product together.

Consistent navigation

The same bottom-navigation logic appears across Meal Plan, Groceries, Favorites and Settings.

Recurring card layout

Recipe content uses the same visual structure across browsing and planning contexts.

Shared action placement

Primary actions — Add Meal, Confirm Plan, Continue, Finish — repeatedly appear in predictable areas.

Tabbed content switching

Recipe-detail states share one tab pattern for Nutrition Facts, Ingredients and Instructions.

The final product

Cooksy today.

Learnings

What the iteration made clear.

01

Structure before flexibility. Designing the weekly planning experience showed how important it is to establish a clear structure before adding more flexibility.

02

Design the connections, not only the screens. Cooksy became more coherent when meal planning, review and grocery preparation were considered as parts of one continuous experience.

03

Iteration can change the product logic. Moving from collecting recipes to assigning meals within a weekly structure showed that meaningful iteration can change how a product works, not only how it looks.

Cooksy became stronger once it supported the decisions behind a week of meals, not just the recipes themselves.

Next project
Yoga with Deni
→

UX/UI Redesign

Yoga with Deni

Redesigning a local yoga experience to make class discovery and booking clearer.

Role
UX/UI Design, Research, Prototyping
Timeline
4 weeks
Tools
Figma, FigJam
Yoga with Deni homepage
Classes overview screen
7-Class Pass booking screen

The Challenge

Finding a yoga class shouldn't feel harder than booking one.

The existing experience made it difficult to quickly understand which class was suitable, find essential information and feel confident about the booking process.

Finding the right class

Users needed a faster way to understand which classes matched their experience level.

Information overload

Dense content and weak hierarchy made important information harder to scan.

Booking uncertainty

The booking journey needed clearer guidance and stronger trust signals before commitment.

Research

Research pointed to clarity, orientation and trust.

23
Survey participants
8
Interviews
5
Competitors analyzed
Insight 01

Level needs to be obvious

Users wanted to know whether a class was suitable for their experience level before exploring it further.

Insight 02

Essential information should be easy to scan

Class times and key information needed to be accessible without searching through dense content.

Insight 03

Trust matters before booking

Moving into a booking process — particularly across different pages or services — required clearer reassurance and context.

Information Architecture

Make the choice understandable before asking users to interact.

Instead of presenting classes as a flat collection of options, the final structure organizes them around experience level — helping users understand where to begin before opening a class.

Classes overview grouped by experience level: For Beginners, For All Levels, For Advanced Practitioners

Key Design Iteration

From filtering to direct discovery.

The first approach introduced filters for style, duration and level. But with only 5–6 classes available, filtering added interaction without adding meaningful value.

Before

With filters

Earlier design with filter dropdowns for style, duration and level

Users had to make selections before seeing which small set of classes might suit them.

After

Grouped by level

Final design grouped by experience level

Grouping the complete offering by experience level made the available options visible immediately.

The iteration removed an unnecessary interaction and made the information architecture do more of the work.

Core User Flow

One continuous path from discovery to booking.

Once users find a suitable class, the experience carries the decision forward — from understanding the class to selecting a booking option and completing payment.

01 — Discover
Classes Overview
Classes overview
→
02 — Understand
Strong Evening Yoga Flow
Class detail: Strong Evening Yoga Flow
→
03 — Book
7-Class Pass Booking
7-Class Pass booking screen
→
04 — Complete
Payment / Booking Summary
Payment and booking summary screen

Interface States

One booking structure, different ways to join.

Rather than creating separate booking experiences, the interface keeps the calendar and available classes consistent while allowing users to switch between three booking options.

01 — 7-Class Pass
7-Class Pass booking state
02 — Drop-in
Drop-in booking state
03 — Trial
Trial booking state

The interaction model stays familiar while the booking context changes.

Trust Before Commitment

Give people enough context before asking them to book.

Trust was treated as part of the experience rather than a final conversion element. Instructor information, participant feedback, class details and a clearer booking journey help users understand who they are booking with and what to expect.

About Deni page
Participant testimonials from the homepage

Beyond The Booking

The experience continues after a class is booked.

The signed-in experience gives returning users a place to review upcoming classes, revisit class history and manage account preferences.

Dashboard showing upcoming classes and class history
Profile and account screen

Final Product

Yoga with Deni, redesigned.

A clearer experience that connects class discovery, detailed information and booking within one consistent product.

Final Homepage
Final Classes Overview
Final Booking
Final Upcoming Events

Learnings

Simplification should match the scale of the product

The filter iteration showed me that more interaction does not necessarily create more value. With a small class offering, clearer structure was the better solution.

Trust is part of the user flow

Booking decisions depend not only on the final CTA, but also on the information and reassurance users receive before reaching it.

Design beyond the conversion point

Extending the experience into booking, payment and account management helped me think about the product as a continuous relationship rather than a single transaction.

Yoga with Deni became clearer by reducing unnecessary choices and connecting discovery, trust and booking into one continuous experience.

Next Project
Violet Diamond →