Question about slight difference in behavior about tlyshynavbar HOT 4 OPEN

@DimaVartanian Thanks for your kind words. I am really impressed by the Spark inspector approach using a jailbroken device, never thought of that!

So, about the idea, I am sold. Anything to improve this component, will improve our app experience anyways :)

Here is an initial rough experiment I did:

I think I used an easier way than playing with backgrounds and views. I set the navigation bar as hidden on viewWillDisappear: if it is contracted, and unhide it in the next view viewWillAppear:. This makes UIKit take care of the animation for us. I still have some concerns, though, so gonna look deeper into it soon.

from tlyshynavbar.

This looks great and more natural than before for sure! So the only discrepancy in behavior now is that when you pop back to the original view, the navigation bar is always reset to the open state rather than going back to the state it was in when you pushed. This is really just a difference in behavior and not a usability issue like the other one was so it might not be very important or even needed. In any case, I'll take a look soon when I get a chance as well :).

from tlyshynavbar.

Thanks, I meant to address the second point, but got dragged in by the first issue. I think it's a very simple matter to reserve the previous state. Honestly, I would keep it the way it is in our app, but an option can be added to reserve the last state for users to choose between the two.

My reason behind making it expand is that I feel the user probably went back using the back button, hence he is focused on the navigation bar. Taking that bar away, even though that's the initial state, might not be ideal for that case. I can see it working better in other cases, though.

from tlyshynavbar.

I thought it was simple, but issues kept popping up.. Need to take a closer look at it.

from tlyshynavbar.