Skip to content
AppDues
Log in
Contact salesSign up

A Patron Plan With No Extra Features: What a Two-Person App Studio Learned

Most subscription tiers sell access: more data, more exports, more seats. A two-person studio called Not Boring Software tried something different. Its most expensive tier added almost nothing in the way of features. It was a way for customers to fund the studio's work. This guide walks through how that tier was framed, why the studio ships each app as a finished product, and where the craft details — sound, camera, controls — carry the experience.

The rule that started the studio: no more boring software

The studio's founding story does not begin with a market map. It begins with a conceptual artist. John Baldessari, by his own description, spent years as a middling landscape painter. Shortly before he turned 40, he destroyed the paintings he had made up to that point and then, on camera, wrote the sentence 'I will not make any more boring art' over and over. He became one of the most influential artists of his generation.

Andy Allen encountered that story at a similar age. He had been working inside analytics dashboards at WeTransfer, which had acquired his earlier company, and he could feel himself drifting into product work that was in fashion but felt hollow. Baldessari's blunt rule gave him a usable heuristic: if you simply refuse to make boring software, better outcomes may follow.

The timing was deliberately out of step. In 2020, the momentum was all behind SaaS, not new app businesses. Allen's own observation is that the projects with the most staying power in his career have tended to be the ones that looked uncool at the start, while chasing whatever felt current tended to fizzle. That is the frame the rest of the studio's choices hang from.

Why a support tier can work when a feature tier would not

A feature tier answers the question, 'What more do I get?' A support tier answers a different question: 'Do I want this work to continue?' Those are separate buying motives, and they need separate framing on the paywall.

The studio's first release bundled three utilities — Weather, Calculator, and Timer — each buyable alone or together through one subscription. Weather's paid angle was easy to explain: it opened up better data sources. Calculator and Timer were harder to justify on features alone, since the paid tier mostly delivered skins, alternate themes, and replacement app icons. Alongside those tiers sat the patron plan, set at five times the standard price. What it added was a physical gift and the satisfaction of keeping the studio going — almost no functional upside at all.

More people chose that plan than the team anticipated. The takeaway is narrower than 'charge five times as much and call it goodwill.' A support tier and a feature tier are distinct products with distinct jobs, so they deserve distinct measurement. When a support tier stalls, the useful question is whether the audience feels any stake in the work. When a feature tier stalls, the useful question is whether the feature earns its price.

A simple field map keeps the two from blurring together:

  • What the buyer gets: a feature tier adds capability; a support tier adds belonging and, sometimes, a token like a physical gift.
  • What the buyer is really paying for: access versus continuation of the work.
  • What to watch after launch: feature-tier conversion and refund reasons versus support-tier retention and repeat support.
  • What a weak result means: the feature is not worth the price versus the audience is not yet attached to the work.

A checklist before you add a support tier

Use this as a pre-launch review, not a guarantee of results. The worked example below is the studio's three-app launch: Weather sold on better data, Calculator and Timer sold on skins and icons, and the patron plan sat above both at five times the standard price with a physical gift and little else.

  • Can you describe, in one sentence, what the buyer is funding? If the answer is only 'more features,' a support tier is the wrong frame.
  • Is there a visible body of work the buyer can point to? A studio with a public catalog is easier to support than a single opaque app.
  • Does the support tier include something tangible or symbolic, such as a physical item or a named thank-you? The studio's tier included a physical gift.
  • Are you prepared to keep shipping new work rather than iterating on old apps? A support tier rewards a pipeline, not a backlog.
  • Have you separated support-tier metrics from feature-tier metrics? Conversion, churn, and refund reasons will differ.
  • Will existing subscribers be grandfathered if terms change? The studio locked in early subscribers' pricing permanently.

Shipping a complete product instead of an endless roadmap

The second structural choice is that every app arrives finished. No V3, no creeping feature list, no chatbot tacked onto a corner. The studio's own framing is plain: this is the calculator we built, it is complete, it does its job well, and we will not change it out from under you.

That constraint creates a forcing function. If you cannot keep iterating on old apps, you have to make new ones. For a studio that wants to re-envision familiar software categories through a design-first lens, that is the work itself, not a side effect.

The origin of that caution is worth understanding. The founder's earlier company made a drawing app that became a well-loved iPad product and was eventually acquired. Raising venture money for a product that is a great small business but not a billion-dollar outcome can leave founders trapped in a business they did not want to run. Shipping complete products and funding them through a support tier is one way to avoid that trap.

Where the craft shows up: sound, controls, and camera

These apps read more like games than utilities. They run on Apple's 3D engine (SceneKit), and the low-poly models lean toward the PS1 era rather than photorealism. The first thing most people register, though, is the audio.

A single tap is not one recording. It draws from roughly a dozen subtly different takes of the same click — a trick lifted from game audio, where footsteps and punches have to repeat without wearing thin. The studio shared the method and free sound kits so other developers could copy it. The ask is small: bring in a sound designer, and the app itself barely grows in complexity.

The camera took three years and several dead ends. The team tried 3D photography and spatial photos before landing on a plainer idea: leave the camera's job alone and rethink how it feels in the hand. Controls are modeled in 3D — dials rotate, sliders carry weight, buttons tilt depending on where you press. The preview sits inset like a viewfinder instead of filling the screen. On the image side, the app bypasses Apple's computational photography — multi-frame composites, noise reduction, HDR tone mapping — and reads raw sensor data directly, which the studio calls 'Super Raw.' Film-inspired LUTs are applied live, and grain and blur are treated as creative choices rather than defects.

A support tier fails differently from a feature tier

When a feature tier underperforms, the usual suspects are price, packaging, and whether the feature is worth paying for. When a support tier underperforms, those suspects mostly miss the point. The audience either feels connected to the work or it does not.

A quick way to read the two patterns side by side:

  • Feature tier, low conversion: the feature is not worth the price or is poorly packaged.
  • Feature tier, high refunds: buyers expected more capability than they got.
  • Support tier, low conversion but strong retention: likely working as intended for a small, committed audience.
  • Support tier, high initial conversion then high churn: buyers probably misunderstood what they were funding.

That distinction matters for how you read your own numbers. A support tier with low conversion but high retention may be working as intended for a small, committed audience. A support tier with high initial conversion and high churn may mean buyers misunderstood what they were paying for. Neither pattern tells you whether the underlying product is good.

The studio's own experience is a single data point, not a benchmark. Treat it as a worked example of framing, not as evidence that a five-times-price support tier will work for your app.

Topics covered only in the full episode

A few threads from the conversation are not developed in this guide. They include Allen's work designing the Microsoft Courier tablet, a device that never shipped; the influence of the early Macintosh on how he thinks about computers as creative tools; and his suggestion to look at the artist John Baldessari and the musician Brian Eno as models for creative thinking. Readers who want those threads can follow the full episode link below.

Frequently asked questions

What is a patron plan in an app subscription?

A patron plan is a subscription tier whose main purpose is to fund the studio's ongoing work rather than to unlock additional features. In the Not Boring Software example, the tier was priced at five times the standard tier and included essentially nothing extra beyond a physical gift and the knowledge that the buyer was supporting the studio. Early subscribers also had their price locked in permanently, and each new app (one per year) was included automatically.

What does it mean for an app to ship as a complete product?

It means the app is released as a finished tool rather than as the first version of an ever-expanding roadmap. The studio's framing is that the app does its job well and will not be changed on the user. That constraint pushes the team to make new apps instead of endlessly iterating on old ones.

Why would an app play a dozen different versions of the same button click?

Variation keeps repeated sounds from becoming grating. The technique comes from game audio, where footsteps and punches need to repeat without feeling mechanical. In the studio's apps, each tap plays one of a dozen slightly different versions of the same click, so no button sounds exactly the same twice.

What is 'Super Raw' in the Not Boring Camera app?

It is the studio's name for working directly with raw sensor data instead of relying on Apple's computational photography pipeline. That pipeline includes multi-frame composites, noise reduction, and HDR tone mapping. The studio applies film-inspired LUTs in real time and treats grain and blur as creative choices rather than defects.