Mobile app development?Start with the build plan.

For an app on iOS and Android, with everything underneath

Mobile app development?
Start with the build plan

An app is rarely one thing: there is a backend underneath, integrations alongside and an iOS and Android shell around it. In the chat you describe what the app has to do, that becomes a build plan of tasks and our Code Agents build them one by one. A person decides at three gates, and the code sits in your own repository from the first task.

From request to app in the store

Why have an app developed?

Four reasons for a custom mobile app

Automate

Move manual processes from spreadsheets and email to a single app. Fewer errors, shorter turnaround and more room for work that actually matters.

Integrate

The connection to your ERP, CRM or API landscape is a task in the build plan, with its own acceptance criteria. One source of truth, no double entry.

Scale

With cross-platform frameworks like React Native or Flutter one codebase runs on iOS and Android. A new feature is then one task in the build plan, not two.

Innovate

AI components in your app detect patterns in usage and data. You ask for that functionality as a task, like any other feature.

Mobile app development: how you see what it costs

We do not make a quote and we do not estimate up front. What an app costs depends on what you build, and an estimate up front would be a number we could not stand behind. What you do get is visibility at three moments.

Before anything starts

Your request becomes a build plan: an ordered list of tasks with acceptance criteria, from architecture and backend to the iOS and Android shell and the store release. You see the size of that plan before you approve it. That is the first gate.

While building

What the factory builds is deducted from your AI balance. You see your consumption and your remaining balance live in your project screen. If the balance runs out, the AI work stops until your balance is replenished on the renewal date, or until you move up to a larger plan.

Human work at three gates

Our architects review the build plan, every implementation in the preview and the merge. That work is charged at an hourly rate and is separate from what the factory consumes.

  • No quote and no estimate up front

  • You see the size of the build plan before you approve it

  • Use of your AI balance, live

From request to working app

The same six stations as on the page How the factory works, but for an app: backend, API, iOS and Android shell, push notifications and store release are tasks in the build plan.

  1. Your request

    Your request

    It starts in the chat: what the app has to do, for whom, and how you will measure it. Does a field engineer need to order offline? Does a customer get a push notification when their order is on its way? What we set down there is the set of acceptance criteria the agents check themselves later on.

  2. The build plan

    The build plan

    Your request becomes an ordered list of tasks, from foundation to features: architecture, stack and user management first, then the backend and API, the iOS and Android shell, push notifications and the store release. The choice between native, cross-platform and web app is one of those tasks. You see the size before anything starts and give your approval: the first gate.

  3. Agents build

    Agents build

    A planner writes the task instruction, a builder implements, a reviewer comments and a fixer works through it until tests, code style and static analysis are green. One task is built at a time: the login screen starts only after the API behind it has been merged. Every task is exactly one pull request, and per task you get a preview you can click.

  4. Architect reviews

    Architect reviews

    Every implementation is judged in the preview before it is submitted. That is the second gate. One of our architects looks at architecture, security and whether it feels right on a phone, because those are questions a person answers better. You click through the same preview.

  5. Merge and deploy

    Merge and deploy

    Nothing is merged without approval. That is the third gate, and merging and deploying is always done by a person. That person can be you, because the code sits in your own repository from the first task. Almost no hand work touches the code itself; the decision is another matter.

  6. Go-live

    Go-live

    Submission to the App Store and Google Play is a task in the build plan, just like the first version itself. After that you ask for the next feature in the chat and it passes through the same six stations. You are not waiting for a sprint planning, because a task starts the moment you ask for it.

Looking for mobile app development?

Looking for mobile app development?

Bring your app to the chat. You get a build plan whose size you see before anything starts, a clickable preview per task, and the code in your own repository. No sales pitch and no quote, but a factory that builds and architects who review.

Native, cross-platform or web app?

The difference between native, cross-platform and web app

Which type of app fits depends on your users and on what the app needs from the device. That choice is a task in the build plan: the architect records the trade-off before the first shell is built. Below we compare the three options.

Native app (Swift or Kotlin)

A native app is built specifically for iOS (Swift) or Android (Kotlin). You can use all device capabilities: camera, sensors, offline storage and push notifications. The downside: two codebases, so two tasks in the build plan for every screen.

Cross-platform and Progressive Web App

With cross-platform frameworks such as React Native or Flutter you write one codebase that runs on both iOS and Android. For most business apps this is the route with the fewest tasks per feature. A Progressive Web App (PWA) runs in the browser but feels like a native app, without installation via the App Store. Ideal when reach matters more than advanced hardware integration.

Maintenance and continued development

What happens after go-live?

  • OS updates: Apple and Google release new versions annually. Your app needs to keep pace.

  • Bug fixes and performance optimisation based on real user data

  • New features based on user feedback and business goals

  • Server and hosting costs for the backend and API layer

Continued development through the chat

Every new feature, OS update or bug fix you ask for in the chat. It becomes a task with the same checks and the same three gates as the first version, and you follow the use of your AI balance live. Hosting and monitoring run monthly; have a look at our software development services for that.

Already have an app that needs to move faster?

Then we put the Code Agent on your existing project. After that you ask for your next feature yourself, in the chat, with a preview per task and a person who merges.

Continuous improvement with data

Analytics is a task in the build plan, so you see exactly which screens perform well and where users drop off. Those insights become your next requests in the chat.

AI in app development

How the factory builds an app

The factory builds, architects review

Almost no hand work touches the code of your app. Code Agents build every task in the build plan: a planner, a builder, a reviewer and a fixer, until tests, code style and static analysis are green. Our architects do what a person does better: review the build plan, look at every implementation in the preview and decide on the merge.

AI components in your app

AI functionality in the app itself is a task in the build plan, like any other feature. Think pattern recognition, predictive analytics or smart search features. All with attention to privacy and EU data sovereignty, because sensitive data stays where you want it.

Full control over your data

For apps with AI components, transparency is essential. Through our #MIND platform you can track exactly how AI decisions are made: traceable via an Audit Trail, with roles and permissions that you define.

Hans Lugtenberg

"A deal is a deal"

Yield.inc is a new asset manager in the Netherlands that focuses on excellent customer experience, sustainability and technology. When faced with the question of whether to develop our platform in-house or with a partner, we got in touch with Spartner. We are still 100% behind the choice for Spartner because we own the source code and with Spartner, a deal really is a deal, whether it concerns the delivery date or the agreed budget!

Hans Lugtenberg Partner at Yield Inc.

Norbert Wegter

"A professional software partner since 2010"

Spartner is involved and contributes in our search for innovations and always delivers top-notch work. After the first Huurda.nl version got out-dated, we collaboratively launched a completely new version in 2020.

Custom-built search engine for rental properties

Norbert Wegter Owner of 123wonen and Expat Homes Holland

"Doijer & Kalff"

After transferring our D&K portal to Spartner, we have elevated the further development and continuity to a higher level. Although the D&K platform was originally developed internally, our technical expert can now focus on other innovations within Doijer & Kalff. Spartner provides the quality we need without excessive costs. They have seamlessly taken over the care of our portal, allowing us to benefit from a flexible capacity that perfectly aligns with our future plans and innovation goals.

Reinier van Bergen Managing Director at Doijer & Kalff

Jurjen Terpstra

"Pragmatic and flexible collaboration"

Spartner has created a customized portal for us for the accountability of large-scale collaborative projects. This enables us and our partners to execute and account for their plans in a shared environment that is secure, transparent, and manageable. The pragmatic and flexible collaboration with Spartner has ensured that we have quickly achieved a functional and user-friendly environment.

Jurjen Terpstra Managing Partner at Wecreate Consulting

Marco Caspers

"AI and machine learning as legal tools"

In 2020, we transferred the development of Lynn to Spartner. As a result of their fast development process, the Lynn platform achieves an increasingly central role in the legal world.

Lynn, the smart AI legal robot

Marco Caspers Software Development Manager at Lynn Legal

Bjorn Gubbels

"As a business you must dare to move forward"

Innovation and change are not always welcomed with equal enthusiasm by our employees, man is a creature of habit but as a company you have to dare to move forward and the need for a contemporary drawing program for the realization of various constructions with our Masterbloc bricks was high. For us but also for Spartner, this challenge was a bit of pioneering and together we had to overcome some hurdles to arrive at a beautiful and efficient business tool. A development and learning process for both parties, in which the feedback of questions and desired adjustments by our employees to Spartner was always in good consultation and we could count on quick feedback and targeted solutions. We continue to exchange experiences with Spartner and look back and forward to a successful collaboration.

Powerful 3D construction drawing software

Bjorn Gubbels Owner of Masterbloc

Marco Leenders

"Spartner extends our capabilities and development capacity"

With weekly calls, using our Azure DevOps sprint system, Spartner actively works together with our innovation, communication and software development departments.

Multi-website CMS with Statamic 3

Marco Leenders Head of Automation

Josh Mountain

"Have been using Laravel Excel for years"

We requested custom help to a performance challenge we had in our implementation of Laravel Excel. I was amazed how quickly these Laravel artisans achieved significant performance gains, which saved us a lot of development time.

Open source package for Laravel

Josh Mountain Co-Founder at IncentivePilot.com

Maurice Evers

"Higher occupancy rate thanks to our user-friendly platform"

Throughout the great years that we cooperate with Spartner (previously Maatwebsite, Ed.), our software has been developed continuously. Students and landlords actively work with features like allocation, payments, chat, contract generation and more.

Custom built ERP for all student residences

Maurice Evers Head of Student Housing Department

Maarten Bremer

"Innovating in the digital identification network of The Netherlands and Europe"

The pro-active approach of Spartner was crucial in understanding the complexity of the eHerkenning network.

Development of eHerkenning connection and services

Maarten Bremer CTO / Founder Ensured

Niels Winters

"Innovation in legal technology"

As jurists with knowledge of IT, we highly value quality; within code, but also in process. The high work-level and trustworthiness of Spartner gives us the capacity to continuously create innovative features.

Legal tech platform

Niels Winters Managing Director JuriBlox

Frequently asked questions about mobile app development

Answers to the questions we hear most often about mobile app development, costs and the process.

How much does it cost to have an app developed?

We do not make a quote and we do not estimate up front, because what an app costs depends on what you build: the number of platforms, the connections to your ERP or CRM, offline use, AI components. What you do see: the size of the build plan before you approve it, and while building how much of your AI balance you have used. The pricing page explains how the AI balance works.

How long does mobile app development take?

That depends on the number of tasks in your build plan, and you see that before anything starts. The factory builds one task at a time and the next one starts as soon as the previous one has been merged. You are not waiting for a sprint planning and you see a preview per task, so you have a working part of the app in your hands early on. We do not promise a lead time, because we could not stand behind it.

What is the difference between a native app, cross-platform app and web app?

A native app is built for one platform (iOS or Android) and uses all hardware capabilities. A cross-platform app (React Native, Flutter) shares one codebase across multiple platforms, which means fewer tasks per feature. A web app (or PWA) runs in the browser and requires no installation. Which option fits depends on your target audience and your technical requirements, and that choice is a task in the build plan.

What steps are involved in mobile app development?

Six stations: (1) your request in the chat, (2) the build plan with tasks and acceptance criteria, which you approve, (3) agents build one task at a time and every task becomes a pull request, (4) an architect reviews every implementation in the preview, (5) a person merges and deploys, and (6) go-live, after which you ask for the next feature in the chat.

Can I start with an MVP and expand later?

Absolutely, and that is how the build plan is structured: first the foundation, then the core features. With a Minimum Viable Product (MVP) you launch the core functionality, gather feedback from real users and then expand in a targeted way. Every next feature is a new request in the chat and passes through the same checks, so you do not build what nobody is waiting for.

What does app maintenance cost after launch?

Hosting and monitoring run monthly. Continued development goes through the chat: every new feature, OS update or bug fix becomes a task, with the same use of your AI balance that you see live. If you already have an app, we put the Code Agent on your existing project.

How secure is an app with AI components?

AI adds no extra risk when the basics are in place: encrypted storage, secure models and clear data flows. We use privacy-by-design as a foundation and ensure EU data sovereignty. Via an Audit Trail it is traceable how AI decisions are made.

How do I decide which features my app needs?

You decide that in the chat, at the build plan. Tell us which problem the app solves and for whom; what you set down there becomes the acceptance criteria per task. Start with the core and expand based on real user data. Per task you judge the result in the preview, and whether something feels right is decided by a person looking at it, not by the factory.

What would you change first?

Enter your web address and say what needs to change. You see it on your own site before you decide anything.

No account needed. You see a first result within a minute.

We have received your message. We will contact you shortly. Something went wrong sending your message. Please check all the fields.