Just Pay the Subscription

Overall sentiment on app subscriptions

  • Many commenters dislike the spread of subscriptions, especially for simple or “finished” apps (calculators, timers, basic fitness trackers).
  • Some are comfortable with subscriptions and cite multiple services they’re happy to pay for; they argue not all subscriptions are predatory.
  • There’s broad agreement that cloud-backed apps and services with real ongoing costs (servers, APIs, heavy maintenance) are more justifiably subscription-based.

Ownership vs. access and longevity

  • Strong nostalgia for “owning” software: buying a CD/box once and running it 10–20 years later, even offline.
  • Others argue “ownership” is increasingly meaningless for mobile apps, which depend on constant updates and platform compatibility.
  • Several want the guarantee that if a company shuts down or stops caring, the version they paid for still runs. Current subscription/app-store models often break this.

Pricing, value, and predation

  • Complaints that many mobile subscriptions are overpriced relative to how rarely an app is used; people compare to streaming services they use daily.
  • Subscriptions are viewed as structurally designed to extract payment for non-use, exploiting forgetfulness and cancellation friction (the “gym membership” model).
  • Common pattern noted: launch cheap or at a loss, then “enshittify” the product while relying on locked-in or inattentive subscribers.
  • Users resent being pushed into subscriptions where a one-time payment or very low-cost subscription (cents/month) would suffice.

Alternatives: one-time purchase, upgrades, and open source

  • Many advocate classic one-time purchases with optional paid upgrades (e.g., a year of updates, then keep using that version indefinitely).
  • Some say upgrade pricing encourages focusing on features users truly value; others note it can incentivize “shiny” features over maintenance.
  • Open source is raised as a contrasting model: indefinite reuse, transparency, and donations/“subscriptions” as voluntary support rather than lock-in.

Platform and ecosystem constraints

  • Mobile platforms (Apple/Google) are blamed for poor backward compatibility and store rules that make non-subscription models harder.
  • Frequent OS and API changes create real ongoing costs, making pure one-time pricing less viable for many indie developers.

Data, lock-in, and UX concerns

  • Strong warnings against using subscriptions for tools that hold important personal data, due to poor export options and risk of losing access.
  • People are frustrated by mandatory accounts, trials that auto-convert, dark patterns around cancellation, and constant, unwanted UI/feature changes.