Mobile Apps
An app is worth it when the work does not happen at a desk: when something is photographed, scanned or signed off, when there is no network, or when a notification has to arrive. Otherwise the browser is enough.
A capability is a means. The linked areas describe what it is used for.
What specifically gets built.
Every line is a commitment about future work — none of it is a claim about completed projects.
The decisions behind it.
Categories rather than vendor names — which product is used depends on your existing systems.
- One shared source base for both systems — a business rule is maintained in one place, not separately in the app and the web application
- Local storage with conflict resolution on sync
- Release in the App Store and on Google Play is part of the scope
What is not included.
So that no time in the intro call is spent on an expectation we do not meet anyway.
- No consumer app without a business process behind it
- No games, no entertainment applications
- No separate second application alongside the web version
These eight capabilities are means, not offerings. Which of them are used follows from the process — not the other way round. If you are not sure which ones you need, that is the normal case and not a problem.