I run a nocode platform with some large and global applications made/run on our platform. During architecting phase of the application - we do estimate if noco

I run a nocode platform with some large and global applications made/run on our platform. During architecting phase of the application - we do estimate if nocode tooling will hit a ceiling. If yes then we explore 4 options: - no brainer, export code and take it from there - write custom Ui controls and patch them into your nocode tool - write custom function and patch in the workflow engine or front end logic - build Ui/UX using external code and use nocode to build backend process and connect front end with apis of the workflows/dbs - generally complex algorithms - eg route optimization, would become a candidate of converting into a web service and eventually consumed in the nocode tool. In my experience - One of the core essentials to write an application on nocode is having your sprint 0 dedicated towards a design phase.