Splicer Blog

Accelerating Native Mobility

Breakthrough Mobile Database Server

At Splicer, we discovered that most client-server code can be derived from a data model definition, which we can derive from your existing server artifacts. Our code generators automate Android, IOS, and server coding to provide tremendous cost savings, and represent a new type of “low code” product.

Instead of relying upon a traditional sync server to update your mobile database, use Splicer’s model mapping to both control, and synchronize your mobile data. With the Splicer GUI, you select components of your server data model that you need in your client model, and then generate client DAOs. This is an easy and efficient way to correlate your client data to your server model, and allows you to deliver the thinnest clients possible. Once this model map has been established, both fetching and synchronization of complex client data objects are trivial. You can then cache the data locally using native client containers, or easily integrate a mobile database like Realm.io.

Unlike a mobile database sync server that cannot correlate a client object database with an RDBMS, we operate at a higher level of abstraction. We use Splicer to correlate our mobile data model with our server’s. With the Splicer GUI, we select components of the server model needed in our client model, and then request those complex objects via native code.

Splicer is a general-purpose “mobile database server” — supporting IOS as well as Android. Additionally, all data objects are typesafe, which allows various compilers to enforce a system data model. And with Splicer, we automate only what is necessary — allowing you to code natively as you’re already accustomed. It is even more useful when integrating sets of mobile apps to your backend — providing the link between the client pojos and your server database or model.

In a sense, Splicer acts as a turnkey “bridge” that maps typesafe Android and IOS objects with structured backend data from relational databases like MySql, Postgres, SQLServer, and Oracle. You can then easily modify that relationship via our “bridge” GUI. We also plan to support NoSQL databases as well, so drop us a line and we will let you know of our progress on that front.