---
title: "Fitness Website Product Design Case Study | Parmis Meshgi"
description: "Fitness Website is a private shared health dashboard designed by product designer Parmis Meshgi."
canonical_url: "https://meshgi.com/fitness/"
html_url: "https://meshgi.com/fitness/"
author: "Parmis Meshgi"
location: "Toronto, Canada"
language: "en-CA"
last_updated: "2026-09-29"
---

> Fitness Website is a private shared health dashboard designed by product designer Parmis Meshgi.

Canonical page: [https://meshgi.com/fitness/](https://meshgi.com/fitness/)

[← Side projects](https://meshgi.com/playground/)

Independent product · Web

# Fitness

Keep two personal health records clear inside one shared daily view.

[Open the website ↗](https://fitness.meshgi.com)

![Fitness progress rings icon](https://meshgi.com/assets/playground/fitness.svg)

My role Product and UX design

Information model, controls, states, and privacy

Platform Private responsive web

Shared health and food record

Milestone August 20, 2026

One date pattern across the product

Core value Shared clarity

With distinct personal records

Project value

## Make daily health context useful without mixing two people’s records.

### What the design needed to achieve

- ✓

Keep Day, Food, and Progress easy to reach.

- ✓

Show one person’s food record at a time.

- ✓

Use the same date controls in every daily view.

Problem

### Daily context is scattered.

Movement, meals, totals, and progress lose meaning when each uses a different route.

Risk

### Shared can become mixed.

Two people can use one dashboard only when each record stays clear.

Direction

### Reduce the surface.

Keep three main views, one date pattern, and direct person selection.

Design decisions

## Use a small structure for repeated daily work.

01

### Keep three main views

Less navigation

The public dashboard keeps Day, Food, and Progress as its main routes.

Intended impact

Place the most common daily questions one step away.

02

### Separate each person’s food record

Clear ownership

Person tabs show only the selected person’s totals and meals.

Intended impact

Prevent a shared meal record from becoming a mixed personal record.

03

### Reuse one date pattern

Predictable control

Day, Food, and Progress place previous, next, calendar, and Today controls in the same position.

Intended impact

Let users change dates without relearning each section.

04

### Keep data movement protected

Private operations

The visible dashboard stays read-only. Protected agent and back-office routes handle imports and writes.

Intended impact

Keep everyday review simple while limiting sensitive actions.

Product proof

## The product structure supports daily review and safe correction.

Day

### One daily overview

The current date leads movement, status, and any urgent review cue.

Food

### One person at a time

Totals, meals, and the selected person stay together during date changes.

Progress

### Shared date controls

The same arrows, calendar, and Today action support comparison over time.

Result

## A private dashboard supports repeated health decisions.

Live evidence

### Three focused views

The production product uses the approved Day, Food, and Progress structure.

Verified boundary

### Protected writes

The visible dashboard stays read-only while private routes manage data changes.

Measure next

### Daily usefulness

Track date changes, review cues, corrections, and repeat visits. Public usage results are not available.

[Private product Open Fitness Website ↗](https://fitness.meshgi.com)

[Next side quest Orange Institute →](https://meshgi.com/orange-institute/)