@nicoreese Yep! This is what managingNavigationController and the associated delegate API was designed to do.

What you can do is when you're not in compact (i.e. sidebar is available), return [] to displayedViewControllers for the Library tab, and return proposedViewControllers in compact. I'd also suggest marking the Library tab as 'sidebarOnly' for its placement. That should get you the behavior you're looking for.

@Joekw @stroughtonsmith Magic is the goal! We wanted to build an easier way to build tab-based apps that adapt well across various platforms and scene sizes.

With managingNavigationController, it removes a lot of the custom hierarchy management for adaptivity from apps so you can focus on building everything else in your app. 🙂

@Joekw @stroughtonsmith I guess the question is if the group hierarchically fits with another root tab (I’d assume it does because how will users access that content in compact).

If so, you could structure it as:

TabGroup (appearance=inline)
- Root Tab
- Section (appearance=rootSection)

Structuring them relatively to the parent will also help take care of adapting between compact and regular.

Beyond that though, can you file a feedback for the issue you see?

@stroughtonsmith @Joekw The API and feature is designed such that the Sidebar is the “everything” destination and the iPad tab bar shows the important + user favourite destinations (thru user customization).

The intent is that you should have a single model across your app, and thru properties on the tab models, we’ll display the same model differently between your phone and pad UI. I can give recommendations if you have an example hierarchy.