I told Barry people would be confused, when I saw it this morning. <s>

Here's the over-arching principle: Annual Subscription vs. One-time Purchase.

Looking at the Standard edition: you can choose to pay $695/yr and get all upgrades and priority support. Or you can pay $495, one-time, but only get refreshes for the current "point" version, and then pay $395 when you decide to upgrade to a "point" version. 1.0 is one point version. 1.1 will be another point version. The same "Annual" vs "One-time and then Upgrade" options exists for each product offering.

The second part to look at is what do you want to distribute.

There are 3 broad paths to take, depending on your situation.

1) The Pro Version: you have unlimited desktop application only runtime distribution.

2) The Cloud Server: with the Standard (or Pro) editions, you can serve the same desktop app as a browser app, as a mobile browser app (the kind of thing embedded in a webview, like PhoneGap does -- although that is all done for you); or you can deliver native iOS and native Android apps (from the same desktop app UI, but I'll bet you end up tweaking the desktop app to make it work the way you want on lower-rez devices -- we'll see on that one). If you are doing volume, you would probably want the Lianja SQL Server (which they are practically giving away). The Cloud server is for one server, but you can have as many cpu's and as many cores in each cpu as you can afford. Likewise with the Lianja SQL Server, which in Recital form is already serving thousands of users in one installation.

3) The ISV Subscription allows you to deploy apps you are selling for which you own the sourcecode (and meet whatever other ISV requirements there will be) in whatever way you want in as many places as you want. It includes 3 dev licenses (and if you have more developers, you get them each a Standard Edition license).

Finally, there is the Team Edition. This is meant for SMB's who might use your application, or write their own, or a mix of the two. They get a built in cloud server, and can share apps across their network, and with an IP address to get to the box on which the app is running (a desktop), can access the same apps on web mobile or web desktop. Given that the Lianja way of building apps is to break it into small parts, there are many situations where you could provide the core app, and let the users add supplementary apps that are then shared. That's the way it has been in VFP: my consulting clients have included a PhD Chemist who was owner and president of an electro-plating company (did or does a lot of the Harley plating); a nuclear engineer who is current constructing two nuclear power plants -- and still writing his own little VFP apps to help manage the process; and a forester who manages (of course) forests. They didn't want me to write their apps: they have more knowledge of what's needed than I will ever have (20 to 40 years experience in all cases). They needed the write tools, and occasional consultation. Lianja makes that possible, and even easier to do than in VFP.

hth,

Hank

>http://www.lianja.com/resources/pricing
>
>Anyone else confused?