My answer above, referring to "Strategy 1", applies specifically to the creation of an application, which is both exported as a native application (to a .apk) and deployed to a Tersus Server which serves the native application's Service calls which are automatically sent to the defined server.
There's also "Strategy 2" in which you split up the application to 2 parts, one containing the client side modelling and exported native, and the other containing the Services and deployed to the server, but this is more cumbersome to model & test, and provides little added value.
If both strategies do not answer your question, then I guess you'll need to provide more details regarding your specific requirements.
Regards,
David
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign
