Frequently asked questions about
having an app built

Answers to the questions we get most often from clients having an app built for the first time.

Preparation and strategy

What do you need to know before having an app built? We explain what an MVP is, when you need a mobile app and when a web application fits better.

What is an MVP and why should I start with one?

An MVP (Minimum Viable Product) is the smallest possible version of your app that already delivers value to users. You only build the features strictly necessary to solve the core problem.

An MVP makes sense because it limits risk: you invest less and discover sooner whether the concept works. You then learn from real users what they are missing and develop further based on that feedback.

We help you determine the MVP scope during the intake meeting and what to save for a later phase.

What is the difference between an app and a web application?

Mobile app — installed via the App Store or Google Play, runs directly on the device.

  • Access to camera, GPS and push notifications
  • Works offline
  • Higher barrier for users (installation required)

Web application — runs in the browser, no installation needed.

  • Lower barrier for users
  • One codebase for all devices
  • Easier to update

Sometimes a combination is the best solution: a web application for administrators and a mobile app for end users. We advise you based on your target audience and requirements.

Technology and development

Which technologies do we use and why? From Flutter to offline-first architecture and integrations with existing systems.

What is Flutter and why do you use it?

Flutter is an open-source framework from Google that lets you build apps for iOS and Android from a single codebase. The app compiles to native code, making performance comparable to fully native apps.

Flutter is our default choice for cross-platform projects because:

  • one team and one codebase reduces costs
  • delivery is faster
  • quality remains high

We are one of the first agencies in the Netherlands to work seriously with Flutter and have since published dozens of Flutter apps. For projects where deep integration with platform-specific features is essential, we choose native Swift (iOS) or Kotlin (Android).

Can I expand my app with new features later?

Yes. We build with a modular architecture so new features can be added later without disrupting existing code.

In practice, we discuss during the design phase which features are in scope now and which are saved for a later phase. This keeps the first version affordable while the architecture already accounts for what comes later.

After launch we work in two-week sprints so you can add new features step by step based on user feedback.

What is offline-first and when is it needed?

Offline-first means the app works fully without an internet connection. Data is stored locally on the device and synchronised with the server once a connection is restored.

This is essential for apps in environments with poor or no network connectivity, such as:

  • warehouses and construction sites
  • slaughterhouses and agricultural locations
  • field services in remote areas

We have built this for clients including MSD Animal Health and Het Waterschapshuis. Offline-first requires more architectural work, which affects the price and timeline.

How do push notifications work?

Push notifications are sent via Apple Push Notification Service (APNs) for iOS and Firebase Cloud Messaging (FCM) for Android.

From the backend you can send notifications to:

  • individual users
  • specific groups
  • all users at once

We build the backend so you can schedule, segment and track notifications. Push notifications are effective for time-sensitive information, but too many leads to opt-outs. We advise you on a good strategy.

Can my app integrate with my existing software?

Yes. We have extensive experience integrating with systems such as AFAS, Exact, SAP, Salesforce and custom APIs.

We also build the backend and APIs ourselves, so you have one point of contact for the entire technical picture. During the intake meeting we assess which integrations are needed and whether the existing systems have well-documented APIs.

Integrations with poorly documented or legacy systems require more work and may affect the timeline.

Publication and quality

How does the publication process in the App Store and Google Play work, and how do we test an app before it goes live?

How does the publication process in the App Store and Google Play work?

We manage the entire publication process: from creating developer accounts to writing app descriptions, screenshots and privacy policies.

Apple App Store: Apple reviews each app manually. This typically takes one to three working days but can take longer if Apple has additional questions.

Google Play: the review process is faster and largely automated.

Updates go through the same review process but are generally faster than the initial submission.

What do I need to create a developer account?

Apple Developer account: €99 per year. Register at developer.apple.com/programs/enroll/.

Google Play Console: one-time €25. Register at play.google.com/console/signup.

We assist with both registrations and guide the entire publication process.

How do you test an app before it goes live?

We test on multiple levels:

  • Automated tests: verify the core logic of the app
  • Manual tests: on real devices, for both iOS and Android
  • Test environment: via TestFlight (iOS) and the internal test track of Google Play you can test every sprint and provide feedback
  • Regression test: before the final release we verify that existing features still work correctly

Security and privacy

How do we ensure your app is secure and GDPR-compliant? We explain how we handle personal data and security.

How do you ensure my app is secure?

Security starts with the architecture. Standard measures we always apply:

  • Encrypted connections (HTTPS)
  • Sensitive data never on the device unless strictly necessary
  • Correct authentication and authorisation
  • Backend on Google Cloud with standard security layers

For apps with medical or financial data we apply additional measures such as certificate pinning and encrypted storage. We follow the OWASP Mobile Top 10 as a guideline.

What about GDPR and privacy?

If your app processes personal data, GDPR applies. We build apps that are privacy-friendly by default:

  • Only request data that is strictly necessary
  • Store nothing that is not needed
  • Implement correct consent flows

If we act as a processor for your user data, we put a data processing agreement in place. We advise you on what you as the data controller need to arrange yourself, such as a privacy policy and a record of processing activities.

After launch

Who owns the source code, what does maintenance cost and how do you keep an app healthy after delivery?

Who owns the source code after delivery?

You do. The source code is entirely yours after delivery and payment. We hand over the code via a Git repository of your choice.

You are never dependent on us: you can transfer the code to another party or develop it internally. We document the code and architectural decisions so it is understandable for another team.

There are no licence fees or hidden obligations.

What does app maintenance cost after launch?

Apple and Google release new versions of their operating systems every year. Without updates your app can become outdated or be removed from the stores.

Each quarter we provide an advisory report on recommended work:

  • Framework updates and dependency upgrades
  • Security patches
  • Performance improvements

You decide which to have carried out. There is no mandatory maintenance contract. Average annual maintenance costs range between €2,000 and €8,000. Deferring maintenance builds up technical debt that requires a larger catch-up later.

★★★★★

Ready to get started?

Let's grab a coffee. Tell us about your idea and we'll give you our honest take on what's possible.

Schedule a call →
WhatsApp