Use your publication's custom domain (or yourname.substack.com) as the start URL. Readers sign in with the email-link login, which works in a WebView; paid posts unlock as usual because the subscription is sold on the web, not in the app. Keep only your domain and Substack's sign-in pages inside the app and open other links outside.
Logging in
Substack signs readers in with an emailed link. Tapping that link in the mail app opens it in the browser, not your app — so the browser is logged in and the app isn't. Better: use the one-time code option if offered, or ask readers to sign in from inside the app and copy the link into it. Test this flow first; it's the main friction for newsletter apps.
Paid subscriptions and Play billing
Paid newsletters are digital content. Selling subscriptions inside an Android app distributed through Play generally falls under Google Play Billing rules. Letting existing subscribers sign in and read is different from offering a purchase button in the app. Read payments in URL apps and Google's current policy; for many writers, sharing the APK directly with readers avoids the question.
Use a custom domain
With your own domain the app survives a move from Substack to Ghost or Beehiiv — just point the domain elsewhere. That's worth more than any other setting here.
What makes it worth installing
- Native push when a new post goes out — readers who mute email still see it.
- Faster access to the archive than searching the inbox.
- Comments and chat a tap away.
FAQ
Is it allowed to make an app of my Substack?
It's your publication; brand the app as yours, not as Substack. Check Substack's terms for current rules on custom apps.
Do paywalled posts work in the app?
Yes, once the reader signs in, as on the web.