The tablet created a strange planning problem for websites. It was not really a phone, and it was not really a desktop computer. It had enough screen space to show a full website, but the interaction model was closer to mobile because people were using their fingers instead of a mouse.
Before tablets became common, it was easier to separate the conversation into desktop and mobile. That was already too simple, but it gave teams a way to think about layouts. Tablets made that split less useful. A website could no longer assume that a large screen meant a mouse, or that a touch device meant a very small viewport.
That changed how I thought about planning. The question was no longer just how wide the layout should be. It was how the interface behaved when screen size, input method and browsing context did not line up neatly.
Touch Changed The Interface
A menu that felt fine with a mouse could become awkward when used by touch. Hover states were especially unreliable because they were built around an interaction that did not translate cleanly to a tablet. Buttons also needed more breathing room because a finger is less precise than a cursor.
This meant that tablet support was not only about resizing the layout. It was about making sure the interface could be used comfortably. Navigation, forms, galleries and calls to action needed enough space to be selected without frustration.
The Middle Screen Exposed Weak Content Decisions
Tablets also exposed weak content decisions. A page that relied on sidebars, small type and dense navigation could feel busy on a tablet even if it technically fitted. The layout had enough room to display everything, but not always enough room to make everything feel comfortable.
That forced me to think more carefully about priority. If a page needed to adapt, which parts should stay prominent and which parts could move lower down? A tablet layout often made those decisions more visible because it sat between the full desktop version and the simplified mobile version.
Planning Across Ranges Instead Of Devices
The more useful approach was to stop planning for named devices and start planning across ranges. A layout should work when it has a lot of space, when it has very little space and when it sits somewhere between the two. A navigation might break at one width, while a gallery might need adjustment somewhere else.
Tablets made it harder to pretend that websites could be designed around one ideal screen. They forced more practical thinking about touch, layout and content priority, which made the expectation of a flexible website much harder to ignore.