I’ve been building a recipe app called DishCache.

The idea is blunt on purpose: I want a better way to save recipes.

Not recipe content as a bookmark. Not a tab graveyard. Not a giant food platform. I want a place where I can save a recipe I actually care about and know I’ll still be able to find it, read it, and use it later.

That part matters because recipes on the internet are often buried under a ridiculous amount of junk.

You click a recipe link because you want to know how to make the chicken, or the pasta, or the cookies. Instead you get six screens of autobiography, SEO theater, kitchen nostalgia, and a small family saga about how someone’s grandmother was 90 years old and taught them the importance of cinnamon, perseverance, and slow Sundays in October.

I do not want that part.

I want the recipe.

DishCache is built around that instinct.

What DishCache does

DishCache is a recipe app where you can save recipes in a few different ways:

  • add one manually
  • paste in the text
  • upload a photo or screenshot
  • save a link to a recipe page

The important part is the link flow.

When you save a recipe link, DishCache captures the part you actually need: the recipe itself and the main photo. It keeps the useful substance and cuts away the bloated blog narrative wrapped around it.

That means you are not just saving a bookmark and hoping the original page stays readable forever. You are saving a usable version of the thing you came for in the first place.

That is the center of the product.

A normal bookmark is a weak promise.

It says: maybe this will still be here later, maybe the site will still load, maybe the page will not get rewritten, maybe the ads will not get worse, maybe the recipe card will not move, maybe you will still want to fight through the story again.

That sucks.

If I save a recipe, I do not want to re-experience the whole content-farm obstacle course every time I need it.

I want:

  • the title
  • the main photo
  • the ingredients
  • the instructions
  • maybe a few notes
  • and the ability to find it again later without bullshit

That’s what DishCache is trying to do.

Saving the recipe, not the nonsense

This is the product idea in one sentence:

DishCache saves the recipe, not the life story around the recipe.

That does not mean source links are irrelevant. It is still useful to know where something came from. But the source should not own the experience forever.

Once I save it, I want the clean version.

I want the actual dish.

The internet has made recipes weirdly hostile to use. A lot of recipe content is optimized for search engines, ad inventory, and endless on-page time instead of clarity. You get a giant preamble, jumpy layout shifts, and some tiny “jump to recipe” link like the page knows exactly what crime it is committing.

DishCache is my way of opting out of that.

What we’ve built so far

The product already has the right bones.

Right now DishCache lets you:

  • save recipes into a personal library
  • import recipes from links
  • capture the main recipe content and main image
  • keep recipes searchable later
  • upload photos and screenshots
  • edit and clean up recipes when needed
  • view them in a cleaner format for actual use
  • control whether they stay private or get shared
  • export your collection

That is enough to make it feel real.

And importantly, it already feels like a product with a point of view.

It is not trying to do everything related to cooking. It is trying to solve one very specific irritation well.

Why it’s been fun to build

DishCache has been fun because the product judgment is unusually clean.

Every feature idea gets tested against a simple question:

Does this help someone save, recover, or actually use a recipe?

If yes, it probably belongs. If not, it is probably noise.

That makes building it feel good.

There is a lot of software where the hard part is trying to invent a reason for the product to exist. This one already has a reason. The frustration is obvious. The behavior is real. People already hoard recipes in messy, fragile ways because the tools are not good enough.

So the build gets to be practical instead of theatrical.

And honestly, there is something satisfying about building a product whose value proposition is basically:

stop making me read a stranger’s memoir when I’m just trying to make dinner.

That is not the whole product, but it is definitely part of the soul of it.

The direction from here

The direction is still pretty simple.

I want DishCache to become the best possible place to save recipes you actually care about.

That means making the core loop better and better:

  • save a recipe quickly
  • capture the useful part cleanly
  • keep the main image and core details
  • find it again later without friction
  • read it in a format that is actually pleasant
  • share it if you want
  • keep control of your own collection

There are plenty of ways the product could grow later, but I do not want to lose the center.

DishCache does not need to become a giant food lifestyle platform to be worth using.

It just needs to be the place where your saved recipes become usable again.

The point

DishCache started from a pretty ordinary irritation, but those are often the best product seeds.

The internet keeps turning practical things into content mazes. Recipes are one of the clearest examples. A thing that should be dead simple — ingredients, instructions, one good photo, done — gets inflated into this long exhausting ritual around the actual information.

I wanted the opposite.

Save the recipe. Keep the good part. Cut the garbage. Find it later. Cook.

That’s DishCache.

If you want to see it, it’s live at dishcache.com.