The cause of

It is also the reason to write notes. There is not much work to move bricks recently, so I can have time to think by myself. At the same time, I am tired of the repetitive work and need to see if I can improve efficiency. Of course, the arrangement of the component library is also done at ordinary times, which can also improve efficiency.

define

The way front-end low-code development works relies heavily on manipulating graphical user interfaces, including drag-and-drop controls, and modifying the configuration of editable areas within them. Take my own understanding: remove the modularization and componentalization work in normal days, and use drag and drop to complete atomic level interaction and logical assembly.

No code and low code

  • No code: One is to find those relatively fixed product forms, such as company introduction, product list and event page, etc. based on experience summary in highly customized scenarios, and open a few editing portals for non-professional developers to use.
  • Low code: Following the ideas of early visual development, we try to achieve a page building process with higher freedom and higher interaction complexity limit through abstract syntax or IDE based on componentalization and data binding.
  • Pure code: Get it all

Strengths and weaknesses and make up a map

Mainstream low code platforms

Looking for a figure

I have tried Jandao Cloud, Yitaobai and Zhixin. Most of them are non-code platforms with simple operation and single function. All of them have become SASS services and the charges are quite expensive. There are a few things I don’t understand about how to interact with the back end. In general, the mainstream are mainly business users, many templates, mainly business functions.

Two ways to develop low code

  • Based on the way you write JSON,
  • Development method based on visual operation platform.

The first one, such as Baidu’s ASIM, is open source. It is equivalent to writing a JSON configuration file and throwing it to the UI to render the DOM. The second one is used by the mainstream low code platform above

Write JSON directly:

  • The efficiency is lower. In complex scenarios, JSON is very long and large, which is not beautiful and inconvenient for troubleshooting
  • Poor reuse, usually framework can also write a component multiple reuse, now JSON requires two JSON elements

I understand it

Combined with my own business needs. I don’t need such a large and complete business template. On the front UI, it’s mainly visual drag-and-drop, it’s the definition and assembly of workflow and then it’s really the embodiment of minimal function implementation on the server side

Todo:

  • It’s time to look at node serverless
  • Use what’s already there, research what’s already there