We are rebuilding the first run of our iOS app. Looking for testers who will tell us it is bad

Nitish Nattudurai — Tue, 22 Sep 2026 04:03:14 +0000

Every recipe app has the same first step. Tell us what you have. Pick from this list. Add your pantry items. Nobody finishes that. You close the app and order food.

We built Peeka to skip it. You take one photo of the inside of your fridge, or a photo of a grocery receipt. The app figures out what food you have from the image. Then it only shows recipes you can cook with those things, not recipes that need four items you do not own.

It is iOS, TestFlight, free, no account required to try it:
https://testflight.apple.com/join/AZm9hsB8

Why I am posting. Our first tester group was 10 people. Almost none of them opened the app on day 2. That number is the whole problem, and it is not a marketing problem. Something in the first two minutes is losing people before the app ever gets useful. So we are tearing that part down and building it again, and I want people looking at it who have no reason to be nice about it.

Three things I actually want answers to:

From the moment the app opens to the moment you see a recipe you would genuinely cook, how many taps and how many seconds? Where did you stall?
When it read your fridge photo, what did it get wrong? Missed items, invented items, wrong quantity. Specifics help more than a rating.
Did you cook anything? If not, what stopped you. Was it the recipe quality, the ingredient match, or just that you were not hungry when you opened it.

There are two of us building this and we are both 17. That means no growth team and no budget, so blunt feedback from people who ship things is worth more to us than another install.

If you leave a comment instead of installing, I will still read it. Tell me what you think the first screen of a food app should do.

DEV Community: Nitish Nattudurai

We are rebuilding the first run of our iOS app. Looking for testers who will tell us it is bad