I firmly believe that low-code is not suitable for every development its simplicity. But this simplicity also means that there are forced limits to development. In my view, low-code should be seen as a playground for trying out new processes or solutions. As you will soon see, you can use SeaTable to develop an initial prototype in no time and then use it to test your process. After a few days, you and your team will quickly gain initial insights: do you actually need this process? Does the process need to be adapted or do we perhaps need to redesign it or approach it completely differently?
In my opinion, low-code should be usa rcs data seen as a playground for trying out new processes or solutions.
Of course, it is also possible that with this new knowledge you will consciously decide on a ready-made special solution or commission a developer to do the programming.
The important thing is that low-code has helped you implement your process and gain experience with it.
By the way, you don't necessarily have to read this text to develop your first low-code application. If you prefer to watch a video instead of reading a text, you can also watch the following video on YouTube.