|Image Source: Joget Inc|
I had an opportunity to share personal view on "What to Look Out for When Evaluating a Low-code Platform?", based on my 10 years of exposure in the advocacy of low-code development tools. It doesn't matter whether or not you are evaluating Joget. My view was shared as a 9-point checklist, which I hope is helpful to serve as a guideline when your organization is assessing low-code tool - especially when it is meant to be served as citizen development platform.
1. ToolingIt goes without saying that, low-code tools are the key pillars in any low-code platform.
- Basic consideration such as processes, end-user application interfaces, forms, reports, user directory and access-control list should be able to be designed and administered through configurations.
- Any very importantly, how sophisticated can the UI of form design be configured from wizard/dialog? It defeats the purpose, if slightly more sophisticated requirements would require coding. Examples are: tabbed form, pop-up search and selection, one-to-many relationship between entities, asynchronous data pulling, grid-table multi-row data input, and validation rules.
- You may want to take note on IDE (integrated development environment) dependency, as to whether any client software installation is required by a low-code developer.
Low-code doesn't imply no-code. As such, is there a "code behind" flexibility when need arises?