Project approach
Web and mobile app development
First we make clear whose job the app solves. Then we choose between a website, a PWA or a mobile app according to device access, offline use and distribution needs.
At a glance
- Page type
- Approach note
- Line of work
- Software and apps
- Related product work
- PayRadarTest build
- LaserDeck PTTPre-release · source code public
This page is the approach note for the Software and apps line of work. What that line delivers and what stays outside its scope are on the services page.
What do we settle in the first call?
The users, the main screens, the data flow and the devices the app will run on. If an account, notifications, payments or an outside service is needed, we handle it separately within the first scope.
Something you can inspect
Once the scope is clear, we agree the screen flow, a prototype and the acceptance criteria. Source code, installation notes, test coverage and publishing responsibilities are set in the quotation and contract.
An example from the portfolio
PayRadar shows offline receivables and payment tracking; LaserDeck PTT shows Bluetooth and Android device permissions. They have different technical needs; we do not recommend the same stack for every project.
Related product work
Let’s assess the scope together
Describe the work you want to solve, the current flow and the output you expect. We will assess a suitable approach and the scope of the work.
Describe your project ↗This page explains the approach for a project enquiry; it is not a binding offer or a service contract. The start and terms of any commercial work are settled in writing. Collaboration framework · Operator and contact
Last updated: