Also at what is the frameworks strategie on locking doing transactions in the database.
Also at what is the frameworks strategie on locking doing transactions in the database.
The pricing is per project (per app). You pay $250, and you get one year of updates and then use it forever.
The license is a Perpetual Fallback License. When you stop paying for a subscription, you will still be able to keep and use the latest version of Avo at the point in time when the subscription ended but you will loose the ability to update to a newer version.
Regarding locking and doing transactions, it does not support that, but that's a very good idea and not that difficult to add in the near-future. Ideally to let the developer specify what kind of locking strategies to use.
I added this topic to keep track of. https://github.com/avo-hq/avo/discussions/982
I think you're over-complicating the pricing. Why not just say it's $250 per project per year? You can still keep the fallback option and explain it in your FAQ. It would be more immediately understandable this way imo.
If an app has a longer lifetime than a year, and I hope it does, then you'd have to resume the subscription to get the updates (bugs and security). It's the way the perpetual-fallback license works. There are plenty of products (table plus, jumpstart rails) and large companies (jetbrains) that practice this model. I wish there was an easier way of shipping those updates without a subscription.
Customers who get value out of your product will want to pay and keep paying and be sure they’re not going to miss important updates if they forget to renew in a year. These are the customers to focus on imo.
People are happy to pay subscriptions for software they get continuing value from. There’s no need to reinvent the wheel on this.
Maybe this is an esoteric case, but I have a project from a previously operating business (TechStars Boston 2010). Every now and then I think I'd like to take a nice stroll down memory lane. And then I remember I have one component that was an annual SaaS that I no longer have an expensive license for, so the thing won't boot. And I don't have the wherewithal to invest the time to replace it. It's extremely unlikely I'll ever adopt something similar in future projects, personal or otherwise.
I get "continuing value" from all sorts of things I'd never want a subscription for. If you're confident in your product's ability to innovate and continue to add value, you shouldn't worry about attrition. Providing a fallback option makes it clear to me that you have that confidence and that makes a huge difference during a purchase decision.
There are developers and agencies that buy Avo, build something for a customer and then transfer the license to them. The customer might not even know that the agency bought something. They might not want to pay something ongoing.
Yes, one could make the case that "hey, you pay hosting ongoing after the project is delivered, why not pay the admin framework?" and that's fair, but I just don't know if we're at that point yet. I'd love it if Avo would bring us closer to that point.
Looking at jumpstart rails, they seem to be doing exactly what I’m suggesting. It’s a simple per project per year price, but then in their FAQ they explain that you stop getting updates if you stop paying.
On the agencies point, yeah I think it’s normal for agencies to sign a client up for a bunch of services they need to build the project. You’ll just be one more on the list.
Also, you do make a point regarding agencies "sign a client up for a bunch of services". I'll try and experiment with that. Thanks for the nudge!
At first glance, it’s just a yearly subscription per project. Simple and standard. Everyone understands it.
If I’m concerned about what happens if I stop paying for jumpstart, I can find that information, but it’s not emphasized at the top like it is on your pricing page. And the yearly subscription is the default, not something I have to opt into again every year.
Most customers are just going to sign up for a yearly subscription and never look back. It’s better for the customer and for jumpstart.
"It’s better for the customer and for jumpstart." It's true.