Latest 0.3.0
License MIT
Platforms ios 10.0, osx 10.12, tvos 10.0, watchos 2.0



Better Notification Observers for Swift.

  • Simpler API with sensible defaults
  • Easier to avoid ‘dangling’ observers
  • Easy activation/deactivation
  • Simple integration with view controller lifecycles


HSObserver is available through CocoaPods. To install
it, simply add the following line to your Podfile:

pod 'HSObserver'

Observers are Released

class Watcher {
    static let wave = NSNotification.Name.init("waveNotification")

    var waveObserver:HSObserver
    init() {
        waveObserver = HSObserver.init(forName: Watcher.wave,
                                           using: { (notif) in
            //Do Something

Unlike a standard observer, waveObserver is fully released when Watcher is released. (Posting a wave notification will not call the //Do Something code)

Observers can be Activated and Deactivated

    var waveObserver:HSObserver
    init() {
        waveObserver = HSObserver.init(forName: Watcher.wave,
                                           using: { (notif) in
            //Do Something



N.B. Remember that you have to activate your observer for it to work.

  • either specify activate:true in the initialiser
  • or call myObserver.activate()`
  • or chain on the initialiser HSObserver.init(....).activate()

HSHasObservers integrates well with View Controller lifecycle

A common pattern for a view controller is to activate observers in viewWillAppear, and de-activate them in viewDidDisppear

Adding the HSHasObservers protocol to any class allows you to add a group of observers, and activate or deactivate them easily.

Observers can be added manually, or by chaining .add(to:self) to an HSObserver

class ViewController: NSViewController, HSHasObservers {

    override func viewDidLoad() {

        //Add manually
        let waveObserver = HSObserver.init(forName: Watcher.wave,
                                           using: { (notif) in
                                            //Do Something
        self.add(observer: waveObserver)

        //Or by chaining
        HSObserver.init(forName: Watcher.wave,
                            using: { (notif) in
                                //Do Something
        }).add(to: self)

this works well with the view lifecycle

    override func viewWillAppear() {


    override func viewDidDisappear() {


Add Multiple Observers

        let manyThingsObserver = HSObserver.init(forNames: [Watcher.wave,Watcher.hello] ,
                                           using: { (notif) in
                                            //Do Something

Specify centre, queue, etc

    /// Create observer
    /// - parameter name:  notification name
    /// - parameter obj:   object to observe (default nil)
    /// - parameter queue: queue to run the block on (default main)
    /// - parameter center: notification center (default NotificationCenter.default)
    /// - parameter block: block to run (beware of retain cycles!)
    /// - returns: unactivated manager. Call activate() to start
    convenience init(forName name: NSNotification.Name,
                     object obj: Any? = nil,
                     queue: OperationQueue? = .main,
                     center newCenter: NotificationCenter = NotificationCenter.default,
                     activate: Bool = false,
                     using block: @escaping (Notification) -> Swift.Void)

HSObservers lets you skip the defaults. We assume

  • object = nil
  • queue = .main
  • center = NotificationCenter.default
  • activate = false

you can override each of these in the initialiser

Note that Apple’s default is to call your block on the same queue as the sender. If you want to do this, then just use centre = nil

I find that I typically want to use notifications to update the UI – so my default is to use .main


ConfusedVorlon, [email protected]


HSNotification is available under the MIT license. See the LICENSE file for more info.

Latest podspec

    "name": "HSNotification",
    "version": "0.3.0",
    "summary": "Nicer Notifications for Swift. - Better creation, activation/deactivation and cleanup",
    "description": "Better Notifications for Swift.n* Simpler API with sensible defaultsn* Easier to avoid 'dangling' notificationsn* Easy activation/deactivationn* Simple integration with view controller lifecycles",
    "homepage": "",
    "license": {
        "type": "MIT",
        "file": "LICENSE"
    "authors": {
        "ConfusedVorlon": "[email protected]"
    "source": {
        "git": "",
        "tag": "0.3.0"
    "swift_version": "4.2",
    "platforms": {
        "ios": "10.0",
        "osx": "10.12",
        "tvos": "10.0",
        "watchos": "2.0"
    "source_files": "HSNotification/Classes/**/*"

Pin It on Pinterest

Share This