Splicer Blog

Data Model Automation

Android MySQL Bridge

If you’re trying to hookup Android to MySQL, you’ve come to the right place. We take your database schema or other server model artifacts and generate both Android and IOS objects. These objects then become the client’s interface to your backend — thereby extending the object-relational paradigm to the mobile coder. This is all possible via our open source server that forms a “bridge” between your clients and your server model or database. The server also comes with a GUI that allows you to manage the relationship between your client models and your server model.

Here at Splicer, we realized that as we begin to roll out sets of mobile apps, the fundamental complication we face is the ability to map various client models to a server model. This may not be obvious at first, but once it is fixed, you will find that mobile development is a breeze. And having the ability to graphically view these model relationships and what data is exposed to your clients is a big help.

How does it work?
Our system derives a server model from your Oracle, PostgreSQL, or MySQL database schema combined with other model artifacts. It then applies this model to our open source server. As you pick elements to publish with our Mapper GUI, Splicer first generates associated DAOs for Android and IOS, and then serves data to them. You can then tweak the database queries as needed, or re-purpose existing server code.

Why is it different?
With Splicer, the client’s data objects are typesafe and guaranteed to correlate to your server model. These client DAOs allow the mobile developer to access the server’s database just like a server-side ORM does. When you change your model, compilers show where your client code breaks due to model changes. If you have multiple types of mobile apps, this type of Model Management will save your sanity.

GUI visualizes the bridge between client objects and structured data
•   Server coding optional
•   Visually control the relationship between client object databases and the backend
•   Re-use server model objects to develop sets of apps
•   Audit data structure details to minimize payloads
•   Compatible with the mobile databases such as Realm
•   Supports synchronization