02 / Services
Phone apps
An app for clients or a field team, connected to your server side.
When the work is done in the field, on a shift, or from a pocket, and a browser is no longer enough.
App
Phone
Screens
Screen
Request
Network
Waiting
Server
Workspace
What it consists of
What goes into the system
- 01
Screens of the first version
First, a list of what the work in a pocket cannot do without. We do not draw the other screens “for later.”
- The main screen of a shift, or of a client
- A record for an order, a request, or a visit
- The action that closes the step
- 02
A poor connection
In the field and at a stop, the network drops. The screen should wait for the network and keep what was entered.
- What can be looked at with no network
- What piles up, and goes out once there is a connection
- A clear error if a packet did not arrive
- 03
The link to the server
The app does not live apart from the records. A status set on the phone is visible in the workspace.
- One source for a request
- Sign-in for the same staff member as in the workspace
- The photo and the file land on the record
- 04
A finger, not a mouse
Buttons, lists, and errors are made for one hand and bright light, not for a wide monitor.
- The large actions sit at the bottom of the screen
- States: empty, loading, error
- A check on real phones, not only in a simulator
- 05
Stores
The build, the signing, and the listing in the App Store or Google Play are part of the release, not a separate surprise at the end.
- A build for the platforms that are needed
- The texts and pictures on a record
- How the next version is deployed
What we do
- 01A list of screens and offline scenarios
- 02An interface for a finger, not for a desktop
- 03A build for iOS, Android, or one shared codebase
- 04A link with your API
- 05Release to the stores
How we proceed
- 01The bounds of the first version
- 02Prototype
- 03Sprints
- 04A check on devices
- 05Release
Stack
- React Native
- TypeScript
- Swift
- Kotlin
A guide for the timing
The first version takes about two months. The full set of screens takes longer, feature by feature.
Outcome
An app that people use without a parallel spreadsheet “just to be safe.”
What usually comes later
Chats, complex reports, and a second scenario “for the office” are usually not in the first version. We add them once the field screen is already in use.