← All work

Product design & build

Mellav

Designing and building a bilingual pet-care app that puts an animal's daily routine and health history in one place, so owners can see how their pet is doing at a glance.

Client
Mellav, my own product, in development in Athens
Role
Founder: product, UX/UI design and full-stack development
Duration
March 2025 to now (MVP built, ongoing)
Team
Solo, with AI-assisted code review (Claude)
Tools
React Native (Expo), Go, AWS (DynamoDB, S3, SES), HTML/CSS/JS, English and Greek i18n
Deliverables
iOS/Android pet owner app, web app, Go API, design tokens and a custom icon set

In short

Mellav is a pet-care app for owners. It brings an animal's health records, daily activities, meals, reminders and documents into one place, in English and Greek. I designed and built the MVP end to end: a React Native app for iOS and Android, a web version, and a Go and AWS back end. The core idea is one animal with four tabs, each answering one question an owner asks every day. Above them sits an Overview that answers the most important one, "how is she doing today?", before the owner has to look for it.

About

Mellav is a product I started after moving back to Greece. It's for people who look after an animal day to day and want its care and its history in one place they actually open. The MVP is the owner journey: signing up, adding animals, logging care and getting reminders. It's built and running against a live API.

Scope

Design and build an owner app that makes everyday care quick to log and easy to see at a glance, in two languages, with an account area that gives owners control of their own data. Vet access was designed alongside it but deliberately left out of the MVP (see Future development).

The problem

Care is daily, records aren't

Walks, meals and medication happen every day, but health history usually lives in a paper booklet or at the clinic. Owners needed both in one place.

Too much to remember

Feeding times, tablets, flea treatment, booster dates. Each is easy on its own, but together they slip. The app had to remember them for the owner.

Two languages, one product

The audience is Greek-first, with English-speaking owners too. Every screen, reminder and fact had to work in both languages from the start.

What I wanted to achieve

  • An owner can see how their animal is doing today in under five seconds.
  • Logging care (a walk, a meal, a vaccine) takes one tap or one short form.
  • Nothing time-sensitive depends on memory: meals, medication and preventative care can all send reminders.
  • One visual system across the mobile app and the web app.

My role

Product
Defined the MVP and its structure (one animal, four tabs, an Overview on top) and decided what stayed out of version one.
Design
Designed every screen of the owner journey, the design tokens and a custom set of 32 icons (15 in filled and outline pairs, plus two single icons).
Build
Built the owner app in React Native (Expo), the web app in HTML, CSS and JavaScript, and the Go API on AWS, with English and Greek throughout.
Data and privacy
Designed the account area around the owner's control of their data: editing details, choosing a language, exporting data and requesting deletion.

The product: four tabs, one animal

Everything hangs off the animal. Owners land on a list of their animals, tap one, and move between four tabs that each answer a single question.

  1. 01 · Overview

    How is she today?

    Today's care score, next meal, activities done and health in a glance.

  2. 02 · Health

    What's her history?

    Weight chart, vaccines, medications, preventative care, vet visits and documents.

  3. 03 · Activities

    What needs doing?

    Daily or weekly routines, ticked off as they happen.

  4. 04 · Meal & Diet

    What does she eat?

    Feeding schedule with reminders and a daily summary.

Main screen
Overview screen
Health screen
Dashboard, Overview and Health, rebuilt from the app's source code: its own colours, radii, spacing and icons. The animal's photo and name stay in the top bar on every tab.

Overview, in practice

The Overview screen is a summary of the other three tabs. Each block answers one question and links to the tab that holds the detail, so owners rarely need to dig.

What the Overview shows first

Today's care, as hearts

Five hearts. Opening the app fills one, and each activity completed today fills another (up to four). It's a gentle nudge rather than a streak to lose.

The next thing due

The next meal sits right under the animal's name, with time, product and portion. It answers "have I fed her?" before it gets asked.

Health without the detail

Counts for vaccines, medications and vet visits, with the next and last dates, so owners can see a gap without reading the history.

Logging care, in practice

Every tab uses the same pattern, so learning one teaches the rest. A card has a title, an icon and a round "+" button. Each row shows the item and its key detail on one line, with a ⋯ menu to update or delete. Adding something opens a short form with a reminder switch where it makes sense. Health holds six kinds of record (weight, vaccines, medications, preventative care, vet visits and documents), and none of them needs more than one form to add.

Activities screen
MealDiet screen
AddAnimal screen
Activities (the action menu open on one row), adding a feeding time with a reminder, and adding an animal with a photo from the library or the camera.

Reminders that don't need remembering

Meals: each feeding time can send a daily reminder at the time it's due.

→ set once, when the meal is added

Medication: each tablet or dose follows its own schedule, from twice daily to monthly.

→ follows the dose's frequency

Preventative care: flea and tick, deworming and check-ups come round on their own schedule.

→ each with its own frequency and next due date

Getting started and staying in control

Signing up is one short form. The account area is where owners manage everything else: personal details, address, password and language. Privacy and data controls (privacy policy, data export and account deletion) are designed in from the start rather than added later.

Login screen
MyAccount screen
Log in, and My Account with personal details, language choice, security, and privacy and data controls.

Design system, in practice

The tokens live in code, not in a separate file that can drift: one set of colours, radii, spacing and type sizes, shared between the mobile theme and the web stylesheet. The icon set was drawn for the product. Most icons come in a filled and an outline version, so the tab bar can show which section is active by its shape as well as its colour.

Colour tokens

  • primary #264653
  • accent #2A9D8F
  • background #C2DFDB
  • danger #E76F51
  • text #102A43
  • summary card #F7FAFB

Radius: input 10, card 20, pill 999. Spacing: 4, 8, 12, 16, 20, 24, 32.

Icon set: 32 icons, most in filled and outline pairs

  • overview
  • outline
  • health
  • outline
  • activities
  • outline
  • feeding
  • outline
  • vaccines
  • outline
  • medication
  • outline
  • vet visits
  • outline
  • weight
  • outline
  • prevention
  • calendar
  • summary
  • fun fact
  • documents
  • upload
  • photo
  • clock
The tokens as defined in the app's theme files, and the custom icon set. The same values drive the mobile theme and the web stylesheet.

Built for two languages and daily use

~375interface strings in the mobile app, each in English and Greek
100pet-care facts across 10 themes, one shown each day
3kinds of local reminder: meals, medication and preventative care
10owner-app screens, from log-in to account and data controls

Outcomes & reflection

The pet owner MVP is built and running against a live API on AWS, on iOS, Android and the web, in English and Greek. It covers the full journey: sign up, add animals, log health records, routines and meals, get reminders, and manage your own account and data.

What I'd do differently: I'd put the app in front of owners much earlier. Every screen was reasoned through, but it hasn't yet been tested with real owners, and that's the next step before launch. I'd also set the technical bar sooner. A code review of the MVP found security gaps in how sessions are handled, which are being fixed before launch. Account deletion currently only flags a request and needs to become a real delete.

Future developmentBringing vets in

The next phase gives vets access to a pet's record, without the owner losing control of it. It's designed and its back end is built, but it's switched off until the owner experience is proven. Instead of a single "share with my vet" switch, owners get three ways to grant access, each with its own limits.

Primary vet

An ongoing relationship the owner sets up, like a family doctor. It covers their animals by default and can be removed at any time.

standing · read-only

Appointment

Booking a visit gives that vet access to that animal for the day of the visit, and lets them add a signed consultation note.

tied to the booking

Temporary (QR)

For when there's no booking: travelling, a second opinion or a one-off test. The owner picks what to share and for how long.

scoped · ends on its own
WhoCanSee screen
VetCalendar screen
Designed, not yet released: "Who can see my pets" for owners, and the vet's calendar, where every appointment leads to the patient record and the consultation.