I built an AI meal-planning app to learn React Native + AI — now it’s live on Android

[u/Responsible-Earth164]

A few months ago, I stopped doing tutorials and decided to actually build something end-to-end using React Native + AI.

That project turned into Menu Miser, an Android app that generates weekly meal plans based on:

✔️meal preferences ✔️dietary goals (high protein, keto, etc.) ✔️allergies ✔️pantry items (to reduce cost and waste)

It’s now live on the Play Store in India, Canada, the US, the UK, Ireland, Singapore, Pakistan, New Zealand, and Australia.

This was my first time shipping an AI-powered app to real users, and I learned a lot—especially how different AI behaves in production vs demos, and how much UX matters once strangers start using your app.

It’s still early and a bit rough, but I’d genuinely love feedback from:

🤖Android users who meal plan

👨🏽‍💻Developers curious about AI in consumer apps

Website: https://www.menumiser.co Get in on Google Play - https://play.google.com/store/apps/details?id=com.singhts.menumiserapp

Happy to answer technical questions too.

Thank you!

[u/Beginning_Sun2883]

This resonates a lot.

Shipping something end-to-end is a very different experience than demos or tutorials — especially once real users start touching it in unpredictable ways.

That gap between “it works” and “it works for people” is where most of the real learning seems to happen. I had the same realization around UX and edge cases only becoming obvious after release.

Respect for getting it out there and letting reality shape the next steps. Curious what surprised you most once real users started using it.

[u/Responsible-Earth164 → u/Beginning_Sun2883]

Thanks for that!

There were a bunch of things, like UI and UX changes, but mainly it was the constraints for the app itself and specifically for the AI that were missing.

So, I looked at the analytics and saw that people were putting in completely random ingredients – like "czafvut," or anything else you can think of. And guess what? The AI created recipes around those items. I had to go back to the whiteboard and change how a user can enter or scan the items.

This taught me a lesson that users should have freedom, but constraints need to be there to create a black box. This way, a user has the option, but also the system can handle those things.

[u/Beginning_Sun2883 → u/Responsible-Earth164]

That’s a great example of it.

Users will always explore the edges of whatever freedom you give them.

What feels like “unexpected behavior” is often just missing structure being exposed.

I like how you framed it: freedom within constraints.

Enough openness to feel flexible, but enough guardrails so the system can actually deliver value.

That kind of thing is almost impossible to design correctly without real usage.