OverlayContainer is a UI library written in Swift. It makes it easier to develop overlay based interfaces, such as the one presented in the Apple Maps, Stocks or Shortcuts apps
There are currently several alternatives like:
OverlayContainer uses a different approach. The library focuses its effort on the hard part, the overlay translation. It perfectly mimics the overlay presented in the Siri Shotcuts app.
It tries to be as lightweight and non-intrusive as possible. The layout and the UI customization are done by you to avoid to corrupt your project. OverlayContainer adapts to it. See the provided examples for help or feel free to ask directly.
✅ Unlimited notches
✅ Adaptive to any custom layouts
✅ Perfect transitions between scroll & translation
✅ Rubber band effect
✅ Animations and target notch policy fully customizable
✅ Unit tested
OverlayContainer is written in Swift 4.2. Compatible with iOS 10.0+.
OverlayContainer is available through CocoaPods. To install it, simply add the following line to your Podfile:
pod 'OverlayContainer'Add the following to your Cartfile:
github "https://github.com/applidium/ADOverlayContainer"The main component of the library is the OverlayContainerViewController. It defines an area where a view controller can be dragged up and down, hidding or revealing the content underneath it.
Thus, your first step is to create a custom view controller container which combines the OverlayContainerViewController and the content you wish to overlay.
It could be as simple as a view controller stacking all its children :
class StackViewController: UIViewController {
var viewControllers: [UIViewController] = [] {
didSet {
guard isViewLoaded else { return }
loadChildren()
}
}
override func viewDidLoad() {
super.viewDidLoad()
loadChildren()
}
private func loadChildren() {
viewControllers.forEach { addChild($0, in: view) }
}
}A startup sequence might look like this :
let mapsController = MapsViewController()
let searchController = SearchViewController()
let containerController = OverlayContainerViewController()
containerController.delegate = self
containerController.viewControllers = [searchController]
let stackController = StackViewController()
stackController.viewControllers = [
mapsController,
containerController
]
window?.rootViewController = stackControllerThe last step is to define the overlay's notches. By default, the overlay container view controller does not display anything.
Implement OverlayContainerViewControllerDelegate to specify the number of notches wished :
enum OverlayNotch: Int, CaseIterable {
case minimum, medium, maximum
}
func numberOfNotches(in containerViewController: OverlayContainerViewController) -> Int {
return OverlayNotch.allCases.count
}
func overlayContainerViewController(_ containerViewController: OverlayContainerViewController,
heightForNotchAt index: Int,
availableSpace: CGFloat) -> CGFloat {
switch OverlayNotch.allCases[index] {
case .maximum:
return availableSpace * 3 / 4
case .medium:
return availableSpace / 2
case .minimum:
return availableSpace * 1 / 4
}
}The overlay style defines how the overlay view controllers will be constrained in the OverlayContainerViewController.
enum OverlayStyle {
case flexibleHeight // default
case rigid
}
let overlayContainer = OverlayContainerViewController(style: .rigid)- rigid
The overlay view controller will be constrained with a height equal to the highest notch. The overlay won't be fully visible until the user drags it up to this notch.
- flexibleHeight
The overlay view controller will not be height-constrained. It will grow and shrink as the user drags it up and down.
Note though that while the user is dragging the overlay, the overlay's view may perform some extra layout computations. This is specially true for the table views or the collection views : some cells may be dequeued or removed when its frame changes. Try .rigid if you encounter performance issues.
Be careful to always provide a minimum height higher than the intrinsic content of your overlay.
The container view controller can coordinate the scrolling of a scroll view with the overlay translation.
Use the associated delegate method :
func overlayContainerViewController(_ containerViewController: OverlayContainerViewController,
scrollViewDrivingOverlay overlayViewController: UIViewController) -> UIScrollView? {
return (overlayViewController as? DetailViewController)?.tableView
}Or directly set the dedicated property :
let containerController = OverlayContainerViewController()
containerController.drivingScrollView = myScrollViewThe container view controller detects pan gestures on its own view. Use the dedicated delegate method to check that the specified starting pan gesture location corresponds to a grabbable view in your custom overlay.
func overlayContainerViewController(_ containerViewController: OverlayContainerViewController,
shouldStartDraggingOverlay overlayViewController: UIViewController,
at point: CGPoint,
in coordinateSpace: UICoordinateSpace) -> Bool {
guard let header = (overlayViewController as? DetailViewController)?.header else {
return false
}
let convertedPoint = coordinateSpace.convert(point, to: header)
return header.bounds.contains(convertedPoint)
}You can track the overlay motions using the dedicated delegate methods.
didDragOverlay is called each time the overlay is dragged by the user to the specified height.
func overlayContainerViewController(_ containerViewController: OverlayContainerViewController,
didDragOverlay overlayViewController: UIViewController,
toHeight height: CGFloat,
availableSpace: CGFloat)didEndDraggingOverlay is called when the user has finished dragging the overlay. The container is about to move the overlay to the specified notch.
func overlayContainerViewController(_ containerViewController: OverlayContainerViewController,
didEndDraggingOverlay overlayViewController: UIViewController,
transitionCoordinator: OverlayContainerTransitionCoordinator)The transition coordinator provides information about the animation that is about to start:
/// The notch's index the container expects to reach.
var targetNotchIndex: Int { get }
/// The notch's height the container expects to reach.
var targetNotchHeight: CGFloat { get }
/// The current translation height.
var overlayTranslationHeight: CGFloat { get }
/// The notch indexes.
var notchIndexes: Range<Int> { get }
/// Returns the height of the specified notch.
func height(forNotchAt index: Int) -> CGFloatTo test the examples, open OverlayContainer.xcworkspace and run the OverlayContainer_Example target.
Choose the layout you wish to display in the AppDelegate :
- MapsLikeViewController: A custom layout which adapts its hierachy on rotations.
- ShortcutsLikeViewController: A custom layout which adapts its hierachy on trait collection changes : Moving from a
UISplitViewControlleron regular environment to a simpleStackViewControlleron compact environment. Visualize it on an iPad Pro.
OverlayContainer does not provide a built-in view controller navigation management. It focuses its effort on the overlay translation.
However in the project, there is an example of a basic solution to overlay multiple overlays on top of each other, like in the Apple Maps app. It is based on an UINavigationController and a custom implementation of its delegate:
// MARK: - UINavigationControllerDelegate
func navigationController(_ navigationController: UINavigationController,
animationControllerFor operation: UINavigationController.Operation,
from fromVC: UIViewController,
to toVC: UIViewController) -> UIViewControllerAnimatedTransitioning? {
return OverlayNavigationAnimationController(operation: operation)
}
func navigationController(_ navigationController: UINavigationController,
didShow viewController: UIViewController,
animated: Bool) {
overlayController.drivingScrollView = (viewController as? SearchViewController)?.tableView
}OverlayNavigationAnimationController tweaks the native behavior of the UINavigationController: it slides the pushed view controllers up from the bottom of the screen. Feel free to add shadows and modify the animation curve depending on your needs. The only restriction is that you can not push an UINavigationController inside another UINavigationController.
Coordinate the overlay movements to the aspect of a view using the dedicated delegate methods. See the backdrop view example.
func overlayContainerViewController(_ containerViewController: OverlayContainerViewController,
didDragOverlay overlayViewController: UIViewController,
toHeight height: CGFloat,
availableSpace: CGFloat) {
backdropView.alpha = // compute alpha based on height
}
func overlayContainerViewController(_ containerViewController: OverlayContainerViewController,
didEndDraggingOverlay overlayViewController: UIViewController,
transitionCoordinator: OverlayContainerTransitionCoordinator) {
backdropView.alpha = // compute alpha based on the transitionCoordinator
transitionCoordinator.animate(alongsideTransition: { context in
self.backdropView.alpha = // compute the final alpha value on the transitionCoordinator
}, completion: nil)
}Be careful when using safe areas. As described in the WWDC "UIKit: Apps for Every Size and Shape" video, the safe area insets will not be updated if your views exceeds the screen bounds. This is specially the case when using the OverlayStyle.flexibleHeight.
The simpliest way to handle the safe area correctly is to compute your notch heights using the safeAreaInsets provided by the container and avoid the safeAreaLayoutGuide bottom anchor in your overlay :
func overlayContainerViewController(_ containerViewController: OverlayContainerViewController,
heightForNotchAt index: Int,
availableSpace: CGFloat) -> CGFloat {
let bottomInset = containerViewController.view.safeAreaInsets.bottom
switch OverlayNotch.allCases[index] {
// ...
case .minimum:
return bottomInset + 100
}
}Adopt OverlayTranslationFunction to modify the relation between the user's finger translation and the actual overlay translation.
By default, the overlay container uses a RubberBandOverlayTranslationFunction that provides a rubber band effect.
func overlayContainerViewController(_ containerViewController: OverlayContainerViewController,
overlayTranslationFunctionForOverlay overlayViewController: UIViewController) -> OverlayTranslationFunction? {
let function = RubberBandOverlayTranslationFunction()
function.factor = 0.7
function.bouncesAtMinimumHeight = false
return function
}Adopt OverlayTranslationTargetNotchPolicy & OverlayAnimatedTransitioning protocols to define where the overlay should go once the user's touch is released and how to animate the translation.
By default, the overlay container uses a SpringOverlayTranslationAnimationController that mimics the behavior of a spring.
The associated target notch policy RushingForwardTargetNotchPolicy will always try to go forward if the user's finger reachs a certain velocity. It might also decide to skip some notches if the user goes too fast.
Tweak the provided implementations or implement our own objects to modify the overlay translation behavior.
func overlayTargetNotchPolicy(for overlayViewController: UIViewController) -> OverlayTranslationTargetNotchPolicy? {
let policy = RushingForwardTargetNotchPolicy()
policy.minimumVelocity = 0
return policy
}
func animationController(for overlayViewController: UIViewController) -> OverlayAnimatedTransitioning? {
let controller = SpringOverlayTranslationAnimationController()
controller.damping = 0.2
return controller
}You can reload all the data that is used to construct the notches using the dedicated method:
func invalidateNotchHeights()This method does not reload the notch heights immediately. It only clears the current container's state. Call moveOverlay(toNotchAt:animated:) to perform the change immediately or to move the overlay to a correct notch if the number of notches has changed.
gaetanzanella, gaetan.zanella@fabernovel.com
OverlayContainer is available under the MIT license. See the LICENSE file for more info.