The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
Last reviewed: 2021-01-20
This is the direction page for No/Low-Code in GitLab. It is not officially a part of any DevOps stage nor is it an official category. Sarah Waldner (@sarahwaldner, firstname.lastname@example.org) Group Manager of Product for the Create stage, maintains this page and the vision.
Like most other category direction pages, this page will be continuously updated based on market dynamics, new data points, and customer conversations.
GitLab's mission is to build software so that everyone can contribute. Most applications are currently written by developers who have backgrounds in popular web application frameworks such as Ruby on Rails.
Out of 23.4 million developers worldwide in 2019, IDC said 1.76 million of them are low coders, representing 7.5% of the total. There were also 810,000 no-code developers worldwide last year, according to IDC’s Market Perspective: Low-Code and No-Code Developer Census, 2019: Growth Begins in Earnest report. Gartner, per its 2019 Magic Quadrant for Low-Code Platforms estimates that "by 2024, low-code application development will be responsible for more than 65% of application development activity."
The phrase citizen developer has begun to surface, indicating an individual without a professional background, who is utilizing Low/No-Code platforms to create applications for customers or internal for business process.
It's important that GitLab is able to serve all application development teams as well as citizen developers as this trend continues to grow and as such, we need to be forward thinking about how to provide a good experience for Low/No-Code developers inside of GitLab.
Low-Code and No-Code platforms are most commonly defined as platforms that enable individuals to visually code by dragging and dropping pre-written code blocks and connecting them together to create an application. This article has a fantastic synopsis of the difference between low-code and no-code platforms. There are many differences in how these platform categories, but the primary one is a no code platform doesn't allow coding for augmenting any components, and a low code platform does.
The primary benefit for adopting a low or no-code platform is speed of application delivery as well as the democratization of the application development process. With a low/no-code approach, apps can be built more quickly with less specialized skillsets, which lowers the barrier of entry of development and deployment of the application. In short, more people are able to contribute to application development, whether that's a traditional web app or an internal business process, and they are able to develop faster than before.
Platforms like ServiceNow and Salesforce are also popular because of their low-code capabilities. They often employ visual coding experiences and excellent support for code completion, syntax highlighting, and code hints. In some cases, the low-code functionality is limited to experiences inside of the application. For example, the primary use case for using Salesforce's low-code capabilities is to create applications and/or views inside of Salesforce.
Low-Code: Target users are professional developers who are primarily looking for efficiency gains but also citizen developers who have a basic knowledge with writing code. Low-code platforms often require coding to introduce pieces of functionality the platform may not have. In low-code platforms some coding is ok, but limits are not.
No-Code: Target users are the citizen developers who will not be writing any code and are primarily looking to develop applications per their needs, most commonly internal business process automation. With no-code platforms, you are limited to the capabilities that the platform provides you. In no-code platforms some coding is not ok, but limits are.
In a sense, no-code platforms can be thought of as a subset of low-code platforms, which is how Gartner has also defined them in their 2019 Magic Quadrant.
Our immediate next step is to validate our thoughts in this space and speak to some customers to assess what problems could be solved inside of GitLab related to this space.
While we likely aren't ready to pursue any specific features into GitLab yet, we are evaluating several open source low-code tools to include in GitLab in this epic. We should likely start with a low-code solution that will be targeted to professional developers already using GitLab. Starting with a no-code framework likely won't get us the usage we'd need for rapid feedback in an acceptable time period.
The bulk of low/no-code platforms are proprietary systems such as Salesforce and Appian, so we will need to investigate more if we can integrate with these tools, or build our own based on an open-source product. For example, applications developed for on ServiceNow and Salesforce may need to be deployed or versioned and GitLab would be an excellent complementary solution for these platforms.
There are two workstreams for us to puruse:
Per the 2020 Gartner Magic Quadrant for Low-Code, the following vendors made the report:
|Mendix||Oracle (Visual Builder)||Kintone|
It's important to note that platforms such as Salesforce Lightning are included in the market definition of low-code and these platforms are primarily used for delivering customer-related applications and extensions to other SaaS products.
Additionally, there are several open source low code tools:
On June 29, 2021, GitHub announced the Technical Preview of GitHub Copilot which has mostly gained interest as a solution that is akin to a low-code platform. There was a notable level of concern that GitHub used public repositories with potentially incompatible licenses to train the AI. GitHub publicly responded in their copilot FAQ.
What they are saying:
Reports of Interest: