Recently, I found probably the first independent editorial regarding native low-code. It provides a great overview: Imagining a Native Low-Code World. It’s great to see someone else shed some light on this exciting subject matter.

Push-button, full-stack prototypes are finally here. And we don’t require a proprietary low code platform like other vendors. Splicer deploys right to the standard enterprise stack you are already running.

Graphically compose Spring Boot microservices using the open source model editor called CAM. CAM allows us to define data subsets for clients, and also aggregate data from multiple sources.

If you’re trying to expand your enterprise code coverage to include mobility, you’ve come to the right place. We use either your database schema, or server model to generate native Android and IOS entity classes. These objects then become the client’s interface to your backend — thereby extending the object-relational (ORM) paradigm to the mobile coder.

Splicer offers “low code” tools to integrate native mobile apps with Spring Boot servers. This is the least invasive mobile upgrade path for Spring Boot — with practically no learning curve. Our open source code runs on top of Spring Data, which provides an easy mobility upgrade to existing J2EE server stacks.

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 (MADP) 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.