We wanted our recipes to stand the test of time with an open document format that supports interleaved ingredients and steps. Our entire concept for recipes hinged around using markdown to improve flexibility for displaying recipe content. Using Markdown as a storage system for recipes Once we had the new project we started attacking all of the problems involved with building recipes:ġ. Using a new Xcode project gave us space to work through design and technical hurdles without worrying about breaking Grocery. You need a place to safely store all of the recipes a user adds, with all of their section headers, ingredients, steps, notes, timers, and photos. You need a list to view all your recipes, a recipe viewer for cooking and selecting ingredients, and an editor to create new recipes. Building recipes seemed incredibly complicated. I initially resisted adding recipes to Grocery because I was in love with the idea that Grocery is just a simple shopping list. What’s the deal with a new Xcode project? We love it too! But for multiple technical and user experience reasons I can safely say that 2.0 is a huge improvement, not only to the experience of using Grocery but also to its technical future for many releases to come. That probably sounds weird if you've already been using 1.0 and love it. One way to look at it: Version 1.0 was basically our prototype.
PAPRIKA RECIPE MANAGER APPLE WATCH CODE
We eventually did bring that recipe feature back to Grocery and we’re excited to be shipping it in the app today! But along the way, we also re-wrote virtually all of Grocery’s UI in a way that greatly improves the consistency of elements throughout the app, as well as how code is structured for re-use across screens. Our goal was to prove that our design worked and bring what we learned back to Grocery and quickly ship our recipe feature. Instead, we created an entirely new Xcode project to iterate quickly on our recipe concept. The obvious next step after design would have been to hit File -> New View Controller in Xcode and start adding a recipe screen to Grocery. We set out to do just that and started design in January of 2018. If we added recipes to Grocery it would need be a great recipe feature that we could trust with those recipes.
To many people, they’re as special as family photos: passed down generation to generation. I think it's important that this realization happened with family recipes because family recipes are very special. We both wanted to have our recipes in Grocery to make adding those sets of ingredients easier. After picking a recipe to make you typically add the ingredients to your grocery list and go shopping. Ryan and I were back home with our families looking up recipes and planning holiday meals.
0 kommentar(er)
