Service · App development

Custom press app development for publishers and newsrooms.

A custom press app for your newspaper, magazine or press room. From paywall flow and offline reading mode to AI transcription, journalist tooling and branded distribution of press releases — built on your own stack, not on a shared platform.

Paywall & subscriptionsOffline modePush & notificationsAI transcription

A press app is more than a news feed in a wrapper.

The big publishers, such as DPG Media and Mediahuis, run their own in-house app platforms, maintained at a cost of tens of millions of euros a year. For smaller publishers, trade journals, regional dailies and corporate press rooms, that is not a realistic route. A shared Tinypass or Piano stack is cheaper, but leaves little room for your own UX, your own brand or your own workflow. Apple News+ and similar aggregators do scale, but they take a considerable share of your subscription revenue, and you lose the direct relationship with your reader.

We build custom press apps that sit somewhere in between: less expensive than your own platform team, more flexible than a SaaS template. Whether it's a consumer reading app, an internal journalist tool or a PR distribution app for your corporate communications, we start from your editorial reality, not from a feature list. The difference rarely lies in technology and almost always in workflow: how copy gets from the field to publication, how a breaking-news push goes out without waking the entire newsroom, and what the paywall flow looks like for readers who only want to read one free article a month.

Press apps also differ fundamentally from other media apps. The requirements around source protection are stricter than for commercial apps. Expected uptime is higher: if a breaking-news push fails, you miss the moment. And the tension between editorial independence and commercial revenue (advertising, subscriptions, sponsored content) has to be visible in both the UX and the data architecture. These are choices you don't leave to a generic template.

Three types of press app we build.

Which direction suits you depends on who the end user is: the reader at home, the journalist on assignment, or the PR colleague distributing press releases. In our first conversation, we'll advise what will deliver the most for your situation.

Consumer · newspaper, magazine, trade journal

Reading app for subscribers

The classic press app: articles, a paywall, an offline reading mode for the train, push notifications for breaking news, and an audio version of longer articles via text-to-speech. Personalisation based on reading behaviour, shareable links per article, and sync between web and app so your readers switch seamlessly between channels. For magazines, we often build a variant with richer media layouts (embedded video, interactive graphics, full-screen photography), while for dailies the focus is on reading speed, low data usage and a minimal UI while reading. A community layer (comments, reader reactions, reader suggestions) is optional and depends on your editorial moderation capacity.

Apple/Google IAPOffline cacheTTS audioPushComments
Internal · journalists and editorial team

Journalist tooling on the move

A mobile working environment for your newsroom: writing and submitting copy from the field, photo and video upload with basic editing, a secure source archive, and AI transcription of interviews via Whisper or similar models. Includes encrypted communication with sources and location tagging for reports, so the chain of custody of your material remains demonstrable. For investigative journalism, we build a FOI request tracker (Wob/Woo) as standard, in which requests are followed up in a structured way, plus a minutes function that converts speech into structured text and automatically links it to the right case file. The editor workflow from the app to the newsroom supports version history and review comments, so copy can go from location to publication in two steps without any manual work left on desktop.

Mobile editorWhisper transcriptionSource protectionPhoto/video uploadGeo-tagging
Corporate · press room, PR agency, spokespeople

Press and PR distribution

For communications departments, spokespeople and PR agencies: a platform where press releases, press kits and quotes go out in a structured way to your own journalist database. Includes embargo management, multi-channel distribution and media monitoring, so you can see which outlets pick up your news. For larger organisations, we build in a quote management layer: which spokesperson is authorised for which topic, which quote has already been used by which journalist, and which embargo deadline applies to which channel. That saves the communications department a structural amount of manual work and prevents incidents with news items published too early. Trade associations and press freedom organisations often use the same stack to coordinate joint statements and international press moments.

Embargo flowPress kitJournalist CRMMedia monitoring

What you get at the end.

A working, production-ready press app, including everything your editorial team and IT team need to carry on with it themselves.

We work in sprints, deliver a test build every two weeks, and agree from the very first conversation which parts you want to manage yourself and which you leave with us.

  • The press app itself, iOS and AndroidReact Native or Flutter, your choice. Includes production and staging builds in App Store Connect and Google Play Console, and an automated release pipeline.
  • Headless CMS integrationIntegration with your existing editorial CMS (Naviga, Atex, WordPress, Drupal) or a new headless CMS such as Strapi, Sanity, Directus or Contentful.
  • Paywall and subscription stackApple/Google IAP for app-only subscribers, or Stripe/Mollie for your existing web subscribers, with a cross-platform entitlements layer so one subscription works across all channels.
  • Codebase plus architecture documentationFull source code, build instructions and an incident runbook. After handover, your IT department can deploy and fix bugs independently.
  • Analytics and monitoringPrivacy-friendly analytics (Plausible, Mixpanel with IP anonymisation) plus crash reporting and performance monitoring. GDPR-compliant by default, with no Google Analytics default.
  • Maintenance contract (optional)Ongoing maintenance, security patches, OS updates and further development for a fixed monthly price. Response times to suit you.

When custom is the right choice.

Not every publisher needs its own app, and not every app needs to be custom. Four patterns where we see custom development genuinely adds value.

Smaller publisher

Too small for enterprise, too big for a template

You are a trade magazine, regional daily or niche publisher. A Tinypass or Piano template is too limited for your editorial flow. Your own platform team is too heavy. A custom build scales with what you actually need.

AI features

Transcription, translation, summarisation

You want to relieve journalists with AI transcription of interviews, automatic summaries for readers, or translation of international wires. Generic press platforms don't offer this, or only to a very limited extent. We build it into your own LLM stack.

Multi-tenant

Publishing group with multiple titles

You are a holding company with several newspapers or magazines under different brands. One codebase, multiple apps, a shared backend and subscription layer: that is exactly where a custom build pays off compared with a per-title SaaS licence.

Corporate communications

Press releases and spokesperson work

You are not a publisher but an organisation with an active press room: a company, trade association or press freedom organisation. Generic PR tools lack an embargo flow and your own branding. Your own distribution app makes a difference to journalists.

Stack and platforms we work with.

No pre-packaged choice, no vendor lock-in. We work with the stack that fits your existing infrastructure and editorial rhythm.

Mobile framework

React Native or Flutter

For most press apps we recommend React Native, thanks to the large pool of front-end talent and the smooth integration with existing web codebases. Flutter is a serious alternative if you want a strongly graphic UX or a high density of animation. We only build native iOS and Android per platform when there is a specific reason for it — otherwise the double maintenance isn't worth it.

Content backend

Headless CMS of your choice

Strapi, Directus, Sanity or Contentful if you're starting from scratch. For publishers with existing editorial systems — Naviga, Atex, WordPress with the WP REST API, Drupal — we build an API layer that keeps the existing CMS in charge. We don't force a migration if your editorial team is happy with its current tools.

Push and notifications

Firebase, OneSignal

Firebase Cloud Messaging is the most common choice; OneSignal is an alternative with better out-of-the-box segmentation tools. For breaking-news pushes we build an editorial approval flow so that only authorised editors can send a push — no junior accidentally waking up three million devices.

Search and AI

Typesense, ElevenLabs, Whisper

For in-app search we work with Algolia, Typesense or Meilisearch — depending on budget and privacy requirements. For audio versions of articles we integrate ElevenLabs or Anthropic-based TTS. For journalist transcription, Whisper is the standard, optionally with an on-device variant so that audio never leaves the device.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Compliance: GDPR, EMFA, EAA and more.

A

GDPR and reader data

Reader data — reading behaviour, subscription status, payment history — falls under the GDPR. We minimise what is collected, arrange explicit consent for analytics and advertising, and put data processing agreements in place with every party that sees data. Cookie and consent flows follow the TTDSG and the Dutch Cookie Act. By default we use privacy-friendly analytics instead of Google Analytics, so that a refusal of tracking consent doesn't mean flying blind on your own app statistics.

B

EU Media Freedom Act (EMFA)

The 2024 EMFA sets requirements for transparency of ownership structures, editorial independence, and protection of journalistic sources. For a press app this means, among other things: ownership information visible in the app, a clear separation between editorial and commercial content, and demonstrable procedures for source protection. We advise on where the EMFA requirements affect product decisions.

C

Source protection and encryption

For journalist apps we build end-to-end encrypted communication with sources (Signal protocol or equivalent), so that even Appfront as the builder has no access to the content. Source databases are set up zero-knowledge where possible, and metadata minimisation is the default — no IP logs, and no retention of connection metadata for longer than operationally necessary.

D

DSA, AI Act and copyright

The Digital Services Act applies to the large publisher platforms, with separate reporting requirements on content moderation and advertising transparency. The AI Act requires transparent labelling of AI-generated or AI-edited content — we build those labels in so your editorial team doesn't have to keep track of them manually. For user-generated content (comments, reader photos) we arrange Creative Commons licences or explicit rights agreements via the submission flow.

E

EAA and WCAG for public media

The European Accessibility Act has applied since June 2025 to commercial services aimed at consumers — press apps fall under it. We build in WCAG 2.2 AA from the first sprint, not as a patch at the end. Readable text sizes, sufficient contrast, screen-reader-compatible navigation, and an audio version of articles that also works without external TTS. Public media (broadcasters, government bodies) often have stricter requirements, which we include separately in the scope.

How a press app project works.

1

Introduction and scoping conversation

We map out who the end user is: reader, journalist or spokesperson. We identify which flows the app needs to support, which existing systems are already running (CMS, subscription platform, ad server), and which compliance requirements apply — GDPR, EMFA, source protection, DSA, EAA. See also our page on app development for our broader approach.

2

User research and CMS architecture

Interviews with 3-5 end users — subscribers, journalists or spokespeople, depending on the type of app. Then we make decisions on the content architecture: does your existing editorial CMS stay in the lead, or do you integrate with a new headless CMS at the same time? The outcome is a workable scope plus the first screen flow.

3

Building in sprints

A working build every two weeks on TestFlight and in internal Android tracks. We start with the highest-risk parts: the paywall flow with Apple and Google review, offline sync, and the first integration with your CMS. Only then do we move on to secondary features such as comments, personalisation and TTS audio.

4

Store review and beta

Apple and Google have strict rules on paywalled content, child protection and in-app purchases. We handle the store submission ourselves, deal with any review questions, and test with a limited group of subscribers via TestFlight and Play Closed Testing before going public.

5

Rollout and further development

A phased release to your subscriber base, monitoring of crash-free sessions and the subscription funnel, and ongoing maintenance for OS updates, security patches and new features. An app is not a project that ends — it is a product that keeps running. From the start, we agree how new features are prioritised: fixed sprint capacity per quarter, or pay-as-you-go on request. For larger developments — a second title, a new subscription model, an ad server integration — we run them as a defined mini-project with its own scope and planning, so the live app keeps running stably while the new work is developed in a feature branch.

Frequently asked questions.

What editors-in-chief, publishers and heads of communications usually want to know before we start.

What types of press app do you build?
Roughly three flavours: a consumer reading app for subscribers (newspaper, magazine, trade journal), an internal app for journalists and editorial staff (mobile editor, transcription, secure communication with sources), and a corporate press or PR distribution app (press room, embargo management, journalist database). In the introductory call, we look at which combination suits your situation — sometimes it is a hybrid.
Apple/Google IAP or your own paywall via Stripe or Mollie?
It depends on where your subscribers come in. App-only subscribers must pay via Apple and Google IAP — the store guidelines require it. Existing web subscribers can keep paying through your own Stripe or Mollie flow and use their existing account in the app. We usually build a cross-platform entitlements layer so that a single subscription works across all channels, regardless of where it was purchased. Apple takes a 15-30 per cent commission on IAP, whereas your own stack only incurs payment fees — which makes for a serious calculation in your business case. See also our page on building a payment platform.
How does offline mode work for subscribers on the move?
Articles are cached locally on the device, either automatically (for example, a morning edition that is ready by 7 a.m.) or manually per article. Images are included at a reduced resolution. Comments and personalisation sync as soon as the device is back online. For longer journeys — on a plane, or on a train without coverage — this is one of the features subscribers value most.
What about AI transcription and copyright?
We work with Whisper or similar on-device and cloud models for transcribing interviews. Importantly, AI transcription does not change the copyright on the source material, and under the EU AI Act, AI-generated or AI-edited text must be transparently labelled for the reader. We build that labelling system in as standard, along with a log of which model processed which segment and when. For sensitive sources, transcription can run entirely on-device, so the audio never leaves the device.
What about GDPR for reader data and source protection?
Reader data falls under the GDPR: minimal data collection, explicit consent for analytics and advertising cookies, and a data processing agreement with every processor. By default, we use privacy-friendly analytics (Plausible or Mixpanel with IP anonymisation) instead of Google Analytics. Source protection is a separate category: for journalist apps, we use end-to-end encrypted communication (the Signal protocol or similar), so that even we as the builder have no access to the content. For large platforms, the DSA also applies, with its own reporting requirements.
How do we meet WCAG and the EAA for public media?
The European Accessibility Act has applied since June 2025 to all commercial services aimed at consumers, and press apps fall under it. We build in WCAG 2.2 AA from the first sprint: readable text sizes, sufficient contrast, screen-reader-compatible navigation, and an audio version of articles that also works without external TTS. Public media (broadcasters, government frameworks) are often subject to stricter requirements, which we can include in the scope separately.
What determines the cost of a press app?
Four factors dominate: the number of end-user types (readers only, or also journalists and editors), the depth of the paywall and subscription flow, the complexity of your existing CMS integration, and whether you need to run multi-tenant for several titles. After the scoping conversation, we give you an honest estimate for a first tier, and then build on a pay-as-you-go basis. If you first want to define the broader AI strategy, see our page on building an AI strategy.

Talk to us about your press app.

A no-obligation introductory call of half an hour. We listen to your editorial reality, think along on paywall strategy, AI tooling or distribution flow, and give you direction you can actually use. No sales talk. For related apps, there are also projects described under building a B2C app.

Edit content