zlacker

>>levmis+(OP)
Intriguing.

But - the first thing I want to know it "how much" and then shortly after that I want to know "can I run it myself".

>>dmje+Mj4
This should be the first and most important question anyone asks when trying a new product/service. If I don't understant the business model and how much I could be locked-in, I don't even bother wasting 1 minute on the product (I might tray that to get inspiration, but I probably wouldn't use that for anything serious).

>>tigrof+mn4
> If I don't understant the business model and how much I could be locked-in, I don't even bother wasting 1 minute on the product

Personally I do it the other way around, first I try it out and see if it's useful, then I'd figure out if I'm willing to accept the tradeoffs of pricing/lock-in.

If you do it the way you suggest, wouldn't that mean you can't actually understand if the business model is fine because of the benefits you get? Seems backwards to me.

>>embedd+KA4
100% agree. Why even question the business model if that's not a product that I would use. First should be "Can I use it?"(meaning does it run on my devices etc.), then "Do I find it useful?" before anything else.