Notificationz alternatives and similar libraries
Based on the "Events" category.
Alternatively, view Notificationz alternatives based on common mentions on social networks and blogs.
-
OpenCombine
Open source implementation of Apple's Combine framework for processing values over time. -
Tokamak
DISCONTINUED. SwiftUI-compatible framework for building browser apps with WebAssembly and native apps for other platforms [Moved to: https://github.com/TokamakUI/Tokamak] -
Katana
DISCONTINUED. Swift Apps in a Swoosh! A modern framework for creating iOS apps, inspired by Redux. -
VueFlux
:recycle: Unidirectional State Management Architecture for Swift - Inspired by Vuex and Flux -
LightweightObservable
📬 A lightweight implementation of an observable sequence that you can subscribe to. -
RxReduce
DISCONTINUED. Reactive implementation of the state container pattern (like Redux). It is based on the simple concepts of state immutability and unidirectionnal data flow. -
TopicEventBus
Publish–subscribe design pattern implementation framework, with an ability to publish events by topic. -
Causality
A simple thread-safe, in-memory bus for Swift that supports fully-typed Events and States.
CodeRabbit: AI Code Reviews for Developers
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Notificationz or a related project?
README
Notificationz :satellite: Helping you own NotificationCenter
Highlights
Keep Your Naming Conventions: This library gives you convenient access to
NotificationCenter
, but it's up to you to set it up the way you like!Nothing to Hide: Not trying to hide
NotificationCenter
functionality. Just an attempt to provide a more convenient APIFull and Simple Testing: Testing this library was simple, since it only forwards calls to
NotificationCenter
for the most part. Mocking that object allowed tests to reach 100% coverage.
Features
You can try them in the playground shipped with the framework!
Use your own naming convention to wrap NotificationCenter
let nsCenter = NotificationCenter.default
let 📡 = NotificationCenterAdapter(notificationCenter: nsCenter)
📡.post(.💃)
// my personal preference, define this in Globals.swift
let NC = NotificationCenterAdapter(notificationCenter: nsCenter)
// Now, you can use `NC` throughout the app
Four simple keywords to remember
let obj = Object()
NC.add(obj, selector: #selector(Object.call)) // normal add observer
NC.observe { notification in } // observe using blocks
NC.post(.tenhut) // post a notification
NC.remove(obj) // remove from nsCenter
Transparent and convenient API
let keys = ["observe", "many", "keys"].map { Notification.Name($0) }
NC.observe(keys) { _ in } // observe on the same thread
NC.observeUI(keys) { _ in } // delivered to the main thread
NC.post(.test)
NC.post(.test, userInfo: ["info":5])
NC.post(Notification(name: .test, object: nil))
RAII-based observers
class Dummy {
// declare the observer as optional
var broadcastObserver: Observer?
init() {
// assign it anywhere you like
broadcastObserver = NC.observe { [unowned self] _ in
self.doSomething()
}.execute() // this is a neat bonus feature
}
func doSomething() {
// exectued twice, since we call "execute" manually
print("it works!")
}
}
var dummy: Dummy? = Dummy()
NC.post(.test) // calls doSomething
dummy = nil // clean up is automatic
NC.post(.test) // doesn't crash!
Getting Started
Carthage
Carthage is fully supported. Simply add the following line to your Cartfile:
github "SwiftKitz/Notificationz"
Cocoapods
Cocoapods is fully supported. Simply add the following line to your Podfile:
pod 'Notificationz'
Submodule
For manual installation, you can grab the source directly or through git submodules, then simply:
- Drop the
Notificationz.xcodeproj
file as a subproject (make sureCopy resources
is not enabled) - Navigate to your root project settings. Under "Embedded Binaries", click the "+" button and select the
Notificationz.framework
Motivation
After migrating to Swift, the NotificationCenter
APIs really stood out in the code. Writing so much boiler plate all over the place just to register, handle, and cleanup notifications. Coming from C++, RAII seemed a pretty invaluable pattern to be applied here.
With this framework, one can easily declare all their observers as properties:
class Sample {
private var keyboardObserver: Observer?
private var reachabilityObserver: Observer?
}
Other programmers should be pleased with this consistency! Moreover, there is no need to worry handling notifications in some other function somewhere nor do cleanup in deinit
. It just works:
keyboardObserver = NC.observeUI(UIKeyboardWillShowNotification) { [unowned self] _ in
// you can write your handler code here, maybe call another function
}
// you can force cleanup by setting the property to nil, but don't have to
keyboardObserver = nil
Author
Maz (@Mazyod)
License
Notificationz is released under the MIT license. See LICENSE for details.
*Note that all licence references and agreements mentioned in the Notificationz README section above
are relevant to that project's source code only.