Skip to main content

The Enduring Appeal of Low Code Software Development


by James Townsend

As we bid farewell to 2020, we can look back on the tech trends that shaped the world response to the COVID crisis.  The shock of COVID and resulting lockdowns accelerated existing trends such as digital transformation, remote work, and even software development methodologies and tools. 

For decades, organizations could only choose between off-the-shelf products and custom software development.  Over the last 30 years another option -- low code software development -- has risen.  This trend began with fourth generation programming languages (4GL) and computer-aided software engineering (CASE) tools in the 1980s.  Desktop database products like DataEase, Paradox, Clipper and Microsoft Access were early examples of the low code approach. 

Today, there are many types of low code software platforms.  Some are business platforms such as Microsoft Dynamics, Salesforce, and ServiceNow. Another group are business process management (BPM) products such as Appian and Pega, the heirs of CASE tools, which not only model business processes but create working code and user interfaces. A third group is more specialized, geared toward a particular type of scenario such as Boomi for integrations.  Meanwhile, the leading cloud vendors Amazon Web Services and Microsoft have rolled out their suites of low code development tools and support for open source products. 

The allure of low code is in the promise to:

  • Build solutions more quickly and less expensively
  • Allow flexibility for future changes as business rules evolve
  • Reduce software testing requirements
  • Reduce the staff needed for ongoing support
  • Shift security and software maintenance to the cloud vendor of the low code platform
  • Reduce reliance on high cost software developers
  • Empower "citizen developers" or power users to create and maintain the apps in place or alongside developers

These benefits are a tall order for any product to fulfill.  I have written elsewhere that low code doesn't mean easy, and that deep technical skills are still needed to succeed on these platforms.  Eliminating code entirely seems to me a fool's errand, because there are business rules more concisely expressed in code than any other way. 

Not every low code project succeeds.  Like all software development, low code projects require the backing of stakeholders and users, solid understanding of requirements and data, project management consistent with the methodology, and, yes, software developers and infrastructure experts. Familiarity with the low code toolset is also a prerequisite for success. 

Low code products are not cheap, and those that require licenses or subscriptions for all users can become prohibitively expensive for large organizations, overshadowing potential labor cost savings. If the licensing model allows it, some low code platforms priced by user become less expensive (at least per app) for each new app which is deployed, bringing the incremental licensing expense to zero. 

The variety of low code platforms also makes it challenging to choose the right one for your project, and even more difficult to standardize on a platform throughout an enterprise. 

Regardless of the limits of low code development, or whether shifting costs from people to platform really saves money, low code is here to stay and likely to increase in comparison to custom development.  Perhaps 2021 will be the year that your organization moves in this direction. 

See related posts:

For Low Code Software, Keep Requirements Low

6 Reasons to Choose Microsoft for your Low Code Application Platform

Low Code Solutions Require High Knowledge

DevOps for Microsoft Dynamics

Microsoft Power Apps and Power Platform: Build Apps without Limits

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of such as  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source: by James Townsend Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do