I'm always curious why companies like this one choose to charge for their app as a one time fee when, to support the app, they have to subscribe to data feeds which cost money per month. I feel like you have to have a subscription model for that unless the price per month is just so low that, with a small amount of volume, you can easily make up for it. Either way always an interesting write-up. I do find it odd that…
From a purely practical standpoint, it's easier to charge for the app and let Apple do the billing and payment processing, than to set up a system to handle recurring billing (and then you need to deal with cancelations, chargebacks, etc.). I've gone through this thought process for a few side projects, and unless I anticipate really large MRR, it's hard to convince myself to go through the hassle of setting up subsc…
You just plugin the Stripe SDK and set up a Stripe account and it's done. It's not hard. It takes like half a day. You don't have to do any of this manually. If you're a tiny team and you are doing this manually you're doing it wrong. I've never had to worry about chargebacks or cancelations being a problem.