Readeck is a reader, and in a reader the content is the whole point. The tab bar, the toolbars, all of that is chrome, and chrome should know when to step aside. iOS 26 added a one-line way to make the tab bar do exactly that.

This is a small companion to the search tab post, pulled out so each stays focused.

One modifier, and the hacks it replacedLink to heading

The tab bar now collapses as you scroll down and comes back as you scroll up:

.tabBarMinimizeBehavior(.onScrollDown)

That single line replaced a pile of manual .toolbar(.hidden, for: .tabBar) calls I had scattered across detail views to fake the same effect before. In a reader this is not decoration. The tab bar quietly leaving while you read, and returning the moment you reach for it, is the difference between an app that hosts the content and an app that gets out of its way.

The search field gets the same treatment, folding up instead of sitting there taking space:

.searchToolbarBehavior(.minimize)

Keeping the availability check out of the wayLink to heading

Both modifiers only exist on iOS 26, and I did not want if #available smeared across the view body, so each hides behind a small extension:

func tabBarMinimizeBehaviorIfAvailable() -> some View {
    if #available(iOS 26.0, *) { self.tabBarMinimizeBehavior(.onScrollDown) }
    else { self }
}

There is one for searchToolbarBehavior too. I only wrap the modifiers that genuinely differ across versions, rather than every line, so the call site still reads as plain SwiftUI.

The takeawayLink to heading

.tabBarMinimizeBehavior is not a headline feature, and that is the point. It costs one line, deletes a stack of manual workarounds, and spends all its effort making the interface disappear so the content can lead. In a reader, chrome that knows when to leave beats chrome that looks clever.