Services · App development
Do you want to launch a new app product? Or does your company need an app for employees or customers? Together, we define what the first version should do, develop the app and agree on what happens after launch. You do not need a finished requirements specification to get started.
Your team takes photos on site, checks deliveries or documents service visits. We look at the whole process with you: who uses the app, which devices they use and where the information needs to go. We include existing systems in the planning.
You have an idea and want to turn it into your own app product. Together, we define the target audience and core function. This gives us an initial scope that users can try out. Further features follow from what we learn with this version. A prototype helps you make decisions; it does not prove demand.
We work out the requirements and user flows, develop the app and test it before launch. Whether a backend, user accounts or interfaces are needed depends on the project. We specify these components in the proposal.
An internal app needs a different distribution approach from a public product. We therefore clarify early on who will use the app, how it will reach their devices and who is responsible for the required accounts. Privacy information, permissions and future maintenance are also part of this planning.
Workspace can provide a foundation for the functions you need. We check whether it suits your product. An app does not automatically require introducing an ERP system.
You bring your idea or an existing work process. We clarify the users, core task and open questions. For a new product, we also discuss how it will be offered.
A prototype can demonstrate the main user flow or test a technical question. We define which decision it should support and what feedback we need.
You receive a proposal with deliverables and acceptance criteria. During development, you review work in progress. The first version focuses on the agreed purpose.
We test the agreed processes and prepare distribution. Before launch, we establish who handles bugs, maintains updates and commissions later changes.
Our focus is Android apps. We test the camera, scanner, Bluetooth and notifications on the intended devices. If you need other platforms, we clarify feasibility and scope before making a commitment.
If the app needs to work without a network, we define which information stays on the device and when it is transferred. Interrupted transfers and conflicting changes also need agreed rules.
Shared data, roles and switching devices may require a backend. We discuss who can view and change which information, and what should happen if a device is lost.
We check which existing systems need connecting and which system holds the authoritative data. For purchases or subscriptions, we also clarify the requirements of the chosen distribution channel. Recurring fees are part of the cost assessment.
Checking deliveries and documenting damage: Proofara shows how a mobile workflow supports work on site. For your project, we likewise consider the information people need to enter and the next step in their work. See Proofara
A household shopping list that works without an account and uses encrypted synchronisation between devices. This experience is relevant to clear lists and shared data. PickQueue is not a sales ordering solution. See PickQueue
Timetables, notes and assignments for university: Sapeluno shows our work on an app product of our own. The product idea, user experience and ongoing development need to work together. See Sapeluno
The main factors are the initial feature set, platforms and devices, user experience, backend and interfaces. Offline use, shared data or payments can require additional work. We therefore define the first version before estimating its cost.
The initial consultation is free of charge and without obligation. For larger projects, we clarify the scope in a paid workshop first. We offer clearly defined phases at a fixed price; open questions are handled on a time and materials basis within an agreed budget.
The proposal separates development and introduction from ongoing operation and maintenance. Costs may include hosting, external services, store fees and updates. We only quote an overall price or commit to a start date once the scope is sufficiently clear.
New operating system versions, feedback and bug reports may require changes. If you wish, we take on maintenance and further development. We agree the scope, responsibilities and recurring costs before launch.
For a startup, we look at which features users actually need after the first version. For a company app, we review how it performs in everyday work. These findings help determine the next development step.
Yes. Describe who the app is for and the task it should solve. We use that to work out the initial scope together.
Yes. We help turn an app idea into a product, from defining the initial scope through development to distribution. Funding, demand and commercial success remain separate responsibilities within your venture.
A prototype tests a specific question, such as the user flow. A first usable version fulfils the agreed core scope and is tested and accepted against that scope.
No. That depends on the data and collaboration you need. Shared data, user permissions or switching devices may require a backend.
The right distribution method depends on the devices, users and how they are managed. We clarify this before development.
After clarifying the requirements, you receive a proposal for the agreed scope. Operation, maintenance and further development are described and agreed separately.
Tell us about your product idea or the task in your business. We will work out the next step with you.