Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/fmo91/pluggableapplicationdelegate
Smallest AppDelegate ever by using a decoupled-services based architecture. ðŸ›
https://github.com/fmo91/pluggableapplicationdelegate
appdelegate architecture ios services swift
Last synced: 12 days ago
JSON representation
Smallest AppDelegate ever by using a decoupled-services based architecture. ðŸ›
- Host: GitHub
- URL: https://github.com/fmo91/pluggableapplicationdelegate
- Owner: fmo91
- License: mit
- Created: 2017-02-26T23:39:58.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2022-07-21T13:56:46.000Z (over 2 years ago)
- Last Synced: 2024-10-11T21:45:22.344Z (about 1 month ago)
- Topics: appdelegate, architecture, ios, services, swift
- Language: Swift
- Size: 55.7 KB
- Stars: 537
- Watchers: 11
- Forks: 79
- Open Issues: 15
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# PluggableApplicationDelegate
[](https://travis-ci.org/fmo91/PluggableApplicationDelegate)
[](http://cocoapods.org/pods/PluggableApplicationDelegate)
[](http://cocoapods.org/pods/PluggableApplicationDelegate)
[](http://cocoapods.org/pods/PluggableApplicationDelegate)
## Introduction
`AppDelegate` is a traditional example of bad code. Lots of line of code that makes so much different things are put together in methods that are called within the application life cycle. But all of those concerns are over.
Using `PluggableApplicationDelegate` you decouple AppDelegate from the services that you plug to it. Each `ApplicationService` has its own life cycle that is shared with `AppDelegate`.
## At a glance
Let see some code.
Here is how a `ApplicationService` is like:
```swift
import Foundation
import PluggableApplicationDelegate
final class LoggerApplicationService: NSObject, ApplicationService {
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey : Any]? = nil) -> Bool {
print("It has started!")
return true
}
func applicationDidEnterBackground(_ application: UIApplication) {
print("It has entered background")
}
}
```
That's all. **It is exactly the same as a AppDelegate**. Think of `ApplicationService` as sub-AppDelegates.
In `AppDelegate` you just have to inherit from PluggableApplicationDelegate to register the services.
```swift
import UIKit
import PluggableApplicationDelegate
@UIApplicationMain
class AppDelegate: PluggableApplicationDelegate {
override var services: [ApplicationService] {
return [
LoggerApplicationService()
]
}
}
```
Yes. That's all. Simple.
## How does this work?
You may want to read my [Medium post about Pluggable App Delegate](https://medium.com/ios-os-x-development/pluggableapplicationdelegate-e50b2c5d97dd#.sz50l4d0l).
Basically, you do an inversion of control. Instead of let AppDelegate instantiate your dependencies, perform actions at every step of its life cycle, you create objects that share the AppDelegate life cycle and plug them into your AppDelegate.
Those objects are observers of the AppDelegate. Your AppDelegate has the only responsibility of notify them about its life cycle events.
## Example
To run the example project, clone the repo, and run `pod install` from the Example directory first.
## Requirements
PluggableApplicationDelegate requires Swift 3.0 or above.
## Installation
PluggableApplicationDelegate is available through [CocoaPods](http://cocoapods.org). To install
it, simply add the following line to your Podfile:
```ruby
pod 'PluggableApplicationDelegate'
```
## Author
fmo91, [email protected]
## License
PluggableApplicationDelegate is available under the MIT license. See the LICENSE file for more info.