Article URL: https://github.com/schlae/IBM_MCGA Comments URL: https://news.ycombinator.com/item?id=48695363 Points: 10 # Comments: 2
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
A developer building a paid desktop app found that Stripe handles payments but provides no licensing features, prompting a search for third-party solutions. Platforms like Paddle, Gumroad, and Lemon Squeezy were evaluated but rejected due to higher fees, reliance on online-only license validation, and vendor lock-in risks. The core technical concern was that server-dependent license checks fail paying customers who are offline and can be bypassed by blocking network access, whereas cryptographic local verification was needed. The developer's caution proved warranted when Paddle announced it was winding down Paddle Classic — the version that included built-in license keys and a Mac SDK — leaving developers on that platform forced to migrate. This led the founder to build Keylight, an in-house licensing SDK designed for offline-capable, cryptographically verifiable license keys that remain independent of any third-party platform.
Developers often delay switching licensing platforms out of fear that existing customers will lose access after the transition. The key to a safe migration is importing customers' original license keys as active records, so the new system recognizes them without requiring reactivation. Running the old and new systems in parallel for a few weeks allows customers to gradually move to updated builds without any forced cutover. Keylight, a licensing platform, supports this approach by storing imported keys exactly as they are, meaning validation checks return the same results as for newly issued keys. The method avoids support ticket surges by ensuring no keys are invalidated at any point during the migration process.
Choosing between a one-time and a subscription pricing model is an early and consequential decision for indie app developers. A perpetual license, where customers pay once and own that version indefinitely, suits locally run tools with low per-user server costs, such as desktop utilities or developer tools. Subscription licensing makes more sense when an app involves ongoing infrastructure costs, hosted APIs, or continuous content updates, as recurring expenses should be matched by recurring revenue. The key distinction lies in what the customer is actually purchasing — ownership of a product versus ongoing access to a service. Developers are advised to let the nature of their product guide the pricing model rather than defaulting to whichever approach appears more financially attractive on paper.
Indie developers launching paid apps typically choose between three platforms — Stripe, Paddle, and Lemon Squeezy — but the choice hinges on a fundamental legal distinction: payment processor versus merchant of record. Stripe, the cheapest at roughly 2.9% plus $0.30 per transaction, makes the developer the legal seller, meaning sales tax and VAT compliance are their own responsibility. Paddle and Lemon Squeezy act as merchants of record, charging around 5% or more but handling global tax collection and remittance on the developer's behalf. Stripe gives developers full ownership of customer data, while Paddle and Lemon Squeezy retain the customer relationship under their own terms, making future migrations more complex. Notably, none of the three natively support offline cryptographic license keys for desktop apps, meaning licensing remains a separate layer regardless of which payment platform is chosen.
Discussion (0)
Log in to join the discussion and vote.
Log in