Custom software
Mobile Apps for Your Customers or Your Team
You need an app for your customers or your team, and you don’t want to pay twice, once for each mobile system. We develop a single app that works on both and publish it under your name on both app stores.
- A single codebase
- Publishing on the stores
- Ongoing maintenance
Who it is for
It is for you if…
- Companies that need an app for customers, employees or technicians who work out in the field.
- Companies with a web application that they also want on mobile, without redoing what already works.
- Companies whose app stores people’s data and that need to control who gets in and what they do from day one.
It is not for you if…
- We don’t make video games. We make apps that handle information: orders, appointments, work reports, customer records.
- Anyone who only wants their website to look good on mobile. That’s solved within the website itself.
What you get
- The app, for both mobile systems
A single app that can be installed from both stores and works equally well on both.
- The server behind the app
Where the app stores and retrieves its data, with control over who has access and no servers to maintain.
- Publishing on the stores
Your app's page on each store, with texts and screenshots, and the app published under your name.
- Code and documentation
Everything under your name, with what's needed to maintain the app and publish new versions.
One app for both mobile systems
We develop the app once and it works on both mobile systems. It isn’t a website disguised as an app: it becomes a native app on each system and runs just as smoothly. Every change is made only once, which is why it costs less to maintain.
The server behind the app
An app stores and retrieves data somewhere. That part isn’t visible, but it’s the one doing the work. It isn’t a server someone has to maintain: it switches on when users come in, and you pay for what you use. If you already have a system with your data, the app connects to it.
Who gets in and what they can do
Each user sees only their own information. A record is kept of who did what and when. And the app talks to your data over a secure connection, the one with the padlock.
Testing, publishing and maintenance
Every version is tested on both mobile systems before release. It is published on both stores under your name. The store accounts belong to your company, not to us. If you don’t have them yet, we’ll sort that out at the first meeting. Afterwards, we keep the app up to date. Before a new version of the phone’s system comes out, we update the third-party components. That way, the app keeps working.
What we build it with
The app is built with Flutter: a single codebase compiled natively for iOS and Android. Behind it sits a serverless backend on AWS, Amazon’s infrastructure: Lambda functions, an API, authentication and a database. The App Store and Google Play listings are prepared, and the app is published under your account. The code is delivered to your repository, the place where it is stored along with its full history. It comes with everything needed to maintain the app and publish new versions.
Glossary
- Flutter
The tool we use to develop the app once so that it works on both mobile systems.
- Backend
The part of the app that runs on the server: it stores the data and checks who gets in.
- Native compilation
Turning the code into a native app for each mobile system, not a website disguised as an app.
What problems it prevents
What can go wrong and how we prevent it.
- The app working well on one system and badly on the other
A native app is generated for each system, and both are tested before every version.
- The app stopping work when the phone's system is updated
Maintenance: the third-party components it uses are updated before they stop working.
- Your users' data being exposed
Each user sees only their own information, a record is kept of who did what, and the connection is encrypted.
- Being dependent on us
The code and the store accounts are yours. You can carry on with another provider.
Frequently asked questions
It depends on how many screens it has and whether the server behind the app needs to be built. After the meeting, we'll give you a plan in stages. The first usable version arrives before the full app.
Yours. The code is yours, and the app is published under your accounts on both stores.
One meeting to understand what the app does and who uses it. Afterwards, we send you a fixed-price quote, broken down by stages.
Because for an app that handles information, the result is just as good. And it costs less to maintain. If your project needs something this approach doesn't cover well, we'll tell you at the first meeting.