Eliminate expensive Appian licenses using the the first low code, enterprise mobile stack. Use this stack to expose BPM semantics as web forms and type-safe data structures for native mobile apps. Lets take a look at how this extension works.
The most difficult piece for enterprise mobile development is integrating sets of clients to your servers. So let’s leverage RMAD tools to extend server data structures to your native clients. This technique provides mind-blowing development efficiency — and allows you to affordably host your own native solutions instead of getting locked into other proprietary “low code” systems.
Gartner says that demand for enterprise mobile apps will drastically outstrip our ability to deliver by 5x: http://www.gartner.com/newsroom/id/3076817
Its time to re-think how we are engineering these enterprise mobile systems. Fortunately in our beta testing, we learned Splicer drastically increases enterprise mobile development productivity without requiring developers to learn new development tools.
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.
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.
Instead of integrating Android with SQLite, use Splicer instead to get direct access to your server model. Splicer connects your relational database to mobile clients by generating both Android and IOS data objects from your existing schema. These client “DAO” objects become the app’s interface to your backend. During run-time, Splicer extracts data objects directly from your database or your server-side model layer and delivers them across the network to your mobile apps.
Android MVC Design
I found a good reference for Android MVC design (“Programming Android”) which states that the Adapters loosely serve as the Controller. For the Model layer, we propose that the data model should be flexible and ideally controlled from a single file. Hence we generate the pojos for the smartphones from the model descriptor in such a way that the model code is independent, and does not overlap with manually-written code; our model is “orthogonal” to controller code such that our code generators do not over-write any programmer-written code.
Today’s enterprise mobile systems require a client-server architecture where the system model is adaptable or malleable. Splicer is designed for modifying client-server models with ease. Our implementation is explored in our other blog posts, but I thought a bit of background theory might be of interest to some people.