I’m a bit confused with the Pricing page. Does the Chrome extension limit of 30 minutes per month in the free plan mean that completely local use on one’s computer is restricted by time? How is this tracked?
I was wondering that too. Paying for cloud usage is entirely reasonable, but there is no reason why there should be limits on what I do locally. Demanding a monthly subscription for local software is grubby—wouldn’t consider that.
The reason for having limitations for local automations is a business one, not a technical one. I like the idea of scaling the price based on how much value Browserflow provides (if it saves someone hours of work, paying less than 20 bucks should be a no-brainer) so that's why there are runtime limits by plan.
I’d be happy to pay $19 once, just as I’ve purchased my other apps. I’d even pay twice that, and I would also consider it fair to charge for upgrades.
But I believe in paying for value, and the value of the software should be covered by a one-time payment, as is the case with purchasing any other product. Continuing to demand payment without providing additional value—a service, computing resources—is not reasonable or appropriate, and I can’t support that business model.
That's totally fine. I chose this model so that I can create a sustainable income stream to continually support and improve Browserflow, but you don't have to agree.
FWIW, I did consider the one-time payment and upgrade model, but it's not possible for Chrome extensions because the distribution is controlled by Google and all users are automatically upgraded to the latest version.
Thanks a lot for the prompt reply and clarification. I agree with the sentiments in the other sibling comments. At this point, this tool is not for me.
