Example transcript — this is what Swiftyscribe produces
Shipping Weekly artwork

Shipping Weekly

Notes on a Slow Launch — What I Learned Shipping an App With Zero Servers

28:19
Format: solo
Published: April 3, 2026
Transcribe your own podcast with Swiftyscribe

AI Summary

A solo reflection on the last eighteen months of building a consumer app that runs entirely on the user's device. Covers the pricing mistake that nearly sunk it, the marketing problem that's impossible to solve when your product doesn't phone home, and the surprising payoff — a level of product simplicity that the cloud-first competition can't match without rewriting everything.

Chapters

  1. 00:00

    1. The premise

    Why 'zero servers' started as an engineering choice and became the product's core promise. The accidental moat.

  2. 06:42

    2. The pricing mistake

    Tried to charge like a SaaS. Learned that customers who value privacy also want to pay once and never think about it again. Moved to a lifetime tier. Revenue went up.

  3. 14:18

    3. Marketing without telemetry

    When you can't see how users use your product, what do you do? Lean on reviews, handwritten support emails, and the willingness to ship instinctively — the old craftsman's model.

  4. 21:09

    4. The simplicity dividend

    No server means no outage page, no scaling anxiety, no security review. Every feature request is a feature question, not an infrastructure question.

Notable quotes

“The day I stopped worrying about server costs was the day the app got better, because I could ship things I'd been afraid would load-spike us into bankruptcy.”

Host•02:34

“A one-time purchase for a private tool isn't a business model. It's a handshake. The customer trusts the software to keep running; you trust the customer to tell their friends.”

Host•11:27

“I have no idea how many people use the filler-removal feature. I know, because I built a product that doesn't phone home to tell me. And that's fine — I built it because I wanted it. If nobody uses it, that's also fine.”

Host•18:52

Transcript excerpt

[00:00]
Host:Eighteen months ago I decided to build an app that doesn't have a server. No account, no database in the cloud, no telemetry. Just a binary that runs on your device and does a thing. Today I want to talk about what that actually felt like to build and, more importantly, to sell.
[00:24]
Host:The first thing you learn is that 'no server' is a weird thing to say out loud. Most people hear it and assume you mean the app is broken, or offline-first in the way a note-taking app is offline-first where eventually it syncs to someone's cloud. But I mean it literally. The binary runs. The data stays. That's the whole story.
[00:58]
Host:The engineering was the easy part. Apple has spent a decade making on-device AI viable, and by the time I started, all the hard research was done. I could pull down a pre-trained speech model, wire it to an audio pipeline, and ship. It took two weeks to get the first transcript out. The eighteen months since then have been marketing, pricing, and learning how to talk about a product that deliberately doesn't do the things the market expects.
[01:42]
Host:Let me start with what I got wrong about pricing.

This is an excerpt. Full transcripts run as long as the episode itself. To transcribe the real podcasts you listen to — end-to-end, searchable, private — install Swiftyscribe on your iPhone, iPad, or Mac.

People & organizations mentioned

Apple

Your transcripts, on your device

Every transcript Swiftyscribe makes runs entirely on your iPhone, iPad, Mac, or Apple Vision Pro. No accounts, no servers, no upload.

Install Swiftyscribe

See more example transcripts →