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.
AgilePoint 1, says low code platforms “are designed to abstract developers away from the actual code and provide a range of pre-built middleware services, eliminating the need for developers to rebuild the wheel… with each new development initiative.” Our middleware utility is unique in that we use “visual models”2 to create mobile data model artifacts that match our server model — expanding our server-side data model out to native mobile apps.
Another article in TechTarget 3 provides good news for managers trying to deal with their mobile development backlog: “Things have changed quickly. Today, CIOs view no NCLC (code/low code) as a way to off-load low-risk projects from developers’ overloaded backlogs.”.
This is all good news in that relief is available now for the mobile app backlog. We see the new tools described in these articles including InfoWorld4 are opening the enterprise to the “citizen developer” (non-programmers) . But what about the “enterprise developers” themselves? Every other low code solution asks you to sacrifice control to get the benefit of time-to-market. Instead, our tools provide the benefits of these “low code” RMAD, MADP, and aPaaS solutions, but enhance an enterprise developer’s productivity writing native code.
Ultimately, all “low code” systems provide new paths to server data. This is good because IT is overloaded and cannot keep up with market demands. Since low code has opened alternative paths into enterprise data, it’s time to address the many-to-many apps-to-databases scenario. One high-leverage piece to automate is the data model — namely, the ability to visually control and automate the relationships of many client models to a many data repositories. Splicer allows us to tackle this critical piece without having to re-engineer the rest of our Spring Boot system. Since delivering relational server data is typically the most complicated part, so lets automate it!
At Splicer, we realized that once we define a model, we can generate a great deal of a mobile client-server system. This drastically reduces developer workload, and allows better management of sets of apps. Also, our tools abstract out the model for you by deriving it from your existing model artifacts including relational SQL/RDBMS data. Since we always need to create data models, we have more flexibility for modifications and re-use if we operate at a higher-level of abstraction.
Control your models and have them automatically deliver data. The models are now compile-checked and guaranteed to correlate with a particular version of a server model. This is very powerful, fixes a ton of problems, and makes native programming fun and effective. Then you can combine Splicer with other best of breed tools rather than purchasing closed end-to-end solutions. This is the proper way to expand your Spring Boot stack out to Mobile.