Native app
A dedicated mobile product, prepared for the agreed operating systems and store submission process.
Built foriOSBuilt forAndroid
- Platform-specific capabilities
- Device and permission checks
- Store materials and review
Small screen.
Whole world.
Mobile products live in the real world. Touch the task, follow the journey and keep the work moving—even when the signal does not.
Explore the experience↘9:41▮▮▮ ▰
Your working day← →
Ready when
you are.
M12T13W14T15F16
Next task · 10:30
Site visit
Project A · Assigned to you
Open task
TodayTasksUpdates
9:41▮▮▮ ▰
← Task detail
In progressOn site.
On track.
Site visit · Project A
✓ Review project notes✓ Confirm arrival○ Add the field update
Add an update +
TodayTasksUpdates
9:41▮▮▮ ▰
Keep the context
A useful
heads-up.
Updates tied to your work.
Project A · Now
Your update is synced
The team can see the same record.
Today · 09:30
Task assigned
Site visit is ready to open.
Notification preferences ↗
TodayTasksUpdates
Swipe the screens or choose a view ↔
Scroll to follow the story. Select a step to jump to it.
A useful next step, right where your thumb expects it.
Mobile product design
Built for
the human hand.
Make frequent tasks easy to find and comfortable to use. Navigation, onboarding and forms account for fingers, small screens and the keyboard.
9:41▮▮▮ ▰
← Site visit
A quick note.
Then back to it.
Field updateSite visit complete. Ready for the next step.
Save update
01
Room to tap.
Clear actions with generous spacing.
02
The task stays in view.
The keyboard supports the next step instead of covering it.
03
Feedback in the moment.
Show what changed, right where the person is working.
What this includes
- Touch targets
- Give actions enough space and separation for a deliberate tap. Keep frequent actions easy to reach.
- Safe areas
- Keep content and controls clear of screen cutouts, system gestures and other device boundaries.
- Keyboard behavior
- Keep the active field and next action visible when the keyboard opens, without losing entered information.
- Onboarding
- Explain the essential journey at the moment it is useful, with a clear hierarchy and readable instructions.
Device capabilities
More possibility.
You stay in control.
The field note FL-028 can include a site photo. Ask at the moment of capture; if permission is declined, the same note stays available.
Capture what matters.
Request access in context, at the point of capture.
Location with a reason.
Define when it is needed and what works without it.
Relevant by choice.
Respect permissions, preferences and device settings.
“Not now” is a valid path.
The photo can wait. The note and the rest of the app remain available.
Connected functionality
Signal fades.
The work stays.
Design what happens between online and offline. Make saved, pending and synchronized states distinct, with an explicit recovery path for interrupted work.
9:41▮▮▮ ▰
← Site visitOffline
Keep going.
Add a note to task FL-028.
Draft · Not saved yet
The signal can wait.
Your work does not have to.
Your work does not have to.
Follow the field noteFL-028.
FL-028.
Nothing lost.
The same field note is saved on the device, waits for a connection, then reaches the shared record once.
On this device0No saved update
→Shared record0Awaiting update
Start with a note. Saving offline does not yet update the shared record.
Local simulation. Nothing is sent or stored after reloading this page. Real offline support is scoped for the data and actions your product needs.
What this includes
- Local state
- Decide what may be stored on the device and what remains available without a connection. Offline support is an explicit design choice.
- Pending work
- Show which changes are saved locally and still waiting to reach the server. A pending update is not yet synchronized.
- Reconnection
- Resume interrupted requests without silently duplicating submissions. Account for conflicts when records have changed elsewhere.
- Accounts & uploads
- Connect account state, uploads and backend operations to the application’s loading, retry and recovery behavior.
Release preparation
The right home
for your product.
Choose native or installable web around the capabilities and distribution you need. Prepare the device checks, assets and update plan for that route.
Installable web
An app-like web experience with installation on compatible devices. Capabilities depend on browser and operating system.
↗
Add to home screenOn supported devices
- Access through a web address
- Compatibility defined upfront
- Web-based release and updates
What this includes
- Device testing
- Review important journeys on the agreed devices and operating systems, including accessibility and permission behavior.
- Release & updates
- Prepare application assets, release notes, version information and distribution instructions. Plan for review and ongoing compatibility.
From first touch
to daily use.
Start with the people who will use it, the task that matters and the devices in their hands. Build the first useful release around those decisions.
Plan your mobile app ↗Explore Web Applications ↗What the work produces.
- A mobile screen system
- Navigation, touch interactions, forms and states that adapt to the agreed devices, including keyboard and safe-area behavior.
- Defined device behavior
- Permission choices, notification preferences, account access and the specific data and actions available offline.
- A release that is ready to hand over
- Tested journeys, application assets, version notes and distribution instructions, with a plan for updates and ongoing compatibility.