I go a bit the other way. I can't stand the constant turmoil in an app's UI in the name of whatever new UX thing is being experimented with. I'd much rather have big updates in one go that I can evaluate on their own merit. That doesn't totally preclude a subscription model, but it is how most subscription services work. Lately, I've been forced to update mobile apps just to connect to whatever backing service. It's obnoxious because even with auto-updates enabled, it may not have updated yet. And now I need to wait for the update or just not use it if in an area with limited cellular coverage.
I appreciate recurring revenue helps businesses, but that's true of all businesses. Software just has the lock-in, generally, to enforce it. If this is the only way to pay for stuff, though, I think JetBrains has the best model I've seen. I pay a subscription and can update software on my own schedule. If I decide to stop, I have a fallback perpetual use license.
I think that really depends on the app in question. Often these apps have a free version where you can evaluate if you think they'll cause UX Turmoil, and then support the ones that are reasonable.
If anything, I find my subscription money helps to support smaller developers and developer teams that tend to be better about not being all about meteoric growth and trend-chasing and focus more on just delivering a quality product.
I appreciate recurring revenue helps businesses, but that's true of all businesses. Software just has the lock-in, generally, to enforce it. If this is the only way to pay for stuff, though, I think JetBrains has the best model I've seen. I pay a subscription and can update software on my own schedule. If I decide to stop, I have a fallback perpetual use license.