Post
by Janschenkel » Tue Jun 14, 2011 8:18 pm
Even with generic ODBC support, you'd still need a specific Android-compatible driver for the back-end database.
There is definite value in an SQLite driver on mobile platforms, but those mobile apps shouldn't connect to remote databases on a server directly. Remember that for most commercial database management systems, you pay per connection. Mobile apps may not be using these connections in an optimal way, as their network may drop, or the user may switch to another app, etc.
A better architecture (also from a security point of view) is to expose your business logic as HTTP(S) web services. This avoids version problems as well (think of an outdated version of the mobile app, unaware of database schema changes until it is updated to a more recent version. With a clear API for remote applications, be they mobile or desktop apps, you have a solid, scalable n-tier solution within reach.
Such n-tier applications can be built with LiveCode - both the front-end and the back-end. And with technology-agonistic web services, you can built your web services using .NET or Java, if a LiveCode Server solution isn't achievable.
Jan Schenkel.