Most of what I do on an iPad happens in a browser.
Since iPadOS 26, the iPad has become much better at being a computer. Apps open in real windows: I can drag one by its corner, set it beside Notes, pull down a menu bar, and keep a call running at the edge of the same screen. With a Magic Keyboard attached, it finally behaves the way its hardware always suggested it could.
That lasts until I open my twentieth tab.
By then the strip along the top of the window has divided the same width among so many tabs that each one is an icon and three letters, and two of them have the same icon. I close a tab I meant to select, because the tab and its close button are now about the same size. When I drag the window narrower to make room for Notes, the strip disappears entirely: the tabs move behind a button, into a grid of thumbnails I have to open, scan, and close again.
None of this is a bug. The tab strip is doing what it was designed to do, on the machine it was designed for. That machine had a wide window that stayed wide, and a mouse. An iPad has neither for most of the day, which means a browser for it can’t simply inherit the desktop layout.
Why a list instead of a strip
A tab strip is a row of fixed width. Every tab I open takes its share from the others, so the more there are, the less each one can show. A sidebar is a list: every tab gets a full row at the same height, and when the rows run out, the list scrolls.
With six tabs the two are interchangeable. With thirty, the strip is a line of icons and the list is still thirty titles I can read. A page title is a line of text, and lines of text stack far better than they squeeze together side by side.




The list has a second advantage, one that took me longer to notice. A strip has a single level; everything in it is simply open. But my tabs aren’t all the same kind of thing. Some I open every day. Some belong to the trip I’m planning and to nothing else. Some I opened ten minutes ago and will never need again. A row in a list can be pinned to the top, folded into a group, or dragged somewhere else. A strip has no place for those differences, so they end up in menus.
On the Mac, browsers built around a sidebar have existed for years and have a loyal following. On iPad, where I think the case for one is stronger, the strip is still the default.
Designing for a window that changes size
The case is stronger on iPad because of how its windows behave. On a Mac I size a browser window once and mostly leave it alone. On iPad the same window is full screen in the morning, sharing the display with Notes by lunch, and squeezed into a column beside a call in the afternoon.
A strip has one comfortable width, so I designed Tweed’s layout around three. Full screen, the sidebar and the page sit side by side with room for both. As a window among other apps, the sidebar stays and the page narrows. Pulled into a column, the sidebar becomes the tab list you’d find on iPhone, and the address bar drops to the bottom, where a thumb can reach it.






I wanted the column to be a complete browser rather than a reduced one. Pins are still one tap away, and groups and Spaces are all there. It’s the same list, laid out for the width it has.
A sidebar isn’t free. It takes a slice of the screen’s width, and on an 11-inch iPad you notice. But in landscape most web pages leave empty margins on both sides, so the sidebar is mostly using space the page wasn’t. A strip, by contrast, costs height, which reading always needs. When a page does need the full width, the sidebar hides and the page fills the window.
Touch, trackpad, and keyboard
An iPad gets used three ways, often within the same minute: a finger on the glass, a hand on the trackpad, or the keyboard. The strip was drawn for a pointer. Its tabs are short, their close buttons are small, and moving one means dragging it sideways through its neighbors.
A row in a list is comfortable to touch and easy to pick up, so most of the organizing in Tweed is done by dragging. Drag a tab to the top of the sidebar and it’s pinned. Drop it on another tab and the two become a group. Drop it on either half of the page and the two pages open side by side; in the sidebar the pair becomes a single row, so it stays together when I move it. Everything else is a touch and hold away.
With a keyboard attached, the same list works the way a desktop browser does. ⌘L goes to the address bar, ⌘1 through ⌘9 jump straight to a tab, ⌃⇥ moves between tabs, ⌘⇧T brings back the one I just closed, and Option-click opens a tab beside the current page. Every command is in the iPad menu bar too, with its shortcut next to it.
Spaces
The feature I rely on most is Spaces. A Space is a sidebar of its own, with its own pins, groups, and tabs, a name, and a color that tints the sidebar. Work stays in one, the trip I’m planning in another, the long reads I’m saving for the weekend in a third. Changing Spaces is a swipe across the sidebar, with two fingers on a trackpad or one on the glass.
Two decisions here were deliberate. A new Space starts empty instead of copying the tabs I already have, because the point of a new Space is that it isn’t full yet. And deleting a Space doesn’t destroy it: it moves to an archive with its tabs, pins, and groups intact, and can be restored from there.
On iPad, each window keeps its own Space as well, so work can sit on one side of the screen and the trip on the other.
The same tabs on iPhone
An iPad is rarely anyone’s only device, so everything in the sidebar syncs. Tabs, pins, groups, bookmarks, history, and Spaces travel through iCloud, using the Apple Account already on the device. There’s no Tweed account to create, and the data stays in your own iCloud.
On iPhone the sidebar becomes a tab list. Swipe up from the address bar and the page shrinks into it; swipe across to change Spaces. The page I left open on iPad in the morning is in that list by the time I pick up my phone.


One detail matters more than it sounds: sync carries the contents of each Space, not which Space a device is showing. Switching Spaces on iPad doesn’t switch them on iPhone, so the page under my thumb never changes because of something I did on another screen.
Everything else a browser needs
A sidebar is only worth having if the browser under it is complete. Tweed has the things I’d miss within a day: Reader, find on page, downloads that land in Files, Picture in Picture, page translation that runs on the device, and a Collector for images on a page. Bookmarks, reading lists, and history can be imported from Safari, Chrome, Arc, and other browsers.
Address-bar suggestions come from your own tabs and history. When you submit a search, Tweed opens the search engine you chose. The app doesn’t send your browsing history to us. You can choose to share crash reports to help us fix problems.
After windows
For a long time the argument about the iPad was whether it counted as a real computer, and most of that argument was about the system: files, windows, external displays. With iPadOS 26, a good part of it is settled. The windows are here.
What’s left is the software inside them. The system can resize a window, but it can’t decide how an app should arrange itself at each size; that is still every app’s own problem, and the tab strip is an example of one that hasn’t been solved. Tweed doesn’t change the page itself. It moves the tabs from the top of the window to the side and puts pins, groups, Spaces, and Split View into that sidebar, so the tabs stay where I put them and stay readable whether the window is full screen, shared with another app, or a narrow column, and on iPhone as well.
If you keep twenty or thirty tabs open on an iPad and often use the browser beside another app, give it a few days. The strip is hard to go back to.

