how many years ago did you last use an optical dicsk (cd/dvd/blueray)?

I'm getting more and more requests to demo Avo to developers and teams and I'm not sure what would be the best demo to build. The simplest, more recognizable demo would be the Blog CMS. I could create Posts, that have many comments; Posts belong to categories; I could demo the files feature. But that seems kind of boring and too "simple". Avo could do more The next thing that comes to mind is to demo a sort of AirBnB clone where hosts can add their places and guests can book them. I could showcase the multi-tenancy features of Avo, but that might look quite different from the actual AirBnB website and might not get my message across. I need to mention that it's important I could do the demo live in about 6-9 minutes. Not everyone has the time to stick around for half an hour to see me build an app. So, I'm asking you guys:

Some pointers for a demo: - Adding a 'theme' for appeal - A use-case that shows applicability in custom applications. Ie, why we use Ruby on Rails over an off-the-shelf product Here's my idea. Farm simulator! A user can have Farms. See what vegetables are growing in those farms. See details about those vegetables. Avo cado.

We're still working on the upgrade docs for Avo 3, and we're going back to the drawing board with pricing based on your feedback. We're still going to have the subscription model but we're thinking about adding a one-time payment per app and one subscription for unlimited apps. Which one is more appealing to you? 1️⃣ Higer starting price and a lower yearly subscription 2️⃣ Higher one-time fee per app (per major version) 3️⃣ Unlimited apps subscription #️⃣ Other (I'll leave a reply)

We actually got the lack of option 2 as feedback when introducing AVO to one of our clients...for agencies using AVO for clients this would definitely make sense imho.

I'd love to hear your thoughts too ✌️

What makes sense for you Adrian? (1) sounds good as you up front some of the return rather than spreading it out yearly over which time I guess many apps might come and go and you will loose to natural attrition. The 'indie-hacker' in me would prob love (3) but to be honest for my customers who I might request to purchase Avo licenses for their project, I think they would be happy paying even a high one time fee as Avo can save so much dev time which is generally expensive (though again I guess (1) may be better for Avo here as it gives you some ARR on the yearly "upgrade" fee).

Hi Adrian. I believe that the higher one-time fee per application (per major version) is the type of licensing that companies are used to, for example, when purchasing Microsoft SQL Server.

Thank you all for your input

All that you said is true. For us subscription works well because we know that some funds will flow in every month, but I see the advantages of one time fee for “client work” companies.

And even the “unlimited” subscription for agencies or companies that build a lot of Avo apps per year. Those ones that have more than 50 developers and the bandwidth to take on so many projects

I believe that everyone that’s looking at Avo is trying to find a similar project out there and see what does that project do to finance itsef. I’m sure that in the Ruby world sidekiq is the first that comes to mind

The major difference between these projects is that sidekiq requires little maintenance, has fewer branches, options, and things that can go wrong. Because of that, Avo requires a lot more support work to fix bugs, and bring new features.

That’s why it requires more development and subsequently funds to keep alive.

I think all I want to say is that it’s not a “finished” product. But we still have a lot to bring to the table

So, yeah, let’s keep this conversation going until we find a good match for everyone

Should we create a #jobs channel so folks can post their availability or requests?

Which notation is better for blocks? 1️⃣

-> { evaluate_something }

2️⃣

lambda { evaluate_something }

regular lambda it is

What about

-> do ... end

? 😂

haha. yeah, that one too

let's try it again 😛

Which notation is better for blocks? 1️⃣

-> { evaluate_something }

2️⃣

lambda { evaluate_something }

3️⃣

-> do end

I prefere the block when lambda returns a hash. Looks cleaner than double brackets

Would anyone be interested in a "Upgrade Avo 2 to Avo 3 one-time service"?

what would that mean? someone doing the work for me on my codebase? or a upgraed fee to use avo 3 on my project where I payed for avo 2?

good point!

It would be a one-time service provided by us to upgrade your Avo configuration files from Avo 2 to Avo 3. You give us access to your codebase, we make the necessary adjustments for you to run Avo 3. Fixed fee service with a time limit.

I am interested. Where can we learn more?