Original Summary

I've shipped 3 paid Mac apps, and the thing nobody tells you is how much stuff surrounds the actual app. So I mapped out my whole setup in one pic. Here's what each piece does: The Mac app Swift 6 + SwiftUI A licence window, with the key saved in Keychain Settings: open at login, updates, licence, about A proper menu bar and main menu (you'd be surprised how many apps skip this) Sparkle for auto-updates Payments Creem or Polar as merchant of record, so they deal with sales tax and VAT, not you Licence keys with device limits Refunds and disputes handled through their webhooks Website Next.js, deployed on Vercel Landing, pricing, FAQ, blog, changelog, terms/privacy/refunds SEO basics: canonical URLs, sitemap, structured data, plus llms.txt for AI search Emails (Resend) Receipt with the licence key Lost-key recovery, 'cause people will lose it Waitlist and release notes Shipping One script builds, signs, notarizes, and packages the DMG A signed appcast so Sparkle can push updates The same flow works in GitHub Actions AI tooling 13 "skills" (step-by-step recipes) so Claude Code, Cursor, or Codex can add a screen, a setting, or a payment provider without wrecking stuff Checks that run after every change and tell the agent when it broke something Honestly, notarization and licensing ate way more of my time than the actual features did. Curious what everyone else's stack looks like. Anything you'd add or do differently?   submitted by   /u/Own-Culture3567 [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/9/27 03:16:22