4 ms·
It depends on the use case. For processes that are stable and where most edge cases have been solved, no-code is ideal. Take Salesforce for example. You can bui
by rchaud 7y ago
It depends on the use case. For processes that are stable and where most edge cases have been solved, no-code is ideal. Take Salesforce for example. You can build a number of mini-applications, like say a university application tracking system, simply by throwing together built-in components in SF.