Splicer is a “low code” platform that integrates mobile apps with structured server data and databases including RDBMS. It also is the least invasive “platform” with practically no learning curve; you can keep developing using the tools you are already using.
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.” This fits what we have done here at Splicer as we use “visual models”2 to create integrated mobile data model artifacts.
Another recent article in TechTarget 3 provides good news for managers trying to deal with their mobile development backlog: “Things have changed quickly. Today, CIOs view NCLC 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? No matter where we look — including MBaaS — we find that your team is asked to sacrifice control to get the benefit of time-to-market. Instead, we need hybrid tools that provide the benefits of these “low code” RMAD, MADP, and aPaaS solutions, but enhance an enterprise developer’s productivity writing native code.
From our perspective, these new classes of tools ultimately provide new paths to server data. This is good because we contend that general-purpose web services have failed us. Why is this? Because web pages are so drastically different than mobile apps that there is not much crossover for code re-use. Also as the demand for new mobile apps explodes, the servers are not architected to support this rapid proliferation. This is the reason that no matter how hard our server guys try, they just cannot clear up the backlog AND continue to support web page delivery with the same web server architecture.
Since we are now open to alternative paths into the enterprise, it’s time to address this many-to-one apps-to-server 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 given server model. Splicer allows us to tackle this critical piece without having to re-engineer the rest of our system. Also connecting to 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. 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.