Do food bloggers need an app to sell a recipe membership?

No. A members website works on every phone, can be found through Google and takes card payments directly. An app becomes worth it once members use your recipes weekly on their phones and ask for one.

Do Apple and Google take a cut of recipe subscriptions?

If the subscription is bought inside the app with in-app purchase, yes: Apple keeps 15% or 30%, and Google keeps between 10% and 15% plus a billing fee in some markets. Payments taken by card on your own website only carry the card processor’s fees, which is why most creator apps sell on the web.

Is a PWA a good alternative to a native recipe app?

Sometimes. A well-built PWA can work offline and keep the screen on in cook mode, and it skips app store review and fees. On iPhone, though, members have to add it to their home screen before it can send notifications, and many never do.

Can my recipe app be published under my own name?

It has to be. Apple’s guideline 4.2.6 rejects apps made from templates or app builders unless they are submitted by the provider of the content, so your app goes out under your own developer account.

Apps and payments · For food creators

Recipe app or recipe website: which should food bloggers build?

Q: How much does it cost to build a recipe app?

Commissioned from scratch, the most common mobile app budget in Clutch’s 2026 pricing guide is US$10,000 to US$49,999, with an average project cost of about US$90,780, plus yearly upkeep. Apple’s developer account adds US$99 a year and Google’s a one-off US$25.

Updated 14 October 2026 · 7 min read

The short answer

For most food bloggers, a members website should come first: Google can find it, members pay you directly by card, and it costs far less to build than a native app. A native iOS and Android app is worth adding once members use your recipes every week on their phones and ask for one, because it lives on their home screen and works better in the supermarket and the kitchen. A web app installed to the home screen sits in between, but on iPhone few of its benefits arrive unless members take the extra step of installing it.

The three options

When food creators talk about “an app”, they usually mean one of three things. They behave differently for members, and they cost very different amounts.

	Members website	Web app (PWA)	Native app
Where it lives	Your domain, in any browser	Your domain, optionally saved to the home screen	App Store and Google Play
Found through Google	Yes, for public pages	Yes, for public pages	No
How members pay	Card checkout on your site	Card checkout on your site	Usually in-app purchase, or sign in after paying on the web
Store review	None	None	Every new build
Works offline	Limited	Yes, if built for it	Yes
Push notifications	Email instead	iPhone: only once installed	Yes

A PWA (progressive web app) is a website built to behave like an app: it can be saved to the home screen, open full screen and cache content for offline use. A native app is built for iOS and Android and installed from the stores.

Discovery: how new members find you

Websites are visible to Google

Your free recipes on your own domain can rank in Google, get shared as links and be pinned. Even with AI Overviews taking clicks (see what AI Overviews are doing to food blog traffic), search still introduces people who have never heard of you.

The content inside a native app isn’t a web page, so it doesn’t rank. If your app is the only home for your recipes, every new member has to come from somewhere else first.

App store search favours names people already know

Apple says almost 65% of App Store downloads happen directly after a search. That sounds like a discovery channel, but think about what people type. Generic searches such as “recipes” or “meal planner” are dominated by large apps with big ad budgets. The searches you can win are for your own name, which means the person already follows you.

In practice, a creator’s app gets its installs from the creator’s own audience: Instagram, TikTok, YouTube, email and the blog. The store is where they install it, not where they find you.

Fees: where the money goes

This is the part that changes your margin most.

Selling inside a native app

Apple’s App Review Guidelines say that an app selling access to premium content or subscriptions must use in-app purchase (guideline 3.1.1). Apple keeps 30%, or 15% for developers in its Small Business Program (under US$1 million in proceeds a year) and for subscriptions after their first year.

Google Play charges 15% on subscriptions in most markets. In the US, UK and European Economic Area it moved on 30 June 2026 to a 10% service fee on subscriptions, plus 5% if you use Google’s own billing.

Selling on your website

On your own site, members pay by card through a processor such as Stripe. Stripe’s standard rate in New Zealand is 2.65% plus NZ$0.30 per domestic card payment.

A worked example

400 members paying NZ$12 a month, so NZ$4,800 a month in sales:

Where they pay	Fee per member	Monthly fees	You keep (before other costs)
Your website, Stripe	about NZ$0.62	about NZ$247	about NZ$4,553
Apple, 15%	NZ$1.80	NZ$720	NZ$4,080
Apple, 30%	NZ$3.60	NZ$1,440	NZ$3,360

Figures are rounded and ignore GST, platform fees and currency conversion. The gap is still clear: card checkout on the web costs a fraction of an app store commission.

That’s why most creator apps take payment on the website and let members sign in to the app with the same account. Apple’s rules on this vary by app type and storefront. In the US storefront, apps may now link out to web checkout, and the commission Apple can charge on those purchases is still before the courts. Elsewhere the rules are stricter. Settle this before you build, not after. We cover it in detail in app store fees vs web checkout.

App review and accounts

A website or PWA goes live when you publish it. A native app has to pass review, and two guidelines matter for creators:

Minimum functionality (4.2). Apple says an app should be more than “a repackaged website”. A web page wrapped in an app shell risks rejection. Recipe tools such as scaling, shopping lists and cook mode help an app clear this bar.
Template apps (4.2.6). Apps made from a commercial template or app builder are rejected unless they are submitted by the provider of the content. In plain terms: your app has to be published under your own developer account, not your app builder’s.

That means paying for your own accounts. Apple charges US$99 a year and Google a one-off US$25.

Cost to build and run

A members website is the cheapest of the three, and a membership platform can cover most of it.

Native apps cost more to build and keep running. Clutch’s 2026 pricing guide, based on reviewed projects, puts the most common mobile app budget at US$10,000 to US$49,999, with an average project cost of about US$90,780 and a typical timeline of around 11 months. A recipe app with accounts, payments, scaling and shopping lists won’t be at the bottom of that range if you commission it from scratch.

Then there’s upkeep. Each major iOS and Android release can need fixes, and every native change goes back through review. Budget for it every year, not just at launch.

A PWA costs a little more than a plain website, because offline storage and install prompts need extra work and testing on iPhone.

What members actually use

Members of a recipe membership don’t sit and browse. They plan the week, shop and cook. Judge each option on those three moments.

Planning: meal plans and scaling

Weekly meal plans, servings that scale and switching between metric and imperial all work equally well in a browser and in an app. This is where a website does fine.

Shopping: the list in the supermarket

A shopping list that combines ingredients across recipes is one of the most used features in any recipe product. Jenn Lueke’s eat goood newsletter has more than 182,000 subscribers, and its paid tier delivers meal plans and grocery lists by email. An app studio’s write-up of her newsletter makes the obvious point: an email client “cannot check off a box”. A list members can tick off in the aisle is something a website or app does and an inbox doesn’t. When Voyage built the Two Raw Sisters app for New Zealand’s plant-based duo, the shopping list was the feature everything else was designed around: it builds itself from the week’s meal plan and sorts by supermarket section. The app is a native one, sold on the App Store and Google Play, so in-app subscriptions pay Apple’s and Google’s commission; the recipe membership examples guide has its prices and features.

Supermarkets often have poor signal. A native app can keep the list on the phone. A PWA can too, if it’s built for offline use. A plain website may stall on the next page load.

Cooking: hands covered in flour

Cook mode means large steps, timers and a screen that stays on. Safari has supported keeping the screen awake for web pages since version 16.4, though for several versions it didn’t work in web apps saved to the home screen. Native apps have always been able to do it.

Coming back: reminders

A native app can send push notifications: this week’s plan is ready, a new recipe is up. On iPhone, a web app can only send them once the member has added it to their home screen, which Apple has supported since iOS 16.4, and many people never take that step. Without an app, email does this job, and does it well.

How to choose

Your situation	Start with
Testing whether your audience will pay	A members website
Members cook from it weekly, mostly on phones	Website, then add a native app
Your recipes rely on offline use (camping, travel, remote areas)	A native app or a well-built PWA
No budget for build and upkeep	A members website

Our rule of thumb: launch on the website, watch how members use it, and add an app when they ask for one. Your website keeps doing the jobs an app can’t: ranking in Google, taking card payments and selling to people who haven’t joined yet. If you’re starting from scratch, read how to start a recipe membership first.

Where Voyage fits

Launch with Voyage partners with established food creators to launch their own recipe membership, website first. Your site works on every phone, with scaling recipes, shopping lists, meal plans and cook mode, and members pay into your own Stripe account. When you want a native iOS and Android app, we design and build it as an add-on, listed under your own developer accounts with your name and icon, and members sign in with the account they made on your website. The website and membership have no monthly or setup fee; we take a share of sales, from 10%, and the app is priced separately. See your own app with Voyage.

Your own app with Voyage