Announcing our free Enterprise low code solution! This tool allows you to generate an android SDK that correlates to the data structures in your relational database. It includes a server model that you can deploy to any JPA-compliant ORM like Hibernate, along with web and Android forms. With it, you can apply low code efficiencies to open source, java server stacks combined with native mobile clients.

Slash mobile app development costs by using the first low code, enterprise mobile stack to better control your client-server data model. By exposing the server model directly to your clients, Splicer automates tedious client-server coding, and eliminates expensive coding costs that typically run over $250K per client. Also, some estimate client-server integration accounts for 80% of mobile app development cost.

Use the first low code, enterprise mobile stack for application development — including B2E (Business to Employee) apps. Our innovative, open source platform is possible because of two novel concepts: Model Maps and Data Model Automation.

I’ve been talking to lots of people in the developer market lately. There is just not enough native mobile architects and developers to go around. The kind of tools we need to fix this are not simply better UI design tools, etc. To solve the developer shortage, we need a quantum leap forward in the tools themselves. The quantum leap I’m talking about are tools that automate to replace coding that we used to do by hand. Think of it as a type of robot that replaces developers. That is what Splicer does.

With Splicer, code your mobile clients natively without javascript. Turns out, you can actually code more productively in a native environment — provided you have the right tools. The reason we have resorted to adding javascript to our Mobile development stack is cross-platform portability, and perceived ease in connecting to backend servers. Unfortunately, this causes all sort of other problems — including increased code stack complexity.

Wikipedia roughly defines Model Driven Architecture (MDA) as focusing on “forward engineering, i.e. producing code from abstract, human-elaborated modelling diagrams (e.g. class diagrams)”¹. Model-Driven Architecture and Model-Driven Development (MDD) is often composed of class diagrams and “Entity relationship modeling”² (ERM) among other things.

Basically, it seems to me that MDA/MDD advocates creating pretty pictures for collaboration between business units, designers, and developers.

Splicer is a “low code” platform that integrates mobile apps with relational SQL databases and RDBMS. It also is the least invasive “platform” with practically no learning curve, and is compatible with your existing development tools. Our open source server is written in java and scala, which provides the optimal runtime performance, and offers a mobility upgrade path to existing J2EE server stacks.

Splicer is the first open source, low code, enterprise mobile app and web development platform. Splicer’s data model automation mechanism works in conjunction with various stable, open source server technologies and mobile app development tools. This powerful combination results in the only open source, enterprise mobile stack — including a high-performance, java/scala server (J2EE) that runs on the Play Framework or Spring Boot. Moreover, our development system supports a variety of both web and native mobile clients for a comprehensive, cross-platform development solution.

Splicer DMA™ allows us to easily map client models to server models. We create our Model Maps™ in the CAM GUI, and then use Splicer’s 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.

Combine the mobile delivery power of Splicer with the Content Assembly Mechanism (CAM) editor. CAM allows us to create data subsets for mobile clients, and also combine data sources. Splicer is the modern replacement for Open-XDX, which delivered runtime data for CAM designs, but was too heavily focused on the XML format.