suggestion: improve footer tabs

[cpg]

Please enhance the footer tabs. There is this limitation listed in the bottom tab bar:

⚠️ DISCLAIMER: ONLY Use tabs at the root level (The first view that shows up on launch). Any other usage may introduce unexpected behavior.

I found this to be true. However, forcing all apps to display a footer with tabs from the launch view if they ever want to use tabs is rather restrictive and generally very awkward for app design and UX.

One work-around I found to work is to transition from a view without footer to a view with a footer via a "replace" transition, so that the user cannot go "back" into the non-tabbed view. I found this to work reliably, though I am not sure if it's something the project can condone. If this is "safe" to do, it may be a somewhat acceptable work-around in general and would be good to have documented for others, making the framework more versatile.

I typically design my apps to have a footer when the user is logged in. Replacing the "top" view into and out of tabs works for me.

[IvRRimum]

+1 for using tabs in other than root page. Really weird behaviour.

[steve21124]

@IvRRimum What weird behavior do you found? So far when presenting with it, it did not give problem for me. (I think the problem is when tapping the second tabbar it is not displaying the content and the code setupTabBar need to be change to handle it) By the way, did any one know if Android support modally displaying nav with footer tabbar in the modal?