Such bloated app delegates fall under the definitions of the Blob anti-pattern and spaghetti code. I am sure the list is not limited to the aforementioned. Conform to various delegate protocols, especially from third parties.Manage UI stack configuration: pick initial view controller, perform root view controller transitions.Manage notifications: request permissions, store token, handle custom actions, propagate notifications to the rest of the app.Manage UserDefaults: setups first launch flags, save and load data.Configure app state for unit or UI tests.Initialize Core Data stack and manage migrations.Initialize numerous third-party libraries.
REGISTER APPDELETE CODE
I am sure each of us either wrote such code or had a luck to support a project with similar mess. It’s very common for app delegate to have dozens of responsibilities which is makes it difficult to change, expand and test.Įven Apple encourages you to put at least 3 responsibilities in your AppDelegate.īy investigating a couple of dozens of most popular open-source iOS apps I composed a list of responsibilities that are often put into app delegates. It ensures the app interacts properly with the system and with other apps. The app delegate is the root object of your app.
In this article let’s have a look at different methods of how app delegates can be made concise, reusable and testable. Undoubtedly, keeping this class clean and concise is crucial for the healthy iOS project. The cost of breaking anything inside the app delegate is extremely high due to the influence it has over your app. The common tendency is that it keeps growing as the development goes, gradually sprouting with new features and responsibilities, being called here and there and eventually turning into spaghetti code. App delegate connects your app and the system and is usually considered to be the core of every iOS project.
0 kommentar(er)
