I think it could be, depending on the application.
Some examples of companies using this model are JetBrains with their IDEs and Adobe with their PhotoShop, etc. suites. They both used to sell as one-time-purchase with upgrades each year, but they now provide a subscription model where you pay a yearly/monthly fee for access to a given set of applications. I know a lot of people were annyoed by the switch to subscription, but it may be more acceptable now.
Note that both JetBrains and Adobe have large suites of very feature-rich applications, and they have been around for decades. Not sure how easy it is to do the same with a single new application, but as customers are getting more and more used to the subscription model, it might work quite well.
Personally, I wouldn’t mind the subscription model as long as the subscription was optional, meaning that I could by version X and stick with that without ever upgrading (if I didn’t want to).
If you plan to do integrations with third-party cloud storage for back-up/sync etc, you could do subscriptions for those, so one could buy the app itself for a one-time fee, then pay a yearly/monthly subscription for the integrations, in a sort of “plug-in” approach (even though the integrations do not technically need to be plug-ins).
I know there are some SEO tools that also have a subscription-model, where the app is local but you pay for access to the dataset, which is updated regularly.
BTW: A nice thing about the JetBrains subscription is that you can pay a fixed amount per year to get access to all their development tools, which is very useful for a multi-platform developer, such as me. I have bought JetBrains licenses in the past, but never bothered to upgrade them, but now that they are subscription-based, it’s cheaper to just buy the whole pack. It’s also nice that they give discounts for the 2nd and 3rd year.