Splicer Blog

Accelerating Native Mobility

Native Enterprise Mobility Tools

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.

Spring Boot for Mobile Crushes SQL/Relational Data

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 Cost via Developer Productivity Tools

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.

Solve Native Mobile Developer Shortages With Better Tools

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.

Javascript-free, Native Mobile Coding for the Enterprise

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.

Model-Driven, Mobile Architecture for Native Mobile App Development

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)”1. Model-Driven Architecture and Model-Driven Development (MDD) is often composed of class diagrams and “Entity relationship modeling”2 (ERM) among other things.

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