Skip to content
AppDues
Log in
Contact salesSign up

What a Quiet App Launch Teaches About Shipping and Pricing

A launch can be well prepared and still arrive on a day nobody is listening. That is the situation David Barnard described when he sat down with Charlie Chapman on the Sub Club podcast to walk through the Weather Up 3.0 release. The result was smaller than he hoped, but the review produced four lessons that apply to almost any subscription app team: how often to ship, how much to rely on a single announcement, how to test paywall defaults, and how to set a price.

Ship in increments instead of saving features for one event

The pull toward a big reveal is understandable. App stores are crowded, and a single dramatic release feels like it should cut through. Barnard's argument runs the other way for subscription products. A recurring revenue model lets a team build value continuously and let that value compound; the older pattern of paid apps and paid upgrades did not reward that behaviour in the same way. Holding features back for years, he said, was his own mistake.

For a reader planning a release, the practical translation is a cadence decision. Smaller updates keep the product visibly alive, give existing subscribers a reason to stay engaged, and signal to prospective customers that the app is still being developed. A useful check before you defer a feature to a future "big" release: does waiting actually improve the feature, or does it only improve the theatre around it? If the answer is the second, ship it.

Assume the news cycle will not cooperate

Barnard lined up a website announcement and worked his press contacts before Weather Up 3.0 went out. The same day, Apple revealed sweeping App Store changes across the EU tied to the Digital Markets Act, and the app's story was buried under the bigger headline. The preparation itself was sound; what failed was the assumption that one day of coverage could carry the release.

Sorting a launch's risks into two buckets makes that assumption easier to challenge. Controllable items — release cadence, paywall defaults, price framing, whether a launch-day offer exists — can be decided in advance and reviewed afterwards. External items — a competitor's announcement, a platform policy shift, a slow news week — can only be hedged. Hedging means spreading attention across owned audiences, existing subscribers, community posts, and a steady release rhythm, so no single day has to do all the work. Any press hit then becomes upside rather than the load-bearing wall.

Test which plan is preselected on the paywall

The launch was not only a story of setbacks. On the Sub Club podcast, Barnard described building a custom paywall and running experiments that compared users who saw the annual plan selected by default with users who saw the monthly plan selected by default. He reported that, among the people who saw monthly as the default, 1,100 stuck with monthly and only 100 switched to annual, and that 10% more people converted when they saw the monthly plan by default.

Read that result carefully. It is a comparison of default selections, not a verdict that monthly is always the better default. The number that matters for a subscription business is revenue, not raw conversion, and a monthly-heavy mix can look strong on sign-ups while producing a different long-term revenue shape than an annual-heavy mix. The transferable practice is the test itself: make the default an explicit variable, measure conversion and revenue together, and re-run the test when your audience or price changes.

Price against what customers think the app is worth

After the 3.0 release, the $40/year annual plan did not perform well. Some users compared Weather Up with similar weather apps that cost less, including some with more features. Barnard's own diagnosis was that he had priced from what he knew, from his view of the app's value, and from the cost of servicing it, rather than from the value customers perceived.

That distinction is worth making concrete. Cost-plus reasoning asks what it takes to run the product. Perceived-value reasoning asks what a customer compares this app with at the moment of purchase. Both matter, but a price that only reflects the first will often sit above what the market expects. A simple check: list the two or three alternatives a prospective subscriber is likely to weigh, and ask whether your price reads as reasonable next to them.

If you want attention, pair it with a reason to act

Barnard's biggest regret about the release was not the annual price itself. It was that he did not run a launch-day sale. His advice was direct: if you are going to do a big, attention-grabbing thing, attach some kind of discount to it. If press coverage does arrive, a visible sale price gives those new visitors a reason to convert rather than to bookmark and drift away.

The discount is a lever, not a strategy on its own. It works best when the launch has a clear audience and a clear moment, and when the discounted price still leaves room for the product to be valued on its merits afterwards.

Keep expectations in check and share what went wrong

The broader point is that preparation reduces risk but does not remove it. A launch can be well organised and still be overtaken by events. What matters is whether the team extracts a usable lesson and applies it to the next release. Barnard's own encouragement was for developers to talk about the failures they have been through, because those accounts help the wider community calibrate its own expectations.

A short post-launch review is enough to make that habit stick: what was in your control, what was not, and which single change will you carry into the next release?

Frequently asked questions

Does the paywall experiment prove monthly should always be the default?

No. It shows that in that test, more people converted when monthly was preselected. Conversion is not the same as revenue, and the right default depends on your price, audience, and how you want the subscriber mix to look over time. Treat the result as a reason to test your own default rather than as a universal rule.

Should every app launch include a discount?

Barnard's advice was conditional: if you are making a big, attention-grabbing push, give people a reason to act at that moment. A discount is one way to do that. It is not a substitute for a product that is worth its regular price afterwards.

Why did the $40/year annual plan underperform?

Barnard's own explanation was that the price reflected his knowledge of the app, his sense of its value, and the cost of servicing it, rather than what customers perceived the app to be worth. Users compared it with similar weather apps that cost less.