Responsive Interface Design for Every Screen Your Staff Use
One interface designed to work on a delivery executive's phone, a shop-floor tablet and an accountant's desktop, without becoming three separate products. GullySystem designs and prototypes responsive layouts for web applications, portals and internal software.
What Responsive Design Has to Solve
Responsive design is not shrinking a desktop screen until it fits. The person on a phone is standing at a gate with one hand free; the person at a desk has a keyboard and two hours. Responsive design decides what each of them sees, in what order, and what is left out entirely.
- For new software, and for existing web applications that fall apart the moment somebody opens them on a phone
- Covers phone, tablet, laptop and large desktop, plus print layouts where the work ends up on paper
- Decides what to hide, collapse or reorder at each size, not merely how things stretch
- Prototype links open on your own devices, so layouts are judged on the hardware your people actually carry
Where Interfaces Break on Small Screens
A layout built at desk width rarely fails politely on a phone. These are the failures that reach us most often.
The Data Table That Will Not Fit
A ten-column table becomes a sideways scroll nobody uses. Field staff stop trying and telephone the office for the number instead, which is slower than the paper it replaced.
Buttons Too Close Together for a Thumb
Actions sized for a mouse pointer and placed a few pixels apart, tapped by somebody wearing gloves on a loading dock. The wrong one gets pressed and undoing it takes ten minutes.
A Twenty-Field Form on a Handset
A form laid out for a desk becomes one long vertical scroll, with the save button somewhere far below and no indication of how much is left to fill.
The Menu Hides What Is Used Most
Desktop navigation collapses into a single icon, and the three actions performed constantly end up buried two taps deeper than the ones needed once a month.
Designed on Office Wi-Fi
Heavy images and screens that show nothing until everything has loaded feel fine at head office and are unusable on a patchy mobile network at a customer's premises.
The Keyboard Covers the Field Being Typed In
On a phone the on-screen keyboard hides both the input and the save button, so the user types blind and then scrolls around hunting for the way out.
How We Design Across Devices
Each screen is settled at the size it is hardest at, then given room at the sizes where room exists.
Decide the Job of Each Device
Before any layout, we agree what each device is for. A phone may only need to look up, scan and update a status, while editing and reporting stay on the desktop. That single decision removes most of the difficulty.
Priority Before Breakpoints
For each screen we rank what must stay visible, what can collapse and what can move behind a tap. Breakpoints then follow your content instead of chasing a list of standard device widths.
Tables Redesigned, Not Squeezed
On a small screen a row becomes a card carrying the three fields that matter, with the rest one tap away, so the information survives even when the table cannot.
Thumb Reach and Target Size
Primary actions sit where a thumb naturally lands and are given targets big enough for real fingers, gloves and a cracked screen protector.
Input Suited to the Device
Numeric keypads for quantity fields, camera or scanner input where a code is being read, touch-friendly date selection, and long forms broken into steps that each fit one screen.
Checked on the Devices in Use
We review layouts on the phone models and browser versions your staff and customers genuinely have, not only in a resized window on a designer's monitor.
Beyond the Browser Window
Some of the hardest responsive decisions have nothing to do with phones.
Tablets Fixed to a Counter or Trolley
A tablet mounted in landscape at a billing counter and one held in portrait on a shop floor are different screens with different reach. Both get a layout rather than one being left to chance.
What Leaves the Screen on Paper
Invoices, challans, gate passes and reports need designed print and PDF layouts, because a screen printed without one wastes a page and hides the total.
Wide Monitors Actually Used
On a large desktop, a layout that stays a narrow column in the middle wastes the screen your accounts team was given. Wide layouts get designed instead of inherited.
Slow and Dropped Connections
Screens say what is happening while data is on its way and what to do when it does not arrive, so a stalled page reads as a network problem rather than a broken product.
What Decides the Effort
Responsive work is counted per screen and per size, so the shape of the product matters more than its page count.
- How many device sizes are genuinely in scope, rather than listed for completeness
- How complex the densest screen is — an entry grid is far harder to fit than a list and a detail page
- Whether this is a new build or a retrofit of a web application never planned for small screens
- The range of hardware your users have, since older low-specification handsets constrain every screen
- Whether print and PDF layouts are included
- Whether review on a set of real devices, in the conditions the software is used in, is part of the scope
Related Design and Prototyping Work
Responsive layout work is usually one part of designing the product itself. The wider service covers the rest of it.
Frequently asked questions
Is a responsive web application the same as having a mobile app?
No, and the difference matters before you budget. A responsive web application opens in a phone browser with nothing to install and one thing to maintain. A mobile app is installed from a store and can use the camera, notifications and offline storage more fully. For most internal software and portals, responsive is enough; for field work that must run without a network, it usually is not.
Can our existing web application be made to work on phones without rebuilding it?
Often, yes, though not always cheaply. We review the current screens, find which layouts can be reflowed and which have to be redesigned for a small screen, and give you the work in stages starting with the journeys your users most need on a phone. Where a screen genuinely cannot survive the transition, we say so rather than delivering a version nobody can use.
Which devices and browsers should we design for?
Whatever your users are on, which is usually not what the office runs. If you have website or application analytics, we start there. If you do not, we ask what your field staff, counter staff and customers carry, and design for the weakest of those rather than the newest.
What drives the cost of responsive design work?
The number of screens and the number of sizes each one needs, multiplied. A dense screen redesigned for phone, tablet and desktop is three layout decisions, not one. Retrofitting an existing product also costs more than designing for it from the beginning, because the existing structure limits the options.
How long does it take to make an existing product responsive?
It depends on how many screens you want covered and in what order. We normally do the most-used journeys first so something is in your users' hands early, rather than delivering the whole product at once. Your build team's release schedule usually decides the pace after the designs are approved.
Do we receive the designs for every screen size?
Yes. Each screen is delivered at the agreed sizes with notes on what changes between them — what collapses, what reorders, what is hidden — and you own those files outright. Your developers build from them without needing to ask us what happens in between.
What do you need to know about our users' devices?
A short list is enough to begin: which roles work on phones, which on tablets, which at desks, roughly what handsets they have, whether they work indoors or outdoors, and whether the network is dependable where they are. If you have analytics, share it; if not, ask your supervisors and tell us what they say.
Tell us what you need.
Send a short brief and one of our engineers will come back to you — usually the same day.
- No obligation
- We reply the same working day
- Your details stay private