What is the difference between a B2C app and a B2B app?
The end user determines everything. With
B2B, that is a professional in a work context, where efficiency, integrations and role management weigh most heavily. With B2C, it is a consumer in their free time: onboarding has to land within seconds, push notifications must not irritate, and you have to deal with App Store rules that don't exist for internal software. The choice of features differs too: social login hardly works in a business context, in-app purchases are often mandatory via the stores for B2C content, and personalisation is far more central. The codebase may look similar, but the design and the metrics differ fundamentally.
Cross-platform (React Native, Flutter) or native iOS and Android?
For the vast majority of B2C apps, cross-platform works perfectly well and is more cost-efficient: one codebase, shared features, and releases that run in step on iOS and Android. We choose native when the app relies on heavy AR/VR, 60fps gaming graphics, intensive use of Bluetooth/NFC, or when fintech security demands tighter platform APIs. Often it is a hybrid: a React Native or Flutter shell with native modules where they are really needed. The right answer almost always emerges from an initial technical session in which we walk through the heaviest features.
What about App Store and Play Store policies?
Apple and Google are strict, and their rules change regularly. At intake we run a policy check on the well-known sensitive areas: sensitive content, children as a target audience, health claims, financial features, use of advertising, Sign in with Apple requirements, and which payment route is permitted. Throughout the project we keep track of policy updates and build the store listing in an early sprint, so you don't run into a rejection only at the very end. If an app is rejected, we help with the appeal to Apple or Google and with the necessary changes.
In-app purchases via the stores or your own payment solution?
For digital content and subscriptions you are in principle required to use Apple IAP and Google Play Billing, with the accompanying commission of 15 to 30 per cent. For physical products, remote services (such as a ride, hotel room or delivery) or business subscriptions, you can run your own payment solution via Stripe, Mollie, Adyen or another payment platform. The line isn't always drawn in the same place, and for some cases it is a grey area. Together we decide which route fits best, implement it cleanly, and take into account Digital Markets Act exemptions where they apply.
What is ASO and what do you do for it?
App Store optimisation is the SEO of the app stores: keywords, title, subtitle, screenshots, video preview and your rating curve determine which users see you and who converts to an install. We do keyword research for the right market, deliver a first set of screenshots in both languages, and build an in-app rating flow that asks at the right moment: after a success moment, not at start-up. After going live we keep improving iteratively based on conversion data per keyword and variant. We handle the build work; your marketing team or agency picks it up from there with campaign tooling.
How do you keep users engaged after the first install?
A mix that differs per app. Push engagement with personalised messages via Braze, OneSignal or Firebase Cloud Messaging, based on behaviour and time of day. Email and in-app campaigns via a CRM integration (HubSpot, Salesforce, Klaviyo). Referral and loyalty mechanisms that reward users for coming back or inviting others. In-app support via chat (Intercom, Zendesk) so that a question doesn't lead to an uninstall. Not everything at once: we start with the two or three channels that look likely to deliver the most for your target audience, and expand when the data supports it.
Does GDPR-K apply if children use our app?
Yes, and it's not a formality. For apps aimed at children under 16 (in the Netherlands) you need explicit parental consent, you may not run behavioural advertising without safeguards, you must be able to demonstrate data minimisation, and you must register the app in a different category in the stores (Apple's Kids Category, Google's Designed for Families). We help with the DPIA, the consent flow and the store classification. Apps that aren't primarily aimed at children but do have a share of young users are subject to lighter but relevant requirements, and we scan for those too.
What determines the cost of a custom B2C app?
Three main factors: the complexity of the core flow (a focused content app versus an app with payments, identity, AR features and heavy integrations), the breadth of the launch portfolio (the Netherlands only or multiple countries and languages, one target audience or several segments) and the level of support after going live (maintenance only or ongoing product development). Compliance aspects such as WCAG/EAA, GDPR-K or PSD2 also play a role in the first sprints. After an introductory meeting we give a substantiated indication for an initial tier, and only on the basis of a fully worked-out scope a fixed price per sprint, so you know where you stand.
How quickly can we go live?
A first working build for a focused B2C app is usually available within a few sprints, via TestFlight and Play Console internal testing. This is followed by a soft-launch and refinement phase before we launch widely on both stores. For larger apps with PSD2, EHR integrations or recommendation engines, expect a programme of several sprints, phased by target group or region. An exact schedule takes shape during the discovery phase, based on scope and dependencies on your side.