Mobile development
An application, when the phone is the workplace
Mobile development is justified when the scenario lives in the hand: a site visit, a shift, a courier, a client's repeated actions, a weak network. I build Android, iOS, and cross-platform applications, including accounts on top of a system that already exists.
What it takes on
Take the work into the field
The employee records a status on site, not from memory in a spreadsheet that evening.
Give the client an app
A repeated scenario — an order, a booking, a status — opens from the home screen.
Survive a poor network
A critical action is not lost if the connection drops on site.
Link the phone to the system
The app does not start a second set of records. It shows and changes the same entities as the office.
Who it is for
Service and field teams
The job, a photo, a status, and a report should fit in one hand.
Products people use often on a phone
The client comes back several times a week, and a browser tab gets in the way.
Companies that already have an account
The server exists. What is missing is a usable phone for one role.
If a person opens the service once a month on a normal network, a separate app in the store is often too early. A strong account should come first.
What can be built
Android
An app for the scenario, the devices, and the constraints of Android.
iOS
The same meaning of the scenario, with the rules of the platform.
Cross-platform
A shared base, when both stores are needed and the logic is one.
Client account
A mobile entrance into a service that already exists.
A corporate app
A closed system for staff, not necessarily a public store.
How it looks in practice
- 01
An engineer marks the work on site
You need the job, a checklist, a photo, and a way to send, even if the basement only catches a network now and then. An evening spreadsheet is already unreliable here.
- 02
A client follows an order
A push about a status change is more useful than an email they will open tomorrow. The account in the app shows only what the person may change themselves.
- 03
The company already has a web system
The records are not rewritten. A mobile client is added to the same data and the same permissions.
How development goes
- 01
A check that the phone is actually required
A list of actions that live badly in the browser.
- 02
Platforms
One system, two, or a cross-platform client.
- 03
Scenarios and network states
What must be saved offline, and what can wait.
- 04
An interface in the hand
Large actions, not a desktop that has been shrunk.
- 05
Build and server
The client, sign-in, and exchange with the existing API.
- 06
Stores
Builds, signing, and what to prepare for review.
Technologies
- TypeScript
- React Native
- Native modules when needed
- REST API
- PostgreSQL
You receive an application in the chosen format, the source code, a build, and a clear list of what is needed to publish in the store.
Demonstrations on this topic
How to commission it
A project with a clear scope
We agree what goes into the next batch, and we hand over that scope, not an endless list of ideas.
MVP
We build one scenario you can already work in, or use to test demand. The rest is not thrown away. It goes into the next batch.
Support
After launch, there is someone to give a bug, a question, or a new branch of the process.
Questions
Where do you start: iOS, Android, or both at once?
With the platform where your users are. The second is added when the scenario is confirmed. A cross-platform base fits when both storefronts are needed at once, and there is no heavy native specificity.
Do you publish the app to a store?
I prepare the build and the store's list of requirements. Developer accounts are opened in the company's name, so the app belongs to you, not to me.
Can a website be enough?
Often, yes. If there is no offline work, no pushes, and no daily gesture of opening from an icon, a responsive account is cheaper and faster. An app is added when those limits are already in the way.
Will the app work without the internet?
Only for the actions where that is agreed. Full offline changes the architecture a great deal. Usually you keep a draft and a queue of sends, not the company's whole database.
How is the app linked to the CRM?
The phone should not create a parallel set of requests. It uses the same system: it creates, it changes a status, and it shows only the roles that are allowed.
Related reading
Neighbouring directions
- Services
A working scenario in the browser: an account, data, roles, and a next step.
- Interfaces
Screens and rules you can develop from, without guessing.
- Support
A clear queue of changes in a live product.