Hello everyone! I started making iOS apps when I was a sophomore in college. I was completely self-taught at first, mostly learning through trial and error, Apple documentation, Stack Overflow, and a lot of YouTube. Sean Allen’s channel (no plug, don’t know him personally) especially helped me understand iOS development in a way that felt practical and approachable when I was still figuring everything out. At the time, I was just building small apps to learn. Some were simple calculators, habit tools, sports stat trackers, and other projects that helped me understand UIKit, Core Data, Firebase, App Store submission, and what it actually takes to turn an idea into something people can download. A lot of those early apps were honestly pretty bad, but each one taught me something important. Mealify 2.0 came from a pretty real problem I had as a student. I was living with a typical student schedule, a limited grocery budget, and not always a great idea of what to cook. I would buy ingredients, forget what I already had, or end up making the same basic meals because I did not know what else to do with the food in my dorm or kitchen. This often caused me to just resort to local fast food joints where I spent way more than I needed to. So I started building an app around a simple question: What can I make with what I already have? That became the foundation for Mealify 2.0. I wanted it to feel less like a complicated recipe database and more like a practical kitchen assistant. You can add pantry items, scan ingredients, find recipes that match what you already own, plan meals for the week, and generate a shopping list for whatever you are missing. While there are recipes in the app, users are encouraged to add their own favorites and download new ones from our community. From a developer perspective, this app has been one of the biggest projects I have worked on. It combines a lot of the things I taught myself over the years: local data storage, AI features, image scanning, recipe management, shopping list logic, meal planning, App Store review requirements, and designing a user experience that feels simple even when there is a lot happening behind the scenes. I built Mealify 2.0 because I wanted something that would have helped me earlier as a student: an app that makes cooking feel less overwhelming, helps reduce wasted groceries, and gives you realistic meal ideas without needing to plan everything from scratch. The biggest lesson I learned is that building features is only a small part of the work. A lot of my early work had cool features but the UI was convoluted, causing users to churn early. I had to think more like a product designer and less like a developer. From the developer’s perspective, the features are logical to them as they are the ones that built it, but that is usually not the case for a customer opening the app for the first time. Most importantly, I learned that shipping imperfect versions is better than never shipping at all. Every iteration of Mealify has taught me something, and the app has improved because I kept building, testing, and listening. It is still improving, but that is also what I like about building software. Every version teaches me something new, and every bit of feedback helps make the app more useful.

Mealify 2.0

AI Pantry Scanner and Meal Planner

AI Pantry Scanner and Meal Planner