I’m sure @ldebeasi will provide better support here than I can, but dear future readers of this thread:
Whenever I have a UI that involves tabs, and I’m finding that things aren’t running completely smoothly, in exactly the way I wish it would, the very first thing I do is to take a very hard look at whether tabs are really the best fit for the situation. I can’t remember a time that it turned out to be.
Tabs are a tricky interface. They seem attractive to developers, especially on mobile devices where screen real estate is a precious commodity, because they effectively give you a “Z axis” to layer a bunch of stuff into the same space. However, “out of sight, out of mind” is a real thing. Action-at-a-distance that affects the contents of tab B from within tab C (or from a launch page) is disorienting for users.
The navigation scenario @ldebeasi is describing in the App Store app may seem very specific and limited. It is. It’s also pretty much the only type of navigation scenario that is well-adapted to a tabbed presentation. Ionic’s tab component is opinionated in this respect, and I think that’s a very good thing, as it guides us developers away from potential shipwrecks.