Hi Hank,

>>- How far along the beta/stable are mobile clients ?
>It's all on the roadmap. The order of things from the current point is likely to be a little different, but pretty much in the order that's there.

>>- Are all languages and tables supported fully on mobile, including cursor, xBase and SQL support ?
>Mobile has cursor support.

in Phonegap there is support for a JS abstraction also called cursor - which is different from a dbf/table based implementation. Any specifics in forum discussions ?

>Lianja tables are automatically pulled into cursors on the client.
>Virtual Tables ("views" against remote sql servers) will be available in 1.3 or 1.2

>The browser mobile client (standalone or phonegap wrapped) uses JS, as that's what is in browsers. On the CloudServer, at present LVFP and JS are supported; PHP and Python are on the roadmap. Native apps have been announced as running VFP, but I would not be surprised to see JS there also.
>
>>- Can local data be encrypted and/or hidden from device thieves or black hat apps?
>
>Local data isn't stored on the device at this point (that's in the roadmap also, for the native mobile apps; I've read that it may show up in browser mobile/phonegap apps, but it's not on the roadmap.

did try to get a picture, excerpted:
Lianja Android Native Mobile 1.0 Release
Expected release date Q3 2014

Native Android Apps. Developers build and test apps using the Lianja App Builder on the desktop and "Deploy" the app as a Native Android App. This will contain a full Lianja/VFP implementation that runs native on Android devices so custom sections and gadgets will run native using the Android UI.
Synchronization of data from offline to online (Lianja Cloud Server) mode in the Lianja Mobile Client.
Mobile App packager to prepare Apps for submitting to Google Play.

the embolded part is the one I am interested in, but might be at odds with

Lianja HTML5 JavaScript Mobile Client

The Lianja Mobile Client is a pure HTML5 JavaScript client that runs Apps developed in the Lianja App Builder using best practices on mobile devices. The Lianja Mobile Client is implemented as a responsive UI and will automatically adjust its appearance on iPhone, iPad, Android Phones and Android Tablets. It incorporates the PhoneGap JavaScript APIs and can be packaged up as a self contained App using the Adobe PhoneGap Build Service that can be submitted to the Apple App Store or Google Play.

and/but

The way I see it is that an application should be broken down into functional categories. Certain categories will be required to run in the main data center / office. Web can provide a subset of the application functionality but not all. Tablet/mobile again can provide a subset of the web functionality but not all.

As you know I want local data storage, if only as cache but possibly for partially disconnected road warrior scenarios, where the promised replication would be wonderful. Is this native android client (exp. Q3/14) currently available to beta-testers ? might clear up some of the lag/incosistencies in the docs, as implemeted functionality is preferred over doc'ed but missing one ;-)

Snowden gave some of my opinions more weight, but without showing such capability I must stay in Java-land for the next months, excerpting some vfp touchups with existing apps ;-)

tia

thomas