> I see this comment or some variation of it every time a new product is shared here that has such a model.
I observe something similar, but we seem to have drawn different conclusions.
> What I rarely if ever see is a proposal for how the developer should make money instead of a subscription.
At the risk of sounding trite, I think people who find subscriptions unpalatable would be happy with anything that isn't a subscription. These could be offered in parallel, so subscription-averse consumers have an alternative to evaluate.
A one-off payment is the obvious and most simple choice -- wrap some limits or caveats around data / transit usage if needed. Freemium option may work in some cases (I think there's sufficient successful examples to validate this as viable). (Only) enterprise users pay. Tier the offerings to protect yourself from the heavy eaters.
I don't think expressing fatigue at the relentlessness of subscription-ONLY services is invalid.