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.
Parsing Mr. Mahapatra’s article: “Not every business user [needs] to be an expert in engineering or have sizable budgets”. “[They can deploy] business apps … with the help of a platform … in a matter of days or weeks instead of months”. “It also minimizes the need for large, dedicated developer teams”.
He further explains, “there is a need for applications and capabilities to scale up in an instant”. I’ve experienced this first-hand, and its incredible to see native apps come to life in a matter of minutes.
He also mentions “context-aware data”, which implies adding meta data to the data itself somehow; it implies we need to create an object data model by using meta data. Creating the the definition in meta data is essential because native clients are heterogeneous. But if we can solve that piece, then the coding is much easier and can be applied to any part of the enterprise.
So it turns out, that solving native low-code is very simple. First, we must get control over our data structures via a comprehensive data model. But because we have heterogeneous clients, then we need to define the data model at a higher (macro) level. Fortunately, implementing this meta model™ in the enterprise is simple because the model itself is implied in the data structures in your various data stores such as RDBMS. This is demonstrated in our native low code video.
Mahapatra continues: “Developers’ jobs would shift [to] partnering with business teams to nurture and encourage low-code building capabilities that will drive greater agility for the enterprise”. This is all practical today via Splicer tooling:
- Collaboration: The partnering happens via better design tools – specifically, by gathering around our simple data model design tool. This is where developers and architects can partner better with the business side of the house.
- Agility: Regarding agility, it’s impossible to have agility without an agile model. Static typesafety around the data model allows for easier iteration of it. This also makes the code base far more maintainable.
- Product-Based Solution: Finally Mahapatra mentions: “developer teams would still be needed to help create the necessary building blocks for meeting the comprehensive requirements for each low-code platform solution if it is to truly scale across each industry and function.” Turns out, our common, product-based solution that runs on the standard Spring Boot server stack obviates this need.
Native Low-Code is applicable to any part of the enterprise, and it’s available today!
Please share your comments below, or feel free to drop us an email.