Requesting app changes

Reply to any email from us. That is the whole process. There is no ticket form and no queue to sit in.

What is worth knowing is which kind of change you are asking for, because the timelines are very different.

Changes that are live the same day

Anything driven from our backend rather than baked into the app:

• Prices, offers and discounts
• Paywall copy and which plan is highlighted
• Content, lessons, articles, whatever sits behind the subscription
• Push campaigns
• Feature flags we already built behind a switch

Ask in the morning, it is usually live by the afternoon.

Paywall variants are the most common thing we swap. These three all ran on the same app in the same month:

Changes that need an app update

Anything that changes the app itself: new screens, new features, redesigns, a new icon. We build it, submit it to Apple, and Apple reviews it. Review is typically a day or two but Apple sets that pace, not us.

So the honest timeline for a new feature is: build time, plus Apple, plus however long your subscribers take to update. Plan around a week rather than a day.

How to ask for something useful

The more specific the request, the faster it ships. Compare:

Can we make the paywall better?

with:

The paywall converts badly on the annual plan. Can we try leading with annual, showing the monthly price underneath as a comparison, and adding the "cancel anytime" line?

The second one gets built. The first one gets a call to work out what you meant.

If you do not know what the fix is, describe what you are seeing instead. "Subscribers churn in week two and I do not know why" is a good message. We can look at the data and come back with options.

What counts as a bug

Something we built not doing what it was supposed to do. Report it with what you did, what you expected, and what happened instead, plus a screenshot if there is anything to see. We fix those without discussion.

A feature that works as designed but that you now want to work differently is a change, not a bug. We will still do it, it just goes through the flow above.

What we say no to

Rarely, but it happens: anything that breaks Apple's rules and would get the whole app pulled, anything that misleads your subscribers about what they are paying for, and anything that would put your account or ours at risk. If we push back on something, we will tell you exactly what the risk is and propose the closest thing we can build instead.