But settings do add complexity and that complexity needs to be organized. I actually think settings are great and I don’t have any plans to stop adding them. Speaking of settings, Grocery has accumulated a lot of them. The only other thing you can’t hide is…Settings…. The app is still all about shopping lists, so you can’t hide that just yet. This release takes the biggest step there yet, by allowing users to hide major features like Recipes, Meal Plans, and Inventory if they don’t want to use them. The app has to strike a very difficult balance between having enough features for power users and being simple and focused enough for users who really do want “Just A Simple Shopping List App”. The need for interface customization in an app like Grocery is high. If they aren’t useful to everyone then some users can hide them. I think that’s something users are really going to like, because as I keep adding more and more actions I don’t want to overthink if they’re useful enough to warrant a spot. Even better, high-visibility context menus on the shopping list all have customization options now to choose which options are available. Context menu actions are offered on virtually every button in the app that has useful actions to provide. That was a big win for a consistency and a very necessary part of shipping this update.Ĭontext menus are something I’ve been shipping since they were introduced, but this year I’m going much further with them.
#Macgourmet not syncing all code
Now I finally had one code path for every screen to be setup the same way with the same properties. So I made the decision to completely remove storyboards and replace them with a very capable and well-rounded base view controller class that performs all of the necessary setup in one place.
Storyboards make it too easy to have different property configurations on different screens, which was making it especially challenging to get my large title navigation bars and translucent toolbars all working correctly across all screens and with support for all of my color themes. The issue I was having with storyboards all boils down to consistency. But as I got into updating the app for iOS 14 and 15 I started to realize that they were holding me back.
I started using storyboards early on and I didn’t really have any issues with them. The redesign is really all about achieving consistency across every screen of the app, and closely aligning with the system style everywhere that’s possible.Īchieving consistency has proved challenging for me, partly because of the age of the app and partly because of how I had been using storyboards.
My goal for the redesign isn’t to change how the app works. Some of the system features that really make an app on iOS 15 feel modern are:Įlevated system background colors for modalsĮver since iOS 14 was released I felt like Grocery was due for a subtle re-design. While I was working on my iOS 15 release last year I started to realize several things that I’d missed from iOS 14 and 15 that I didn’t have time to implement for iOS 15. I essentially started working on Grocery 3.0 after iOS 15 shipped. That list tends to grow a lot after major iOS releases, and I don’t always get to everything I want to change when a major new iOS version is ready to ship. I think about Grocery all the time and I’m constantly adding new things to my todo list of features and changes.