Hi Erik, here's how my test of Cibello went from start to finish.
Store listing
You only linked the Play Store listing. If you have a website, include the landing page too.
The listing looks good and it's clear you've thought about ASO. The screenshots work well, but "Plan easier days ahead" has a contrast issue. Make sure all text is readable.
The concept is simple: what can I cook with the food I already have? I understood it right away without reading the description.
Getting started: installation, sign-in and navigation
I found the app on Android by searching your name. Install was smooth.
You ask me to sign up before I've seen anything of the app. That's fairly standard and most users won't mind, but do a quick competitor check on how far other apps let you go first. Yours asks very early.
The bigger issue, which I also saw in one of your other apps: the screen says Login even though I've never made an account. I'd consolidate this into one flow:
- One screen that says Continue
- Continue with Google, Continue with Apple, Continue with email
- After the email step, check if the account exists. If yes, log in. If no, go to sign up.
- OTP is standard for mobile apps now. If you keep passwords, ask for it in a separate step after the email.
The create account screen has no back button. "Already have an account? Log in" isn't enough, a back option is standard. Some text is also left-aligned where it should be centered, especially on buttons.
The analytics consent screen is smart: one screen, quick to click through.
Onboarding
I always say max 30 seconds for onboarding. I like that you can select multiple goals. For "How precise do you want to be?" I predict almost everyone picks Simple mode. Track it, and if that's true, drop the second option.
I then hit Skip by accident, because it felt like a long onboarding. Even if it isn't, that's the impression it gives.
Food inventory: scanning
The scan options are clear: fridge, freezer, pantry, ingredients, receipt, plate, barcode. I tried to scan my fridge and hit the paywall right away, then saw it again. That felt too intrusive.
The pricing is very cheap, but the plan names (Household, Family, Large household) make it harder to understand, and the pop-up doesn't show the difference. The real difference is 50, 100 or 200 scans a month and how many people you can invite, at $3.25, $5.50 and $7. Just say it directly.
Free scans
It said 0 scans this month, so I couldn't test the core feature. TestMyBuild requires that I can test for free, so my scanning test ended there.
This is not about giving more value for free. People need to try the main feature once before they pay. Give 1 to 3 free scans, no more. With 10, people won't pay. With 1 to 3, they scan the fridge, want to do the freezer too, and pay.
Or let them scan and lock the result behind the paywall. Better still, generate a recipe and make them pay to see it. I know scans cost you money, but ask for payment when people are highest in dopamine: the moment they feel the app will make life better. For you that's: "I just found a meal from what's already in my house."
Recipes
What's for dinner makes sense. I can't tell if the photos are AI generated or real, and that says enough. The Thanksgiving section is a nice touch, and For you fills up even without my data. I couldn't check if suggestions match my ingredients, since I couldn't scan anything.
Planning
Under My day, Log meals takes me to the scan screen, but there's no clear option to scan a meal. I assume Plate does that. Rename it to Scan a meal or Log a meal.
Weekly planning is premium. The monetization is clearly there, I just need to try the core first.
At home
Very complete, and it shows attention to detail. The diet preferences go as far as Buddhist vegetarian.
One thing: the food budget shows Swedish kronor, while I'm paying in US dollars. If I download from the US store, show US dollars.
Saving and sharing / Reliability
I didn't get far enough to test household sharing. No crashes or freezes on Android.
Biggest improvement
Let people try one scan before the paywall, and show the paywall at the moment of success, not before it. After that, merge sign-in and sign-up into a single Continue flow.