Which types of publishers do you build magazine apps for?
We work for four main groups: specialist publishers with a B2B magazine for a professional readership, commercial consumer magazines (lifestyle, hobby, culture), regional newspapers and newsletters, and industry bodies or professional associations with a members' magazine. Corporate publishers producing their own magazine for customers or employees also fit this approach. For independent content creators in the Substack tradition, we build something lighter: the same architecture, with a smaller scope.
Which CMS do you integrate with?
We work most often with Drupal (widely used across the Dutch specialist and public publishing market), headless WordPress, Sanity, Storyblok and Strapi. For publishers with an existing CMS, we build a dedicated integration layer. What we don't do is force your editorial team to move to another CMS. If the team is productive on the current system, we build around it.
What is your approach to paywalls and freemium?
We build three standard models: hard paywall (only subscribers can read), metered paywall (X free articles per month) and freemium (free news, paid long reads or dossiers). The choice is about commercial strategy and audience, not technology: all three models sit in the same codebase with configurable rules. We integrate with Recurly, Stripe Billing or a custom subscription layer, and with iDEAL, Apple Pay, Google Pay and SEPA.
How do you handle Apple's in-app purchase rules?
Apple requires in-app purchase for digital content subscriptions sold within the app, along with its associated commission. We therefore always build two flows: an in-app offer via Apple or Google where required, and a web flow in which subscribers register and then log in within the app. Since the Digital Markets Act, more alternatives exist in the EU, and we factor that flow into the App Store review strategy.
Does the app also work offline?
Yes. Offline caching is essential for magazine apps. Readers download an issue on the train, on a plane or at the beach, and want to keep reading without a connection. We build the cache intelligently: recent issues and bookmarked articles are stored locally, while older issues are fetched on request, so the app doesn't take up unnecessary phone storage.
How do you produce audio versions of articles?
There are two options: text-to-speech using a high-quality Dutch voice (ElevenLabs, Azure Neural or Polly, depending on licensing requirements) for automatic audio versions, or human-narrated audio produced by your own editorial team. Many publishers combine both: TTS for daily short pieces, and their own audio for longreads and interviews. Where needed, we connect the audio flow to the same subscription layer and to a
streaming platform.
Native iOS/Android or Flutter?
Both are possible; it depends on the magazine app's requirements. Native development (Swift for iOS, Kotlin for Android) gives maximum control over reading typography, AR effects, dynamic type and accessibility features. Flutter offers faster build times for two platforms at once, but can sometimes limit heavy typographic and AR features. For most magazine apps we recommend native, as typography is more valuable to publishers than a few weeks of build-time saving. For multi-title portfolios, however, Flutter may be the right choice.
How does advertising work within the app?
We integrate with Google Ad Manager, Xandr or a direct ad server integration for your publishing house. We build native advertising in the editorial tone of voice as a dedicated content type in the CMS, not an external widget that clashes with the style. For ad transparency under the DSA, we build an ad archive and a disclosure flow. For magazines aimed at children or young people, we build explicit restrictions into the ad stack in line with the Dutch Advertising Code.
How do copyright and reuse work?
The Copyright Act and the DSM Directive protect articles, photography and layouts. In the CMS we build a rights layer that records, for each article, which licence applies: whether it can be cached offline, whether the text may be shared, whether an audio version may be produced, and whether it may be reused in a newsletter. These rights are enforced within the app, so nothing appears in a feature for which the rights have not been cleared.
How much does a magazine app cost?
A single-title app for one trade journal or consumer magazine is a different project from a multi-title portfolio for a media company with regional and national titles. The biggest cost drivers are: number of titles and multi-tenancy, depth of the CMS integration, paywall and subscription complexity (a single annual subscription versus a hybrid freemium model with several tiers), AR, audio and video features, and compliance demands (accessibility, DSA, ePrivacy consent flow). We work to a fixed sprint budget and give you a concrete price for the full build after the planning phase.
Who owns the source code?
You, the publisher. With each release we hand over the source code, build scripts, design tokens and deployment procedure in a Git repository of your own, which you manage. This is crucial for publishers: you can part ways with Appfront at any point without the app ceasing to work and without another development partner having to start from scratch. No lock-in to proprietary platforms, no black-box code.
Do you also provide maintenance after launch?
Yes. Magazine apps are long-cycle products. Every iOS or Android update requires compatibility testing, and every change in legislation (a DSA amendment, a ruling by the Dutch Data Protection Authority, an accessibility requirement) means the flows need to be reassessed. We offer a fixed monthly maintenance contract, first-line incident response and agreed roadmap capacity for new features. If your IT team would rather take over, we supply the runbooks and documentation so the handover can happen without any dependence on us.
