Industry · Publishing & media

Magazine app development. For publishers who want to keep their readers in their own hands.

We build custom magazine apps for trade publishers, consumer magazines, regional newspapers and industry associations. Editorial flow from your CMS, paywall or freemium, offline reading mode, push notifications for new issues, audio versions and native ads — all in one app that your publishing house owns.

TypeTrade journals & B2B magazines
TypeConsumer magazines
TypeRegional newspapers
TypeIndustry & association magazines

The Dutch publishing market in figures.

~600
Members affiliated with publishers' industry associations
~50%
Digital share of magazine revenue
~7,5M
Dutch people read a digital news outlet every day
~80%
Of reading happens on mobile, via an app or mobile web

Indicative proportions based on NDP Nieuwsmedia, Mediamonitor and Magazine.nl annual figures.

Where publishers lose the most to platforms.

For most publishers in 2026, the pain point is not creating content. The editorial team is responsible for that, and it has worked well for years. The problem lies in the distance between that editorial team and the reader — a distance that large platforms are actively widening. An article that only appears in social feeds or in an aggregator app builds no reader relationship of your own, no subscriber data, and no repeat visits that the publisher controls.

Your own app reverses that trend. Readers download your magazine's app, open the first issue, receive a push notification when a new issue is published and read offline on the train. That reader is in your subscriber database, not a platform's. Issues come straight from your editorial CMS — Drupal, WordPress, Sanity, Storyblok or Strapi — without a vendor putting a layer between you and your reader.

Many publishers once started with their own app on Adobe Digital Publishing Suite or a similar platform. Those platforms have quietly been wound down in recent years, have become too expensive, or the vendor has been acquired. What remains is an app the publisher has no source code for, cannot connect a design system to, and must reorder from the vendor with every iOS or Android update. A custom app has no such dependency: the code is yours, the design fits your brand, and we handle every OS update under a maintenance contract that you can leave whenever you wish.

The other recurring theme is the subscription model itself. Many magazines have a hybrid flow — a few free articles, then the paywall, and above that a paid subscription with archive, audio and possibly live events. That layer rarely lives in a single system. Your own app keeps that flow tidy in one place: we connect the paywall, free quota, freemium trial, annual subscription and membership to a payment and subscription layer that also handles iDEAL, Apple Pay, Google Pay and SEPA direct debit. That reduces sign-up and cancellation frustration and gives the publisher visibility of churn before it becomes a problem.

An app that fits the type of magazine you publish.

A trade journal for accountants needs a different flow from a lifestyle magazine or a regional newspaper. For each type of publisher, we show what we typically build.

Trade journals & B2B magazines

Trade publishing is a market in its own right. Readers are professionals, subscription prices are higher than in the consumer market and the content has archive value. For an accountancy journal, a legal trade journal or a medical journal, the app is often also a reference work in which readers search, cite and download PDF extracts.

For this segment we build an app with a full-text search layer across all editions, an article citation export (BibTeX, RIS, plain), a CPD points registration integration where relevant, and an eIDAS-compliant digital signature for B2B subscription renewals. The CMS integration with a headless CMS or headless commerce layer keeps the editorial flow tight.

  • Full-text archiveAll editions searchable, with filters for author, section and volume.
  • Citation and PDF exportReaders export articles for their own files or publications.
  • CPD points or accreditationIntegration with NBA, NOvA or medical professional registers for reading registration.
  • eIDAS signatureFor business subscription renewals and purchasing contracts.
  • B2B licence flowEmployer subscription with SSO via SAML or OIDC for the whole department.
  • Native advertising slotsTrade-relevant ads in the same tone of voice as the editorial content.

Built within the full compliance framework for publishers.

A magazine app touches subscriber data, ad tracking, copyright and digital accessibility. From the first sprint we work within all relevant frameworks and deliver the DPIA and accessibility reporting alongside.

GDPR & UAVG

Subscriber data & profiling

Subscriber databases fall under the GDPR, with an explicit legal basis required for reading-behaviour analysis. We set up the architecture with data minimisation, retention settings and an opt-in for profiling that is strictly separate from the subscription contract.

ePrivacy Directive

Push, cookies & trackers

Push notifications, ad cookies and analytics trackers require valid consent under the ePrivacy Directive and the Dutch Data Protection Authority's guidance. Our CMP layer (Cookiebot, OneTrust or an open-source alternative) is integrated without compromising the reading experience.

Dutch Copyright Act 1912 + DSM Directive

Copyright & press publishers' right

The Dutch Copyright Act and the DSM Directive protect articles, photography and layout. We build rights management into the CMS integration, so it is clear for each article which licence applies and which uses (offline cache, sharing, audio version) are permitted.

Digital Services Act

Content moderation & advertising transparency

The DSA sets requirements for advertising transparency, ad repositories and moderation of user contributions. Our ad server integration and any comment system are set up to be DSA-compliant, including making it mandatory to show who is paying for an ad.

Advertising Code + child protection

Ad restrictions & target audience

Magazines with a younger audience are subject to extra restrictions on ad content and the sharing of personal data. We build filters into the ad stack and integrate age verification where relevant, in line with the Dutch Advertising Code and the NRC guidelines for marketing to children.

eIDAS Regulation

B2B digital signature

For B2B trade publications where subscription contracts and purchase confirmations are signed digitally, we deliver eIDAS-compliant signatures with an audit log and qualified timestamp.

EAA + WCAG 2.2

European Accessibility Act

Since 28 June 2025, the EAA requires digital publishing products to meet WCAG 2.2 level AA. From the first sprint we build with semantic markup, VoiceOver support, dynamic text sizing and colour contrast, so there is no retrofit work afterwards.

Cyber Resilience Act

Security maintenance across the lifecycle

The CRA obliges publishers with digital products to apply patch management, vulnerability reporting and a Software Bill of Materials. Our releases ship with an SBOM and dependency scanning as standard, which is essential for publishers with a long-cycle subscription product.

Seamlessly connected to the publisher's ecosystem.

We integrate with the CMS, paywall, subscription software and ad server your editorial and commercial teams already use. No rip-and-replace: the app connects to what is already in place and does not replace any editorial workflow.

Drupal
Editorial CMS
WordPress
Headless & classic
Sanity
Headless content
Storyblok
Visual-editor CMS
Strapi
Open-source headless
Recurly / Stripe
Subscription billing
Mollie / Adyen
iDEAL, Apple Pay, Google Pay
Google Ad Manager
Ad serving & native

No one-off integrations on a per-project basis.

We have standardised the integrations above: one integration layer on top of the editorial CMS, a second layer for identity and subscriptions (Recurly, Stripe Billing, your own subscriber database), and a third for advertising and analytics. On each new project we reuse these abstraction layers, so the effort goes into the early phases and build time shortens for later publishers.

For media companies with multiple titles and shared SSO, we build a multi-tenant identity layer, so one reader with one account can access several apps (trade portfolio, consumer portfolio or regional portfolio). For publishers who also offer video or podcasts, we integrate with a streaming platform, so audio versions of articles, video essays and even live streams fit into the same app without the publisher having to maintain two different apps.

For commerce features — a webshop for single issues, merchandise, yearbooks or event tickets — we integrate with a headless commerce platform that lives inside the same app. That way, the publisher can set up cross-sell flows without sending readers to a separate webshop and without ending up with the UX stack of two different systems.

From editorial audit to going live in the App Store and Play Store.

A magazine app project rarely starts with the technology. First we look at the editorial flow, the subscription structure and the ad stack. Only then do we build — in sprints that involve the editorial and commercial teams.

01 · Audit

Editorial and subscriber mapping

A day in the newsroom with a managing editor, a commercial manager and your IT or digital lead. Result: the current flow mapped out, data points marked, and a sharp scope for the first edition.

02 · Design

Editorial UX and brand system

A dedicated template flow for each type of contribution — news, longread, interview, opinion, dossier. The brand system comes straight from your existing house style, not from a generic app template.

03 · Build

Sprints with editorial testing

A working slice every sprint: CMS integration first, then offline cache, then paywall, then push, then ads. The editorial and commercial teams test every release straight away.

04 · Beta and review

TestFlight, Play Console, app review

We guide you fully through a closed beta with subscribers and the App Store and Play Store review processes — including the discussion around in-app purchase rules and alternative payment flows.

05 · Maintenance

Releases, OS updates and analytics

With every iOS or Android update, every change in legislation and every new edition feature, we keep building. Fixed monthly price, and you keep the source code under your own control.

In every project we explicitly work together with your existing IT supplier, design agency or marketing agency. We build the app layer and the subscriber and payment layer connected to it; the editorial CMS, the main website and any DAM systems we leave where they are if they work. For publishers in the media city of Hilversum or other creative hotspots, we work from our team in the media city of Hilversum and Amsterdam, with a physical presence at the editorial location where that helps.

What we typically build for magazine apps.

Trade journal · B2B

Reference app with CPD integration

Edition app for a trade journal with a full-text archive across volumes, citation export and an integration with the professional register for reading CPD points. eIDAS signature for business subscription renewals.

Headless CMS
editorial stack
SAML SSO
employer licence
Consumer magazine

Editorial app with audio and AR

Monthly edition with an offline reading mode, text-to-speech for on the go, AR overlays for cover shoots and native ads in the editorial team's tone of voice. Hybrid paywall with a free quota and an annual subscription.

iDEAL / Apple Pay
payment stack
CMP-ready
ePrivacy & GDPR
Regional daily newspaper

Editions, breaking news & podcast

Daily edition app with breaking-news push notifications, podcast versions of longreads and hyperlocal ad targeting. Multi-tenant identity for a media company with several regional titles under one holding company.

Multi-tenant SSO
one account, multiple titles
EAA / WCAG 2.2
accessibility

Trade associations & corporate publishing.

Alongside commercial publishers, we work for trade associations, professional bodies and corporate publishing departments that want to release their members' magazine as an app. The dynamics differ from those of commercial publishers: the revenue model is based on membership rather than single-copy sales, the subscription is often linked to a membership administration that runs outside the app, and advertising is limited or even excluded because membership fees cover the income.

For trade associations, we build app flows that connect directly to the membership system (Procurios, e-Captain, AFAS or a custom CRM layer), with SSO via DigiD or eHerkenning where appropriate and automatic deactivation when a membership ends. For corporate publishing, such as a large company with its own magazine for customers or employees, we connect to the organisation's existing SSO (Azure AD, Okta, Workday) and to an internal content flow managed by corporate communications.

For content creators in the Substack or independent publishing tradition, we build apps that differ in scale but run on the same architectural layer: an editorial CMS, a paywall, a subscription layer, a community feature and push notifications. The difference lies in the creator's editorial autonomy and the requirement that the app lives in its own brand system from day one. That suits a custom app approach well: one creator, one brand, its own design system, no template look.

For all three groups (commercial, members' magazine, corporate publishing) the recurring decision is the same. Do you build on a platform that may be acquired or shut down in three years' time, with all your content and subscribers locked into it? Or do you build on your own codebase with standard components that you can never be locked out of? We build the second, and we document the handover so thoroughly that another development team can take over the app without the publisher remaining dependent on Appfront.

How the publishing market thinks about apps.

NDP Nieuwsmedia: Vision on digital

"For publishers, the digital relationship with the reader is the most important channel they own. Their own apps and their own subscriber data determine whether a publisher can stay independent alongside the big platforms."

European Accessibility Act: enforcement 2025

"From June 2025, digital editions of magazines and newspapers must meet WCAG 2.2 level AA. Accessibility is no longer optional but a product requirement."

Reuters Institute Digital News Report

"Apps from European publishers show higher subscriber retention than mobile web alone, provided the app genuinely offers its own reading experience and is not just a repeat of the web."

Answers for publishers going digital.

Questions we often hear from editors-in-chief, digital leads and publishers of trade and consumer magazines.

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.

Talk to us about your magazine app.

A half-hour introduction with a editor-in-chief, digital lead or publisher. We listen to your editorial and subscription flow, sketch a first direction and give you an honest view of what is feasible. No obligation.

Edit content