Programming language: Swift
License: MIT License
Tags: UI    
Latest version: v0.4.2

NotchKit alternatives and similar libraries

Based on the "UI" category.
Alternatively, view NotchKit alternatives based on common mentions on social networks and blogs.

Do you think we are missing an alternative of NotchKit or a related project?

Add another 'UI' Library



CI Status Version CocoaPods Carthage License Contact

NotchKit is a simple way to hide the notch on the iPhone X, and create a card-like interface for your apps. Inspired by this tweet from Sebastiaan de With:

I hope / wish that the 'iPhone 8' UI looks like this: using black OLED or wallpaper behind to make apps 'cards'. Would be beautiful. pic.twitter.com/mravS87NFy— Sebastiaan de With (@sdw) August 31, 2017

Here's what it looks like:



  • Swift 4
  • iOS 8


NotchKit is available via CocoaPods and Carthage


To install NotchKit using CocoaPods, add the following line to your Podfile:

pod 'NotchKit'


To install NotchKit using Carthage, add the following line to your Cartfile:

github "HarshilShah/NotchKit"


Integrating NotchKit is extremely simple. Firstly, import NotchKit in the file where your AppDelegate is stored.

Next, replace the didFinishLaunchingWithOptions method with the following, swapping in your custom view controller's class in place of ViewController

func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {
    window = NotchKitWindow(frame: UIScreen.main.bounds)
    let rootViewController = ViewController()
    window?.rootViewController = rootViewController
    return true

If you use Storyboards, you can instantiate your Storyboard and fetch the new rootViewController in code using the following, swapping in your Storyboard's class for Main:

let storyboard = UIStoryboard(name: "Main", bundle: nil)
let rootViewController = storyboard.instantiateInitialViewController()

If you target a version of iOS earlier than iOS 11, you can still use NotchKit by loading the NotchKitWindow conditionally using the #available syntax, as follows:

window = {
    if #available(iOS 11, *) {
        return NotchKitWindow()
    } else {
        return UIWindow()

And that's all, you're done!


There are some customisation points offered in NotchKit.

You can adjust these from any view or view controller belonging to the window, by simply calling the window as a NotchKitWindow, as follows:

(view.window as? NotchKitWindow)?.propertyToCustomise = valueYouWantToSet

Target Devices

By default, NotchKit hides the status bar and home indicator on all devices. However if you choose you can limit this behaviour to just the iPhone X and have it do nothing on other devices by setting the shouldShowBarsOnlyOniPhoneX property to true.

Masked Edges

By default, NotchKit masks all edges where applicable. You can customise this behaviour using the maskedEdges property, which accepts a UIRectEdge object that specifies the edges you want to mask.

Corner Radius

You can customise the corner radius of the window, via the .cornerRadius property. This property is an enum and can either be .standard, which does all the maths for you to show an appropriate corner radius, or you can set a custom value by setting it to .custom(n), where n is a custom corner radius of your choice.


Written by Harshil Shah. You can find me on Twitter.


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

P.S.: This was made mostly as a joke while I was debating different ways to handle the iPhone X.

Apple's updated Human Interface Guidelines for the iPhone X explicitly call this out:

Don't mask or call special attention to key display features. Don't attempt to hide the device's rounded corners, sensor housing, or indicator for accessing the Home screen by placing black bars at the top and bottom of the screen. Don't use visual adornments like brackets, bezels, shapes, or instructional text to call special attention to these areas either.

I'm not sure if violating the HIG is often used as grounds for a rejection, however I wouldn't bet either way.

It only took me a couple of days using the simulator to realise that embracing the notch is the way forward. My intention with open-sourcing this was to make it easier for others to reach that conclusion as well.


*Note that all licence references and agreements mentioned in the NotchKit README section above are relevant to that project's source code only.