Thanks! I didn’t incorporate the N in the 1:1 art because the D is itself already a 1:1 shape. So given that the N’s upper curve is 50% the height of the shape, we’d only be left with the lower right corner as an expressive surface. So I just opened up the upper right corner to compensate 🙂
I wish that for one brief and terrifying moment I could enter the headspace you need to be in to create a Venn diagram like that.
I can’t wait to share more type stuff—this probably won’t be the last I have to say about it 😛
I think part of the rationale here is that when you allow the bottom nav to enter the system back stack, things can get overloaded and confusing pretty quickly. In theory the app could put every single tap of a destination into the back stack, which makes a really really long trail to follow. Or it could cut off after some point, but deciding what…
I think the bottom bar makes sense for YouTube — content in the app is similar because it’s all video, but the app groups video content into sections that are very distinct not only in which videos they present but also in how the user interacts with the videos.
I think — generally speaking — if you’re descending the hierarchy it’s best to communicate that in the toolbar by changing to an up button. On Android it’s understood that swiping from the left opens the nav drawer so if it needs to be accessible from every screen it can still be accessible if not immediately visible.
Instagram displays this behavior — navigating deeper into a hierarchy from the bottom nav does create history for the back button, but the app also keeps track of where you are in that hierarchy when you switch between bottom nav destinations.
In Instagram you could theoretically come back to a destination and be several…