The first time I opened Mela, on a Sunday morning in Menton, I made coffee instead of breakfast and read recipes for an hour. I had not done that with a piece of software in some years. The reading view is the kind of thing one notices on the second sentence and again on the eighth — typography that gets out of the way, line lengths that respect the eye, photographs given the room they were photographed for. I closed the app and made a soft-boiled egg, which is what I had been planning to make in the first place, but slowly.
Two days later, on a Tuesday at half past six, with leeks on the cutting board and a four-year-old asking, again, about pasta, I opened Basil. The reading view is fine. It is not Mela. What it is, that Tuesday, is the place dinner happens. Both things are true. They are also, on closer inspection, the entire comparison.
§ I.What Mela gets right
Mela is the work of Silvio Rizzi, who also makes Reeder, and the lineage shows. The whole product feels like a reader — calm, opinionated, deeply Apple-native, the kind of app that wins an Apple Design Award by being precisely what it intends to be and nothing else. The reading view, again, is the headline. Long-form recipes from food writers who can actually write are returned to their original dignity inside it.
The discovery model is borrowed, beautifully, from the world of RSS. You add the recipe sites you trust — a chef, a magazine, a cookbook author's blog — and Mela pulls in their new posts the way Reeder pulls in articles. There is no algorithm. There is no community. There is your taste, expressed as a list of sources, and the app updates politely when those sources publish. It is a quieter way of finding new recipes than any feed.
Imports are clean. Cooking mode exists and works. There are timers. The subscription is fair.
§ II.Where Basil differs
Basil and Mela have nearly identical answers on import quality. Both pull structured recipes from URLs reliably. Basil extends further into video and social — Instagram reels, TikTok, YouTube — which is where most of the recipes my friends actually share now live. If you save mostly from blogs, the difference is small. If your last ten saved recipes were videos, it is large.
The divergence widens past import. Basil's meal planner is a calendar you drag recipes onto, by day or by week or by month, with a glance that tells you what dinner is for the next seven evenings. The grocery list aggregates across that plan and groups by aisle, deduplicating ingredients across recipes — two pinches of salt do not become a separate line. Allergens tag at the household level and flag on every recipe automatically. Calorie and macro information is available on the recipes that have it, present without being pushed.
Mela does not really do these things, because Mela is not trying to. The product's restraint is part of the product. Basil is not trying to be a reader; Mela is not trying to be a kitchen operations app. Both choices are honest.
Mela is the right answer if you mostly read recipes. Basil is the right answer if you mostly cook them.
§ III.The deeper philosophy
There is a kind of cook for whom the recipe is the artefact — the thing to be saved, returned to, admired, shared. Reading recipes is, for this cook, an activity in its own right, separate from cooking them. A long Sunday-morning browse through the latest from a few favourite food writers is part of the pleasure of caring about food at all. Mela is built for this cook with a precision that almost no other app in the category attempts.
There is another kind of cook for whom the recipe is the instruction — the thing that has to work on a Tuesday at seven, with a child underfoot and the leeks already cut. The reading view matters less, because the recipe is not being read; it is being executed. What matters is whether the screen stays awake, whether the steps advance with a swipe, whether the shopping list is correct on Saturday morning, whether the app remembers that the household does not eat shellfish.
Most people are both kinds of cook at different hours of the week. The question is which one they are more often. The honest answer, for most home cooks I know, is the second. The Sunday-morning browse is the exception. The Tuesday-evening dinner is the norm. Software should be optimized for the norm.
§ IV.Who each is for
Mela is for the cook who reads. Who follows recipe writers the way other people follow novelists. Who cares deeply about typography and would resent a cluttered screen on the principle of the thing. Mela is, for this cook, almost certainly the most beautiful app on their phone — and one of the most justified subscriptions.
Basil is for the cook who is doing the cooking. Whose phone leans against a salt cellar at half past six. Who has a meal plan, a grocery run, a child to feed, a household to remember the allergies of. Who would like one app open to the recipe and not, also, three other apps open to the calendar, the list, the timer, and the dietary notes.
I read recipes in Mela on Sunday mornings. I cook dinner with Basil on Tuesday evenings. The leeks were good, by the way. The pasta worked. The four-year-old ate two helpings, which is the only review of any kitchen software that ultimately matters. If you mostly read recipes, Mela is for you. If you mostly cook them, Basil is. Neither is a criticism. Both are a kindness.
