Skip to content
AppDues
Log in
Contact salesSign up

Touch Grass: 40,000 preorders, a $20,000-a-week vision bill, and the retention problem after the spike

Touch Grass locks distracting apps until you photograph real grass. Its builder, Rhys Kentish, posted a rough prototype, watched it spread across several platforms at once, and collected tens of thousands of preorders before the app existed. The launch story is useful less for the virality than for two decisions it exposes: a per-call cloud vision API that scaled with the hook, and a product design that made uninstalling the easiest way out.

The launch sequence, in order

The sequence matters because each step changed the next one. Kentish posted an early prototype to Reddit, spent a couple of months polishing it, then posted again to Hacker News and Reddit one morning. He expected a few hundred downloads over the first weeks; by lunch he thought his analytics were broken. The same day he put the app up for preorder, and roughly 40,000 people later received the App Store notification that it was live. Launch day itself drew something like 50,000 unique active users.

A useful way to read the sequence is as a chain of dependencies rather than a list of wins:

  • A rough prototype tests whether the hook travels before any polish is spent.
  • A preorder page gives a viral post somewhere to land, so traffic converts to a notification instead of a search for a clone.
  • A per-call cloud dependency is cheap at prototype volume and dangerous at hook volume.
  • A product that is easy to uninstall turns a spike into a long tail.

Why the vision bill scaled with the hook

The first version checked each photo with Google's cloud vision API. At the volume Kentish expected, that was a modest prototype decision. At the volume the hook produced, he calculated it would have cost something like $20,000 a week to run. The fix was to rewrite the vision detection natively on device, which he did across three sleepless days, shipping just before launch.

The distinction worth keeping is between a prototype-stage cloud dependency and a launch-stage one. A per-call API is fine while the audience is small and the hook is unproven. Once the hook is proven, the cost grows in step with the very reach that makes the app spread. A pre-launch check is to multiply the per-call cost by the volume the hook could plausibly produce, not by the volume you hope for.

A worked example using the captured figures: 40,000 preorders and a $20,000-a-week cloud vision estimate describe the same hook from two directions. The preorder count is the demand signal; the weekly bill is what that demand would have cost if the detection stayed in the cloud. Neither number is a forecast for another app, but together they show why the rewrite happened before launch rather than after.

A small marketing surface that travelled widely

The marketing surface was unusually small. The website has not changed since launch day: a screen recording and a line of text about reducing screen time. The first Reddit post was an early prototype with no UI polish; it reached the top of r/SideProject in November. A later tweet was a single sentence over a screen recording and reached around 1.5 million impressions, with reporters in the replies and interview requests from TechCrunch and Fast Company, all while the app was still in preorder.

Kentish's timing tip for European developers is to post in the morning: a strong European morning puts the post in front of the US East Coast as it wakes, then the West Coast. The more transferable habit is his one-sentence test. He distils the app into a single sentence, says it to people in real life, and watches their faces before building. For Touch Grass, they chuckled.

The observation that makes this more than luck is that the post performed well on several separate platforms at the same time, which points at the hook rather than at any one channel.

The retention problem the spike hid

The 50,000-user launch hid a design flaw. Touch Grass was easy to uninstall: if you wanted Instagram and it was raining, the first move was to delete the app. There was no simple off switch, which Kentish now calls a product oversight. Charlie Chapman names the result a churn problem, and adds a detail that makes it worse: iOS now asks, at the moment of deletion, whether to cancel the subscription too, and almost everyone says yes.

The rebuild is about staying rather than spiking. Kentish is gamifying the app with eight-bit UI, rewards for hours off the phone, critters that visit a meadow, and guides modelled on the dogs he and his wife dog-sit, with a planned paid feature where your own pet becomes your guide. He describes the growth chart as a very large viral spike followed by a very long tail. He has never run a paid ad and is not trying to recreate the spike; the work is on retention.

A reader-facing checklist for the same situation:

  • Check whether the core action has a graceful off switch, or whether uninstalling is the only exit.
  • Check what the platform asks at deletion time, including subscription cancellation prompts.
  • Separate the spike metric from the retention metric before deciding what to rebuild.
  • Treat a viral moment as a test of the hook, not as a growth plan.

Copycats, character, and the preorder page

Kentish is not sure he would post an unpolished prototype today, because people can copy faster. Chapman pushes back: even a thousand clones the day after a viral post would have had nowhere to land without the preorder page, and the clones would have collected the downloads. His working assumption is that no one is quietly cloning you, and that if someone is, it means you have found traction.

Kentish's answer is that character is the moat, and so is the person. Ideas with character are the hardest to copy. He sees clones every day now, and people on Reddit and Twitter point at them and say he did it first, because they follow him rather than only the app. His framing is that your app is not necessarily the brand; you are your brand.

Frequently asked questions

Why did the cloud vision API become a launch risk?

The first version checked photos with Google's cloud vision API. At prototype volume that was modest; at the volume the hook produced, Kentish calculated it would have cost something like $20,000 a week. The bill scales with the same demand that makes the app spread, so the rewrite to on-device detection happened before launch.

What did the preorder page actually do?

It gave a viral post somewhere to land. Around 40,000 people received the App Store notification that the app was live. Without it, Chapman argues, clones could have collected the downloads while the original had no conversion point.

Why was Touch Grass easy to uninstall?

There was no simple off switch, so deleting the app was the fastest way to get back to a distracting app. Kentish calls that a product oversight. iOS also asks at deletion whether to cancel the subscription, which compounds the churn.

What did Tinder object to in Tender?

Not the name or the swipe gesture, but the word swipe in the App Store listing, which Tinder has trademarked. The listing was changed and the app stayed in the store. The legal letter later became the marketing story on TikTok.