Sustain

The GLP-1 companion built around protein, not weight

Visit Website
August 1, 2026 I built a GLP-1 tracker around protein instead of weight. Here's what I got wrong at first.

Sustain came out of a structured market research pass evaluating solo-buildable app ideas against real App Store data and competitor teardowns. A GLP-1 companion app ranked highest: fast-growing user base, high willingness to pay since people are already spending $200 to $1,000 a month on the medication itself, and every existing tracker built around weight instead of what these patient communities actually worry about most, losing muscle instead of fat.

Built solo, mostly with AI coding tools, SwiftUI and SwiftData, no third-party dependencies until billing and account sync forced two: RevenueCat and Supabase. The core feature is a camera-based protein estimate, point it at a plate, get a grams estimate in a few seconds instead of weighing food.

Here's the part worth being honest about. My first attempt at marketing this was a Reddit post pitching the "your medication dose affects your protein needs" angle, and a user tore it apart, said I was assuming people are idiots for not already knowing that. She wasn't wrong that the logic is obvious, what she was actually reacting to was the post reading like a thin excuse for a plug. I rewrote the messaging around effort reduction instead, the photo estimate, an automated weekly recap, rather than a correlation nobody needed explained to them.

Just shipped a 2.0: mandatory Sign in with Apple plus real account sync, replacing what used to be a fully local, no-account app. That was a real tradeoff, some users specifically liked that nothing left their device, but losing all your data on a phone switch with no way to recover it was a bigger problem in practice.

Free for manual logging. Subscription unlocks the AI estimate and full history. Genuinely curious how other people here think about the local-only versus account-required tradeoff, and whether you've had a piece of user feedback that stung at first but was actually right.

5 Comments

  1. 1

    The account tradeoff is interesting because both sides are really forms of trust.

    Keeping data local asks users to trust you with less. Sync asks them to trust that their history won't disappear when something happens to the device.

    Which one matters more probably only becomes obvious once you see what users consider more costly to lose: privacy or continuity.

    1. 1

      That's a sharp way to put it, trust in different directions. What tipped it for us wasn't the abstract case though, it was concrete: a friend testing the app switched phones and lost everything. There was no account system at all, not even auth, just local storage. So it wasn't really "sync vs. no sync," it was "any continuity vs. none."

      That said, the privacy side of the tradeoff was real too, not just marketing. "Nothing ever leaves your device" was a genuinely clean pitch and some users cared about it specifically. We didn't get to keep both.

      Curious if you've run into this on something you've built, and which way it went.

      1. 1

        I have, and the fact that you had to give up something users genuinely valued is actually the part that caught my attention.

        I'd rather not reduce my perspective to a quick comment here, though. I'd be interested in continuing the conversation by email if you're open to it. What's the best email to reach you on?

        1. 1

          support (at) hearthlyapps (dot) com — works well, happy to keep going there.

          1. 1

            Thanks! I’ve just sent it over.

            Looking forward to hearing your thoughts whenever you have a chance.

About

Sustain came out of a structured market research process evaluating solo-buildable app ideas against real App Store data and competitor analysis. A GLP-1 companion app ranked highest: a fast-growing user base, high willi