Baratie

Why this project matters to me

Baratie was my first mobile app and I wrote every line myself, without AI. Today I build most prototypes with AI coding agents — and this project is the reason I can review what they write, scope work realistically and talk to engineers about it.

The theme came from the course brief's freedom to pick any topic: the Baratie is the floating restaurant in One Piece, so the app got a comic font, an ocean palette and a fish chef as its mascot, Captain Redgill — the one part I generated with AI.

What it does

• Recipes — browse all categories from TheMealDB, with your own recipes mixed in.
• Daily special — one featured dish, refreshable if you want something else.
• Search — any dish by name, straight from the API.
• Add — your own recipe with ingredients, instructions and a photo from the camera roll.

Under the hood

The API returns every recipe with twenty separate ingredient and measure fields. A small mapping layer turns that into a clean list before anything reaches the UI, so the screens never have to know what the API looks like. User recipes live in a shared React context and use the same shape, which is why they can sit next to API recipes in the same lists.

Navigation runs on file-based routing with five tabs and stacked detail pages.

What I'd do differently

Own recipes are kept in memory only — close the app and they're gone. That was a deliberate scope cut for the deadline, but it's the first thing a real user would notice. Next time: local persistence first, polish second.