Replaces the iOS system status bar with a configurable version that can be used for nicer looking screen captures/recordings of your app!
The system status bar is a very iconic part of iOS, visible in the vast majority of screenshots taken from the platform.
When it comes to marketing screenshots, Apple have a very strict design policy on what the status bar looks like. Full signal strength, WiFi icon, "9:41AM" and full battery:
Unfortunately, the vast majority of apps on the App Store usually have some flavor of the following:
When integrated into an app,TOStatusBarSimulatorwill replace the real status bar with a simulated one, designed to perfectly emulate the same style of status bar in Apple's marketing screenshots and videos.
This library is great for making screenshots, and even screen recordings of your app all showing the same consistent status bar style.
It's also great if showcasing your apps on a demo iOS device in kiosk mode, allowing for an additional layer of polish and branding.
iOS 8.0 and above
CocoaPods is the preferred method of installing this library, as you can easily limit its integration to only your debug builds.
Add the following to yourPodfile:
pod 'TOStatusBarSimulator', :configurations => ['Debug']
Drag the folderTOStatusBarSimulatorinto your Xcode project. Make sureCopy Items if Neededis checked to ensure a copy is imported into your Xcode project folder properly.
Be sure to remove the library from your project when you're ready to ship to avoid any risk of getting rejected by Apple.
TOStatusBarSimulatoris controlled via issuing commands through a set of class methods. These can be called at any point in your app's execution:
[TOStatusBarSimulator show]; [TOStatusBarSimulator setCarrierString:@""]; [TOStatusBarSimulator showActualTime:YES];
Most likely not. Although there is private API access in this library, it's limited to manipulation via strings, so it's possible that Apple might not detect it.
In any case, there's no reason why users would want this functionality in a production level app, so it's definitely recommended that you only include it in your debug builds.