What types of publishers do you build magazine apps for?
We work for four main groups: trade publishers with a B2B magazine for a professional audience, commercial consumer magazines (lifestyle, hobby, culture), regional daily and news titles, and trade associations or professional bodies with a members' magazine. Corporate publishers with 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 with Drupal (big in the Dutch trade and public-sector publishing market), headless WordPress, Sanity, Storyblok and Strapi. For publishers with their own CMS, we build a dedicated integration layer. What we don't do is force your editorial team to switch to a different CMS: if the team is productive on its existing 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 deal with Apple's in-app purchase rules?
Apple requires in-app purchase for digital content subscriptions that are taken out within the app, with the associated commission. That's why we always build two flows: an in-app offer via Apple/Google where needed, and a web flow where subscribers register and then log in to the app. Since the Digital Markets Act there are more alternatives in the EU, and we include that flow in the App Store review strategy.
Does the app also work offline?
Yes. Offline caching is a must-have for magazine apps: readers download an issue on the train, on a plane or on the beach and want to keep reading without a connection. We build the cache smartly — recent issues and bookmarked articles stored locally, older issues on request — so the app doesn't take up more phone storage than necessary.
How do you handle audio versions of articles?
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 the short daily pieces, in-house audio for longreads and interviews. We connect the audio flow to the same subscription layer and, where needed, to a
streaming platform.
Native iOS/Android or Flutter?
Both are possible, depending on the requirements of your magazine app. Native (Swift for iOS, Kotlin for Android) gives you maximum control over reading typography, AR effects, dynamic type and accessibility features. Flutter offers a faster build for two platforms at once, but can occasionally impose limitations on heavy typography and AR features. For most magazine apps we recommend native — typography is worth more to publishers than a few weeks of saved build time — but for multi-title portfolios Flutter can be the right choice.
What about advertising in 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.
What about copyright and reuse?
The Dutch Copyright Act and the DSM Directive protect articles, photography and layout. In the CMS we build a rights layer that records, per article, which licence applies: whether it can be cached offline, whether the text may be shared, whether an audio version may be created, and whether it may be reused in a newsletter. These rights are enforced in the app — nothing appears in a feature for which the rights haven't been cleared.
What does a magazine app cost?
A single-title app for one trade magazine or consumer magazine is a different project from a multi-title portfolio for a media company with regional and national output. 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 multiple tiers), AR/audio/video features, and compliance requirements (accessibility, DSA, ePrivacy flow). We work with a fixed sprint budget and, after the planning phase, give you a concrete price for the complete build.
Who owns the source code?
Your publishing company. With every release we hand over the source code, build scripts, design tokens and deployment procedure in your own Git repository, which you control. For publishers this is crucial: you can part ways with Appfront at any time without the app ceasing to work and without another development partner having to start from scratch. No lock-in on proprietary platforms, no black-box code.
Do you also provide maintenance after go-live?
Yes. Magazine apps are long-cycle products — every iOS or Android update requires compatibility tests, and every change in legislation (a DSA amendment, a Dutch Data Protection Authority ruling, an accessibility requirement) means flows need to be reassessed. We work with a fixed monthly maintenance contract, first-line incident response and an agreed amount of roadmap capacity for new features. If your IT team wants to take over, we provide the runbooks and documentation so the handover can happen without any dependency on us.