The Cockpit in Your Pocket

Navigation within thumb reach, long tables as readable cards, and date fields that behave the way you expect on a phone.

Organisation & context Knowledge & product

The cockpit was never unusable on small screens. Layouts have always adapted to the available width, pages stayed readable, forms worked. What was missing was something else: an interaction model that suits a phone rather than merely fitting on one.

Because the way people work has changed over the years. A working day rarely waits for a quiet half hour at a desk. You clock in on the way to a customer, create a task between two meetings, check who is on leave while standing on a platform. Those moments were the most frequently requested ones.

Mobile is more than a screen width

Responsive design solves a presentation problem: content has to fit a narrower column. Mobile interaction solves a different one: input comes from a thumb instead of mouse and keyboard, the eye takes in less at once, and the same hand is holding the device.

This release therefore does not address width. It addresses interaction and presentation. The three places where that shows up most clearly in daily use are navigation, tables, and the input fields for dates and times.

Navigation within thumb reach

Navigation now opens as a panel you can reach with your thumb. Anyone working one-handed no longer has to shift their grip to move to another area. A collapsed menu also leaves more room for the content itself.

On a small screen, every permanently occupied area is a decision against something else. Navigation should be available when it is needed and out of the way afterwards.

Long tables become cards

On a large screen a table is the clearest form: columns side by side, values directly comparable. On a phone the same table turns into sideways scrolling, and the mapping regularly gets lost: which value belonged to which row?

Long tables therefore appear as cards on small screens. Each entry keeps its fields together and stays readable in one piece. The data is identical; only the form follows the device. Comparing still works best on a large screen, and looking up a single entry while away no longer requires hunting for it.

Dates and times without detours

Date and time fields are a topic of their own on a phone. They look different on every system, tend to break out of their frame, and end up visibly misaligned next to neighbouring fields. These are exactly the fields you need most on mobile: clocking in, creating a task, requesting leave.

They now behave the way you expect on a phone. They stay inside their field, line up with their neighbours, and open the picker the device is known for. This is not a new feature but one less point of friction in a place that gets touched several times a day.

Same cockpit, no reduced version

There is no separate app and no stripped-down mobile view with fewer capabilities. Same cockpit, same data, same workflows. A task created on the way to a customer is waiting at the desk exactly where it belongs, and a quick lookup on a platform happens in the same application the rest of the team uses.

Together with open pages that update without reloading, this makes switching devices something you no longer have to think about. You simply keep working wherever you happen to be.

Related articles

Frequently asked questions

Mobile is more than a screen width – what does this mean in everyday work?
Responsive design solves a presentation problem: content has to fit a narrower column. Mobile interaction solves a different one: input comes from a thumb instead of mouse and keyboard, the eye takes in less at once, and the same hand is holding the device.
Navigation within thumb reach – what does this mean in everyday work?
Navigation now opens as a panel you can reach with your thumb. Anyone working one-handed no longer has to shift their grip to move to another area. A collapsed menu also leaves more room for the content itself.
Long tables become cards – what does this mean in everyday work?
On a phone, a wide table turns into sideways scrolling, and the mapping gets lost along the way: which value belonged to which row? Long tables therefore appear as cards on small screens. Each entry keeps its fields together and stays readable in one piece.
Dates and times without detours – what does this mean in everyday work?
Date and time fields are a topic of their own on a phone: they look different on every system and tend to break out of their frame. These are exactly the fields you need most on mobile, when clocking in, creating a task, or requesting leave. They now stay inside their field, line up with their neighbours, and open the picker the device is known for.
Same cockpit, no reduced version – what does this mean in everyday work?
There is no separate app and no stripped-down mobile view. Same cockpit, same data, same workflows. A task created on the way to a customer is waiting at the desk exactly where it belongs.
What practical insight does the article offer?
Being usable on mobile is not only about a layout getting narrower. It means interaction and presentation fit the device: navigation for the thumb, cards instead of sideways scrolling, and input fields that behave as expected.