telly/TLYShyNavBar - Githubissues

v1.0, Finally! With better code design, and fully featured!

Pod Version

This component helps you mimic the navigation bar auto scrolling that you see in the Facebook, Instagram, 9gag (which uses this!) and other apps. Not only that, but with the ability to add an additional extension that scrolls along as well! It is designed for ease of use, and is battle tested in our own Telly app^[1]!

Battle Tested!!

_{[1]: AppStore version doesn't have the latest, though. Coming soon. :grin:}
_{[*]: Content are shown for demo purpose only of how this component is used in the Telly app. We hold the right to show those contents as part of our contract with Sony Pictures.}

Outline

Features: See what this component has to offer!
Quick Start: TL;DR people, you'll love this.
Design Goals: The cherished aspects of this component.
A Deeper Look: You're invested in this now and want to make the most out of it.
How it Works: The deep stuff...
FAQ: Read this before losing all hope.
Contributing: Together, making iOS better.
Author: Watashi-da!
Similar Projects: Similar projects that influenced the project in some way.

Features

Feature	Demo
Scroll a `UINavigationBar` with an extension view
Support opaque and translucent `UINavigationBar`s
Fully featured, with animations and variable resistance
Responsive, resilient and robust
Supports `UITableView`, with headers, too!
`UICollectionView` is more than welcome
In-call status bar? No problem!
Sticky extension view (Thanks @yukaliao !)
Sticky navigation bar (Thanks @TiagoVeloso!)
Fade the entire navbar (Thanks @longsview!)

You can test some of these features in the Objective-C demo:

Quick Start

Get the component
- Using CocoaPods:
  Add the following to you Podfile pod 'TLYShyNavBar'
  Import the header #import <TLYShyNavBar/TLYShyNavBarManager.h>
- Using Carthage (Thanks @bradleyayers!):
  Add the following to your Cartfile github "telly/TLYShyNavBar"
  Import the header #import <TLYShyNavBar/TLYShyNavBar.h>
- Using Submodules:
  Download the project/git submodules, and drag the TLYShyNavBar folder to your project.
  Import the header #import "TLYShyNavBarManager.h"
Write one line of code to get started!!

/* In your UIViewController viewDidLoad or after creating the scroll view. */
self.shyNavBarManager.scrollView = self.scrollView;

IMPORTANT NOTES!!

Don't use with UITableViewController. Add a UITableView as a subview of UIViewController instead.
If you are assigning a delegate to your scrollView, do that before assigning the scrollView to the TLYShyNavBarManager! To learn more, see below.

Using TLYShyNavBar in Swift

Nothing special is needed, really. Just make sure you have a Bridging Header setup, and import:

#import "TLYShyNavBarManager.h"

Then, you should be able to follow the Objective-C instructions, since the code is almost identical.

Design Goals

Ease of Use: This is the most important, and should never be compromised. Even if compatability breaks or versatility is limited, the component should remain easy to integrate.
Portable: Less dependencies, lightweight, self-contained, ... etc.
Compatability: Whenever possible, the component should simply work with whatever you throw at it.

A Deeper Look

The above example, while small, is complete! It makes the navigation bar enriched with humility, that it will start getting out of the way when the scroll view starts scrolling. But, you may want to do more than that!

ACCESS THE MANAGER OF SHYNESS

Simply access it within your UIViewController subclass as a property. The property is lazy loaded for you, so you don't have to instantiate anything:

self.shyNavBarManager

ADDING AN EXTENSION VIEW

You can assign your own extension view, and it will appear right beneath the navigation bar. It will slide beneath the navigation bar, before the navigation bar starts shrinking (contracting). Adding an extension view is as simple as:

/* Also in your UIViewController subclass */
[self.shyNavBarManager setExtensionView:self.toolbar];

To stick the extension view to the top and have it remain visible when the navigation bar has been hidden:

/* Also in your UIViewController subclass */
[self.shyNavBarManager setStickyExtensionView:YES];

CONTROLLING THE RESISTANCE

When you starting scrolling up (going down the view) or scrolling down (going up the view), you may want the navigation bar to hold off for a certain amount (tolerance) before changing states. (i.e. if the user scrolls down 10 px, don't immediately start showing the contracted navigation bar, but wait till he scrolls, say, 100 px).

You can control that using the following properties on the shyNavBarManager:

/* Control the resistance when scrolling up/down before the navbar 
 * expands/contracts again.
 */
@property (nonatomic) CGFloat expansionResistance;      // default 200
@property (nonatomic) CGFloat contractionResistance;    // default 0

CONTROLLING THE FADE BEHAVIOR

You can customize the fade behavior of the UINavigationBar through this property:

/* Choose how the navbar fades as it contracts/expands.
 * Defaults to FadeSubviews
 */
@property (nonatomic) TLYShyNavBarFade fadeBehavior;

How it Works

OK, I'll admit that I added this section purely to rant about how this project came together, and the decision making process behind it.

THE BASICS

At a component-user level, this works by adding a category to UIViewController with a TLYShyNavBarManager property. The property is lazily loaded, to cut any unnecessary overhead, and lower the barrier of entry. From the property, you can start customizing the TLYShyNavBarManager for that view controller.

Now, you may start asking, what about the navigation bar? Well, the navigation bar is accessed from the view controller your using the manager in. Let's break that down...

When you access the shyNavBarManager for the first time, it is created with the self parameter passed to it, effectively binding the shyNavBarManager to the UIViewController.
The shyNavBarManager accesses the UINavigationBar through the assigned UIViewController.

... And that is how the basic setup is done!

THE EXTENSION VIEW

When you call setExtensionView:, it simply resizes an internal container view, and adds your extension view to it. There is no magic here, just simple, single view extension.

CAPTURING SCROLL VIEW EVENTS

This one was a pain... First, the experiments that this project went through included:

Observing the contentOffset property
Adding self as a UIGestureRecognizer target
Adding a UIPanGestureRecognizer to the scroll view.
Make the user implement UIScrollViewDelegate, and send us the events.

The above didn't yield the perfect experience we were hoping for, except the last one. It did, however, make for redundant code everywhere, and forced the component user to implement the UIScrollViewDelegate. That's when the NSProxy happened.

When you assign the scrollView property to the TLYShyNavBarManager, we attach a proxy object to the UIScrollView as the delegate, and then the original delegate to that proxy. The proxy forwards the events we are interested in to the TLYShyNavBarManager, and of course, does everything else normally for the original selector, you won't even notice a thing!

THE DRAWER CONCEPT

The way the offsets are applied to the navigation bar and extension view is through an elegant doubly linked list implementation. We set the offset to the first node (navigation bar), and ...

If it is contracting:
- We pass the contraction amount to the next node, and it returns a residual amount.
If we are expanding:
- We process the offset in the first node, and pass the residual to the next node.

It is a simple concept. Say we dragged down by 100 px while the navbar was contracted. The navigation bar would take 44 px of that to expand, and then pass the residual 56 px to the next node (extension view) to calculate its offset. The same goes for contracting, but it starts from the last node, all the way up to the navigation bar.

We also add a parent relationship for a single purpose: Make the child follow its parent's offset. So, if the parent (e.g. navigation bar) is scrolling away to the top, we make sure the child accommodates the parent's offset in the calculation, so it appears as if the child is a subview of the parent.

Note: Even though there might be an illusion that the views are expanding and contracting, it's really just a translation (scrolling) of the views. There might be an advantage to actually resizing the bounds, so the extension view doesn't appear behind the navigation bar, for example, so that approach might be explored in the future.

FAQ

Opaque Navbar Shows Black Bar When Scrolled Up

You have to check the «Extend Edges» Under Opaque Bars in the View Controller configuration. Credit for this solution goes to @tiois.

I get an exception saying: "Please make sure the viewController is already attached to a navigation controller"

There are downsides in making this component as easy to use as it is. If you have read the how it works section carefully, you'd realize that trying to configure the the shyNavBarManager before it is included in the UINavigationController hierarchy, will break the component, since within the component, we cannot find the navigation bar, and an assert is triggered:

NSAssert(navbar != nil, @"Please make sure the viewController is already attached to a navigation controller.");

Of course, that can be avoided by creating your own TLYShyNavBarManager, like so:

TLYShyNavBarManager *shyManager = [TLYShyNavBarManager new];
shyManager.expansionResistance = 777.f;

/* ... sometime after the view controller is added to the hierarchy  */
viewController.shyNavBarManager = shyManager;

Contributing

PRs are welcome! It is important to test changes, though. Simply go over the demo, make sure nothing is broken. Please do check both translucent and opaque modes. Once all is good, you're good to go!

If it is a feature or bug, it would be greatly appreciated if a new view is added to the demo project demonstrating the bug/feature.

Thanks for everyone who opened an issue, shot me an email, and submitted a PR. Special thanks to those who submitted code that got checked in! This project was made possible with your help. (See contributors graph)

Author

Mazyod (@Mazyod)