App development · iOS and Android
Mobile apps for work on the move
Take a photo, document a condition or look up information at a job site: a mobile app starts with the activity on the phone. I help businesses and organisations turn that activity into a clear development project.
An application for customers or a hobby group is also possible. Before choosing the technology, we look at who will use it, on which devices and in what conditions. An office workstation has different needs from a basement with unreliable reception.
door frame.
Note.
Context.
The place of use shapes the interface
For a handover report, someone might open a case, attach photos and fill in missing information. The form must explain what is still needed and whether information has already been transmitted. Small buttons or lengthy mandatory text can get in the way on site.
Other uses include checklists, product information, collection management or recording service jobs. Camera, location and notification features are agreed individually. Access to a device feature is only included if the task requires it.
Compare a browser application with an installed app
| Decision | What we clarify |
|---|---|
| Access through a link | Are the supported browsers capable of what is needed? |
| Installation on the device | How do users receive the app and updates? |
| iPhone, Android or both | Which devices actually need support? |
| Camera and other features | Which permissions and device interfaces are needed? |
A web app may be the right form for your needs. An installed app and its distribution add requirements. We assess the intended user journey before committing to platforms or a price.
Offline also means synchronising changes later
Working without a connection requires more than displaying a screen. We decide which data is stored on the device, which actions remain possible and how users recognise a successful transfer.
Conflicts matter too: what happens when two people change the same case or a photo uploads later? The necessary rules and tests are described as a distinct scope. A portal may also be useful for shared customer documents.
Price the app project and test it on real devices
Costs depend on functionality, supported platforms and required interfaces. Login, offline synchronisation or payment are additional work packages. A clickable prototype can clarify the interface first; it is not yet an operational app.
You provide typical tasks, sample data and the intended devices. Before handover, we test agreed user journeys, permissions and error cases. Publication, store accounts, fees and maintenance after operating system updates are agreed separately.
Questions about development and publication
Can we start with one platform?
Yes. The first audience and its devices can define the starting point. A second platform is assessed separately for technical and commercial viability later.
Can you publish the app in the app store?
This can be part of the project. Accounts, materials and responsibilities are clarified first. Approval by the relevant store cannot be guaranteed.
Can we try out an app idea first?
A prototype can demonstrate selected screens and decisions. We specify exactly which functions are demonstrated and which are already implemented.
Your contactRafael Hager
The first step
Which task should your app handle on the move?
Describe a task your users should complete on the move.
All software services ↗