The most difficult piece for enterprise mobile development is integrating sets of clients to your servers. So let’s leverage RMAD tools to extend server data structures to your native clients. This technique provides mind-blowing development efficiency — and allows you to affordably host your own native solutions instead of getting locked into other proprietary “low code” systems.
Gartner apparently coined the term “RMAD” and discusses the challenge of mobile enterprise development here: http://www.gartner.com/newsroom/id/3076817 . Quoting Gartner, “Integration is often the largest part of the effort”. This is the piece Splicer solves, so good. I’m not sure what they mean by “bimodal IT approach”, but Splicer does provide model Agility, while allowing you to easily integrate to structured databases including RDBMS. So I think we’ve got that concept covered. When they suggest RMAD tools, we believe using any proprietary technology end-to-end is a terrible mistake. Instead, Splicer focuses on RAD-ifying the development of client-server models, which again is the most difficult piece.
Generally, RMAD and MADP tend to over-automate, and attempt to tie you to their proprietary approach. Another drawback of end-to-end RMAD and MADP is it can be difficult to hire people qualified in these technologies. And by committing to these proprietary systems, you can paint yourself into a corner in that most of them will not be around within a few years. And most developers that I know would much rather code natively. Code is what provides the power and flexibility to maintain a system long-term.
Quoting the article again:“Organizations want to have full control over their mobile app development initiatives”. True that, but then they imply you must compromise. We disagree. It seems everyone is so freaked-out with the complexity of mobile development that the pendulum has swung too far in these systems: they eliminate all coding. Instead, with Splicer, you have source code control and the benefits of RMAD (namely the “RAD” part). So, instead of hiring engineers to integrate native apps, leverage Splicer instead as part of a “mixed source” strategy.
We certainly understand that these tools are useful in very specific circumstances, but for general enterprise development, they are not practical. This implies we need other tools that solve particular pieces of the puzzle. Splicer solves the mobile client-server mess by allowing you to first manage your mobile models and then automatically serve data to them. As a RAD tool, Splicer uses automation to expose DAOs to mobile coders. Its novel “RAD” piece is a GUI that allows you to pick which elements in your server model you expose to a a particular mobile client. More details on this can be found at http://splicer.io.