The current Twitter bottom nav is a little wonky though I use it on mobile web, not sure if it's different on the app (ex: opacity changes on scroll) I would see if there's specific accessibility best practices to take into account in this kind of situation

I’m curious because I’d say most guidelines are loose enough that they can be interpreted in multiple ways; otherwise all apps would look and interact the same. Which does not happen. Also, many apps thoughtfully break guidelines and are still very successful.

This might be a hot take but I don't think it's necessarily a bad thing if more apps interact the same.. I'd say there's more of a spectrum in terms of pure visuals, but accessibility should be accounted for either way

I 98% agree 😄. We shouldn’t make things different just for the sake of being different, however innovation requires deconstructing the status quo.

I don't think making something accessible and being innovative are mutually exclusive but I'll stop replying now lol

hmm, don't think there's a "right" answer and i think it really depends on the context. i think the main question when a user navigates to a new page/section is, "what should they be concerned with?" then that leads to "what elements should be visible or not visible?"

Totally agree. Rarely is there a right answer and it’s dangerous to blindly follow iOS or android ‘guidelines’ to a T. I think the question of does X aid in helping the user complete task Y is the right one while balancing for consistency. Thanks!

Here is what Apple has to say developer.apple.com/design/human-i…

I just wrote this out and then saw your reply. This is the right answer. That doesn't mean anyone _has_ to follow it, but this is the expected behavior.

Correct. It’s considered best practice. I personally sometimes like to hide TabBar but it’s very use-case related. 🙃