A low-code development platform (LCDP) provides a software development environment – typically a graphical user interface (GUI) – that involves little or no writing of code. A low-code platform may produce entirely operational applications, or require additional coding for specific situations. Low-code development platforms are typically on a high abstraction level, and can reduce the amount of traditional time spent, enabling accelerated delivery of business applications. A common benefit is that a wider range of people can contribute to the application's development, not only those with coding skills, but good governance is needed to be able to adhere to common rules and regulations. LCDPs can also lower the initial cost of setup, training, deployment, and maintenance.[1]
Low-code development platforms trace their roots back to fourth-generation programming language and the rapid application development tools of the 1990s and early 2000s. Similar to these predecessor development environments, LCDPs are based on the principles of model-driven architecture, automatic code generation, and visual programming.[2] The concept of end-user development also existed previously, although LCDPs brought some new ways of approaching this development. The low-code development platform market traces its origins back to 2011.[3] The specific name "low-code" was not put forward until 9 June 2014,[1] when it was used by the industry analyst Forrester Research. Along with no-code development platforms, low-code was described as "extraordinarily disruptive" in Forbes magazine in 2017.[4]
Use
As a result of the microcomputer revolution, businesses have deployed computers widely across their employee bases, enabling widespread automation of business processes using software.[5] The need for software automation and new applications for business processes places demands on software developers to create custom applications in volume, tailoring them to organizations' unique needs.[6] Low-code development platforms have been developed as a means to allow for quick creation and use of working applications that can address the specific process and data needs of the organization.[7]
Reception
Research firm Forrester estimated in 2016 that the total market for low-code development platforms would grow to $15.5 billion by 2020.[8] Segments in the market include database, request handling, mobile, process, and general purpose low-code platforms.[9]
Low-code development's market growth can be attributed to its flexibility and ease.[10] Low-code development platforms are shifting their focus toward general purpose applications, with the ability to add in custom code when needed or desired.[3]
Mobile accessibility is one of the driving factors of using low-code development platforms.[6] Instead of developers having to spend time creating multi-device software, low-code packages typically come with that feature as standard.[6]
Because they require less coding knowledge, nearly anyone in a software development environment can learn to use a low-code development platform.[11] Features like drag and drop interfaces help users visualize and build the application[8]
Security and compliance concerns
Concerns over low-code development platform security and compliance are growing, especially for apps that use consumer data. There can be concerns over the security of apps built so quickly and possible lack of due governance leading to compliance issues.[10] However, low-code apps do also fuel security innovations. With continuous app development in mind, it becomes easier to create secure data workflows.[citation needed]
Criticisms
Some IT professionals question whether low-code development platforms are suitable for large-scale and mission-critical enterprise applications.[12] Others have questioned whether these platforms actually make development cheaper or easier.[13] Additionally, some CIOs have expressed concern that adopting low-code development platforms internally could lead to an increase in unsupported applications built by shadow IT.[14]
See also
References
- 1 2 Richardson, Clay (June 9, 2014). "New Development Platforms Emerge For Customer-Facing Applications". www.forrester.com. Retrieved 18 November 2016.
- ↑ Lonergan, Kevin (29 July 2015). "On the down low: Why CIOs should care about Low-code - Information Age". Information Age. Archived from the original on 2 February 2017. Retrieved 22 January 2017.
- 1 2 Marvin, Rob (12 August 2014). "How low-code development seeks to accelerate software delivery - SD Times". SD Times. San Diego Times. Retrieved 18 November 2016.
- ↑ Bloomberg, Jason. "The Low-Code/No-Code Movement: More Disruptive Than You Realize". www.forbes.com. Retrieved 20 August 2018.
- ↑ "Low-Code vs. No-Code App Development | Microsoft Power Apps". powerapps.microsoft.com. Retrieved 2023-01-06.
- 1 2 3 Marvin, Rob. "Building an App With No Coding: Myth or Reality?". PCMAG. PC Mag. Retrieved 18 November 2016.
- ↑ "Software developers: We're on board with low-code (Or even no-code) tools". ZDNet.
- 1 2 Richardson, Clay. "Vendor Landscape: The Fractured, Fertile Terrain Of Low-code Application Platforms" (PDF). Forrester Research. Archived from the original (PDF) on 2017-08-09. Retrieved 2017-01-25.
- ↑ Hammond, Jeffrey. "The Forrester Wave™: Mobile Low-Code Platforms For Business Developers, Q3 2018". www.forrester.com. Forrester Research. Archived from the original on 15 August 2018. Retrieved 8 August 2018.
- 1 2 Rubens, Paul (10 November 2014). "Use Low-code Platforms to Develop the Apps Customers Want". CIO. CIO Magazine.
- ↑ "Why We Will Always Need Data Scientists". Built In. Retrieved 2024-09-25.
- ↑ Rymer, John. "Low-Code Platforms Deliver Customer Facing Apps Fast, But Can They Scale Up?". Forrester Research. Archived from the original on 2 February 2017. Retrieved 22 January 2016.
- ↑ LLC, Flatlogic (2022-12-05). "What is the difference between Low Code & No Code". Flatlogic Blog. Retrieved 2023-01-06.
- ↑ Shore, Joel (31 July 2015). "How no-code development tools can benefit IT". Search Cloud Applications. TechTarget Magazine. Archived from the original on 2017-03-31. Retrieved 22 January 2017.