Low-code and no-code are two distinct concepts that target different personas and require separate product strategies. This page presents low-code and no-code work streams in two sections.
|2022-12-17||Visual Workflow Builder POC||https://youtu.be/DI-IcY6vm6g|
|2022-11-28||Automation UX POC||https://youtu.be/w-dGDBlIr0Y|
|2022-10-31||Workflow Automation MVC||https://youtu.be/L_pvpjtYdLk|
|2022-10-24||Introduce low-code/no-code SEG||https://youtu.be/r3Ib00Z5Dj0|
At GitLab, issues and MRs are the backbones to project planning and delivery. Project managers typically have processes to update issue assignees, labels and other statuses based on certain triggering events and conditions. However, these repetitive takes do not scale when the orgnization grows and become counterproductive and error-prone.
GitLab's complete DevOps lifecycle solution provides a tremendous opportunity for rule-based automation to streamline across business functions. The visual programming model allows the non-technical business users to then build and own these automation rules.
When managing projects, I want to automate the repetitive tasks, so I can focus on the more value-added work.
Given the current focus on the project management automation, the Project Management group is the SEG's product development group affinity to partner with.
Gartner predicts by 2024, 75% of software solutions will be delivered with some help of low-code tools. While developers appreciate the efficiency gain, they also share several concerns with room for improvement. For example:
GitLab is well-positioned to disrupt the low-code market by unifying a new breed of open-source low-code platforms with GitLab's mature DevOps workflow to provide an alternative software delivery approach with maximized efficiency.
When building applications with low-code platforms, I want to follow the best DevOps practices, so that my application can be trusted.
The project follows the Double Diamond design process with an emphasis on delivering customer value early and iteratively.
The project is currently progressing through the discovery phase to understand the problem domain better. The next step is to gather internal and customer feedback on the identified problem and high-level approach. A more concrete delivery plan is to be announced soon after the finalisation of the problem statement.
Epic link: TBA
Ideally, we can adopt FOSS solutions with an active community. Engaging these communities from day-one means that we can receive feedback from early problem validation, iterative delivery all the way to the final product launch.
In addition, the project may also benefit from the internal dogfooding process. Teams and individuals who have the need to build internal apps are the candidates for dogfooding the low-code solution.
Low-code typically refers to the development platforms that leverage the graphical user interface or other means to reduce the traditional coding effort to accelerate software delivery. These platforms target developers who are comfortable writing code to introduce additional business logic.
No-code's goal is similar to low-code in terms of expediting application development. However, no-code platforms eliminate the need to write code, therefore, are more prevalent among citizen developers.