Your first low-code use case and simplicity vs. complexity

Starting a new low-code project is fun.

Still, sometimes it can be challenging to choose the right use case. What features do you want to add while ensuring the project does not turn into a technical odyssey that never goes live or doesn't create value?

To make things easier, it's best to look for use cases that offer medium technical complexity and create a tangible value return on investment.

But what makes a use case complex?

There are several requirements that you should avoid in your first project to keep things simple.

For instance, it's recommended to host your application on a managed environment like MxCloud instead of deploying it on-premise or on the edge. While the latter options are always available they usually increase the technical burden on a project.

Web browser apps are also preferred for first use cases over mobile apps, which require a more challenging user experience and user interface design.

Data-related requirements can also increase complexity, especially when you need to CRUD/export/import data outside of the Mendix Database. Additionally, processing significant volumes of data can also increase the complexity of your project.

Reporting requirements for graphic representations, excel exports, pdf exports, and other features often add complexity to your project. The same applies to specific content management requirements like dynamic images, file uploads/downloads, and document generation.

Finally, integrating your application with other systems like ERP, MES, and/or PLM can significantly increase complexity as you have to manage the integration layer, data complexity in the integrated system, and data flow processes.

By avoiding a combination of many of these requirements (or at least reducing them for a first application version) in your first low-code project, you can keep things simple and increase your chances of success.