{"id":1822,"date":"2026-06-23T18:36:13","date_gmt":"2026-06-23T18:36:13","guid":{"rendered":"http:\/\/192.168.86.67\/?post_type=portfolio&p=1822"},"modified":"2026-06-24T19:40:50","modified_gmt":"2026-06-24T19:40:50","slug":"ting-meal-planner","status":"publish","type":"portfolio","link":"https:\/\/www.rossomando.net\/index.php\/portfolio\/ting-meal-planner\/","title":{"rendered":"Ting Meal Planner"},"content":{"rendered":"\n

Ting Meal Planner<\/h2>\n\n\n

Role:<\/strong> Product Owner, Product Designer, UX\/UI Designer, Flutter Developer
Project Type:<\/strong> Personal Product, Mobile App, MVP Beta
Platform:<\/strong> iOS and Android<\/p>\n\n\n\n

Context<\/h4>\n\n\n\n

Ting Meal Planner started with a real problem at home. My wife shared how mentally draining it was to constantly figure out what to cook, especially while balancing groceries, schedules, and meals for our family.<\/p>\n\n\n\n

My first solution was a three week spreadsheet that tracked breakfast, snacks, lunch, and dinner, including separate meal needs for our toddler. The spreadsheet helped, but it also showed me there was a better product opportunity.<\/p>\n\n\n\n

Existing meal planning apps either felt too complex or locked the workflow I wanted behind a rigid subscription model. I wanted to create a cleaner, more approachable meal planning app that helped users plan meals, shop smarter, and cook with less friction.<\/p>\n<\/div>

\"\"<\/figure><\/div>\n\n\n\n
\"\"<\/a><\/figure>
\n

My Role<\/h4>\n\n\n\n

This was a full product ownership project. I handled the product thinking, UX design, UI design, design system, Flutter development, requirements documentation, and beta preparation.<\/p>\n\n\n\n

I also used the project as a way to deepen my understanding of how design systems connect to front end code and to sharpen my native mobile product design skills.<\/p>\n<\/div><\/div>\n\n\n\n

\n
\n


From Spreadsheet to Mobile Product<\/h4>\n\n\n\n


The first version of the app was intentionally simple. It included a basic dashboard with meal cards and week controls, but I realized the app needed more structure before sending users into the main experience.<\/p>\n\n\n\n

That led me to design a three step onboarding flow:<\/p>\n\n\n\n