Does the Dynamic form system useful?

David Chen
2 min readDec 18, 2020

Dynamic form system
During the work, we will receive several requirements frequently either from clients or from internal users. However, most of the requirements would be as following.
1. Hey, Can we alter this field name as a title case?
2. Hey, Can we alter this field to somewhere?
3. I am not sure how the product would look like can we do a quick POC?

However, as an engineer don’t really care what it looks like in most cases, If we have already predefined the schema, API…. We should be able to change this bit easily but somehow we will feel it is wasting our time as well? As a lazy engineer? would come up why we not build a dynamic form system and then the user can alter whatever they want. What we really need to do is pre-define everything and create a place for them to build their playground.
Basically, the end game is everything would be all data-driven. User should take their own responsibility to design the form they want and choose the resource we have already pre-defined. Then we don’t need to do anything. What a happy world it is??
However, does that really easy to achieve? My answer is no… Does really dynamic? My answer is I am not sure but why I would like to do that? The reason, in the beginning, is just that would be super cool. It’s a fantastic journey.

The following will introduce the solution existing in the world and compare what is the main difference. Also, will try to keep a record of the process of how we generate our own dynamic form system. It might be useless. It might be boring. It might be not scalable but again this is a cool journey, isn’t it?

Feel free to give any feedback if you feel my english grammar is wrong or view is wrong.

--

--