foreword
Low-code is a method of designing and developing software applications quickly with minimal manual coding. By using visual modeling in a graphical interface to assemble and configure applications, developers can skip all the infrastructure and speed up development.
1. Find the problem
1. "Before taking a step, first consider whether you can go back"
Let’s not talk about the function and performance of the low-code platform now. Whether it can improve efficiency and how much it can be improved will not be discussed for the time being. The point of "platform and environment lock-in" alone is the biggest obstacle to technology promotion in the entire industry.
The reason is simple. There are hundreds of platforms, but if you choose one, because you cannot generate code, it means that all R&D and data resources must be placed on this platform, and it will not be possible to migrate in the future.
This means, "Once you take this step, you will not be able to return to the original path!" This is unacceptable for any enterprise and team, and the risk is too great.
2. "What about previous code and R&D/data resources?"
Adoption of low-code platforms may require adjustments to organizational structures and processes. This may involve changes in the way different teams collaborate and communicate.
Every enterprise, due to long-term R&D and evolution, often forms its own R&D system and its own R&D resources/data resources. How to use these resources on the "low-code platform" is also a problem.
Can our SDK be uploaded?
Can our existing components be used directly?
Our team is used to elementUI, how do we continue to use it?
How do we use a large number of various types of data and interfaces? …
3. "In addition, the programmers themselves are also the resistance to the use of the platform"
For such a platform, many programmers have an "instinctive resistance". Of course, the most important thing is to worry about whether the technology will be locked in a certain low-code platform, will it affect the future "self-technical improvement", or even affect the own income? Of course, there are deeper reasons, which are closely related to the programmer's mentality.
In short, what technology and platform should the enterprise choose? It must be the R&D director/CTO/CIO who has the final say, and they will seek the opinions of the technical team. If most of the technical team opposes, this technology will definitely not be promoted.
Two, solve the problem
1. Can the standards of low-code platforms be unified?
In fact, it is simply impossible, whether it is through open source, or the endorsement and promotion of major manufacturers... It is actually impossible. In fact, technology can only evolve, and seldom can be fixed through formalized things, unless it is part of a fait accompli.
2. "Generate Code"! ! !
This is also what I want to say, a truly feasible "low-code platform" landing solution that can be accepted by programmers. The generated "code" unifies the form through the programming language. This is to achieve "smooth evolution" instead of "leap forward". Historically, binary to assembly language, assembly language to high-level language, is also such a "smooth mode".
"The whole stack of the low-code platform generates code for you, and all applications are saved in the form of code"-this is the form that can be accepted by the R&D team.
3. A code-generating low-code product
iVX platform
iVX, can be understood as a visual "full-stack code generator", and this "code generation" is quite thorough, almost all applications can use iVX to perform "automatic code generation" without writing any code .
The development of the iVX platform is extremely difficult and involves a wide range of technical fields. As far as I know, it is the only one that can automatically generate full-stack codes in the global field.
Although the market includes many media that define iVX as a "low-code" platform, in fact, iVX and other "low-code/no-code" platforms on the market, whether it is "technical architecture", "implementation method", "user experience" /operation" and "product purpose" are completely different.
All other low-code products can almost be regarded as a "rapid development framework within the enterprise". The runtime and development are integrated, which means that all developed applications can only run in the environment of this low-code manufacturer. The application cannot be exported or independently deployed, and the manifestation is "unable to generate application source code".
However, iVX is not a product completely aimed at "enterprises", but a new "development paradigm" oriented to programming and programmers. iVX always only solves two problems: "How to let novices quickly learn application development?" And "How to make development more efficient?". Therefore, iVX can be used by both individuals and businesses, and it's free online.
3. "Reusable" of iVX
Reusable front-end code
iVX provides various front-end components, supports CSS embedding, supports JS code embedding, supports various component libraries and uploads custom components. The iVX front-end program supports compilation into various types, including web applications, applets, native apps, Mac OS and Windows desktop applications, etc.
Reusable SQL code
Through the iVXdbo component, developers can connect to any common database such as Mysql, Oracle, SQL server and Postgres that they deploy. It supports self-written SQL to operate the database and obtain the returned results, seamlessly integrating with other background service logic.
Reusable backend code
It supports common background languages such as nodeJS, Java, python, etc. Users can upload the background code or SDK by themselves, and communicate with the main service through the RPC protocol.
Summarize
Now code generation has the ability to be "readable" and "debuggable". The experience is no different from that of handwritten code, including the way of maintenance.
In short, it should be more rational to only help programmers and not challenge programmers. The unique feature of iVX is that it not only provides an easy-to-use visual development environment like other low-code platforms, but also generates code that can be exported, edited and debugged independently. This design concept makes iVX a real low-code development platform.
In fact, for such a platform, to a large extent, there is no need to write any code by hand, including secondary development, which can be completed on the platform through drag and drop configuration. However, it is very important to maintain the "code" interface for programmers!
