Providing automated architecture as a service, Splicer converts native enterprise stacks into a low code, rapid mobile app and web development platform. Splicer’s data model automation mechanism works in conjunction with various stable, open source java server technologies and mobile app development tools. This powerful combination enhances open source, enterprise mobile stacks — including high-performance, java servers (J2EE) running on the Play Framework or Spring Boot. Moreover, our development system supports heterogeneous web and native mobile clients for a comprehensive, cross-platform development solution.
Splicer’s data model automation allows us to easily map client models to server models. We create our client models in the CAM GUI, and then use our data model automation to generate the client and server models. This keeps the models in sync. These maps essentially define a view into the database. You can think of these views as “perspectives” that layout the screen flows in our mobile apps.
Use Splicer to connect Realm Object Server to a Relational Database/RDBMS. Splicer can deliver data from relational databases to mobile apps through Realm Mobile Platform.
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.
Leverage our RMAD tools to expand your Spring Boot capabilities into full-stack, native mobility. A difficult piece for enterprise mobility 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.
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.