Confusing navigation tree

Hi,

I’m confusing the way you set up navigation in the twitter sample. For example: scene home and tweet repeated from root stack, then appear one more time in the stack under the Tab.

Could you explain it?

Root Stack

Stack under Tabs

[anhtuank7c]

Thank you so much @grahammendick @burakgormek

[grahammendick]

I encourage you to dig a bit into the different design systems you’d use if you were building a native app without React Native. On IOS you use UIKit and on Android you use Material Components. These provide a completely different UX. The Navigation router renders to these 2 different design systems using a single component. So you end up with apps that look and feel like real native apps.

Your image of a customized tab bar is actually an image of a Floating Action Button anchored to a bottom App Bar. The Navigation router supports this on Android (see Cradling a Floating Action Button). But you can’t anchor a Floating Action Button to the TabBar because it isn’t part of Android’s Material Components.

If you want a customized TabBar that looks the same on Android and iOS then you’re going to have to build it yourself or use a third-party library.