Mobile Application Design for Apps People Actually Install
Interface design for apps downloaded from the Play Store or App Store — offline behaviour, permissions, gestures and each platform's own conventions. GullySystem designs mobile apps for field staff, dealers and customers.
What Mobile Application Design Covers
An installed app is not a website in a frame. It can use the camera, work without a signal, and send a notification that opens straight to the right screen — and it's judged against every other app on the same phone, not against a website.
- Covers Android and iOS apps for field staff, delivery and service teams, dealers and customers
- Different from responsive web design — an installed app is downloaded, works offline, and can use device features a browser cannot
- Includes onboarding, permissions, offline states, notifications and each platform's own navigation conventions
- Used for a new app and for a redesign of one already published, with existing users and reviews to protect
Where Installed-App Design Gets It Wrong
Most of the complaints in a poorly rated app come from a small, repeated set of design decisions.
A Website Squeezed Into an App Shell
The app is a browser window in disguise. It ignores the gestures and permissions a real installed app is expected to offer, and users notice within the first few taps.
The App Assumes Signal It Doesn't Have
A field engineer opens it in a basement or a remote site, the screen spins, and there's no path forward for work that genuinely needs to continue without a network.
Permissions Are Requested Before They're Explained
The app asks for camera, location and contacts on first open, before the person has any reason to grant them, and most people decline and never revisit the decision.
Android and iOS Get an Identical Screen
A single design ignores the back-button and navigation habits each platform's users already carry with them, so the app feels foreign on whichever platform it copied less.
A Notification Opens to the Wrong Place
A push notification about a specific order opens the app to its home screen instead of that order, so the person has to go searching for what they were just told about.
How We Design for Android and iOS
The design decisions that only exist once software is installed rather than opened in a browser.
Offline States Designed Explicitly
What can be viewed, entered and queued without a connection, and exactly how it syncs when the signal returns, drawn as its own set of screens rather than assumed to work itself out.
Permissions Asked for at the Right Moment
A camera permission is requested when the person is about to scan something, with a plain reason attached, instead of in a batch on first launch.
Platform-Specific Navigation
Android and iOS conventions for back navigation, gestures and system menus are followed on their own platform rather than one design forced onto both.
Designed for a Thumb, Not a Cursor
Primary actions sit where a thumb naturally lands, sized for a real finger, a glove, or a cracked screen protector.
Notifications That Deep-Link
A notification takes the person directly to the record it's about, rather than to the app's front door.
What's In Scope Beyond the Screens Themselves
A mobile app design engagement usually covers more than the working screens.
- Onboarding and the first-run permissions flow
- Offline and sync states for every screen that needs to keep working without signal
- Camera, scanner and location-driven screens
- Notification design and where each one deep-links to
- App icon, splash screen and the screenshots used on the store listing
What Shapes a Mobile Design Project
Two apps with the same screen count can need very different amounts of design work.
- Whether the app has to work fully offline or only tolerate a brief dropped connection
- How many device capabilities are used — camera, GPS, biometric login, Bluetooth
- Whether Android, iOS or both are in scope, and how closely each should follow its own platform conventions
- Whether this is a new app or a redesign of one already live, with existing users and store reviews to protect
- How much offline data needs to be stored on the device and reconciled later
Where Mobile Design Sits in Our Work
Mobile app design follows the same discovery, journey and prototyping process as any other product, applied to a platform with its own rules.
Frequently asked questions
How is this different from responsive design for a website opened on a phone?
A responsive website opens in a phone's browser with nothing to install and one version to maintain. An installed app can work offline, use the camera and GPS directly, and send push notifications — capabilities a browser page cannot offer. If your users need those, this is the right service rather than responsive web design.
Do you design for Android, iOS, or both?
Usually both, following each platform's own navigation and interaction conventions where they genuinely differ, rather than forcing one design onto the other. Where your users are overwhelmingly on one platform, we can scope the work to that one instead.
What happens to the design if a field engineer has no signal at all?
Offline states are designed as their own screens — what can still be viewed and entered without a connection, and how it's shown to be queued for sync rather than lost. We treat this as a core part of the design, not an afterthought handled by a developer during the build.
What drives the cost of mobile application design?
How many device capabilities are used, whether full offline support is needed, and whether both platforms are in scope with their own conventions followed properly. An app that only ever needs a live connection is considerably simpler to design than one that must work fully offline.
Do you design the app store listing screenshots too?
Yes, when it's part of the scope — the icon, splash screen and the promotional screenshots shown on the store listing are usually included alongside the app's own screens, since they're judged by the same audience.
Can you redesign an app that already has users and reviews on the store?
Yes, and we plan the release in stages deliberately, so existing users aren't confronted with an unrecognisable app overnight and a wave of one-star reviews about a change that would have settled down in a week.
What do you need from us to start a mobile app design project?
Access to the app if one already exists, clarity on which device capabilities the app genuinely needs, the conditions your users work in — signal strength, gloves, sunlight — and, for a redesign, any feedback or store reviews you've already collected.
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