Skip to main content

Low Code Software Tradeoffs


Recently I wrote on The Enduring Appeal of Low Code Software Development and 6 Reasons to Choose Microsoft for your Low Code Application Platform which explain why low code development is popular and why Microsoft is especially successful among the low code application development platforms.  Like many decisions, moving to low code software involves tradeoffs, so this post is devoted to some of the considerations that may shape your decision on whether and how far to move toward low code.

Performance

The first tradeoff is performance.  If your goal is to squeeze every bit of performance out of a system, low code may not be the best option.  Low code platforms involve layers of abstraction and code that introduce overhead,  For extremely large data sets, intensive calculations, or real time operations, you do not see many low code systems.  Instead, the highest performance systems use full code and get as close to the data as possible to max out speed. 

User Experience

Low code systems save you development time by offering pre-built user interface elements.  You do not have to build out or maintain as much code as if you were creating each screen from scratch.  The tradeoff comes if you want the screens to look different than offered by the low cost platform by default.  In many cases you can change the look and feel through custom programming, thus giving up some of the virtue of the pre-built environment.  If you are creating a user experience unlike any other, you may be better off to start with the blank slate of full coding and build the user interface from the ground up.  

Vendor Lock-in

Choosing a vendor for your low code platform means you are committed to that vendor and to the future of their company as well as their products.  The more solutions you base on that low code platform the more you are exposed to this business risk.  You must choose a company you are confident will be around for the long haul, and that their product will continue to receive security updates as well as research and development investments. With small vendors you may be concerned that they will go out of business or be acquired.  With all vendors you must be confident that the product you choose remains competitive and not discontinued.  

Product Cost v Development Cost

While low code offers the promise of faster development and simpler maintenance of software, it carries the ongoing cost of licenses or subscriptions for the low code platform.  These costs can add up, especially if they are based on the count of users and you have a large number of users.  Custom code can give you zero license costs, so you can spread the cost of development across all the user base and over a long period of time.  In a simple example, the same solution might cost $100,000 to develop as low code and $1 million to build as a custom application.  If you have 100 users and they pay $1,000 per user per year then your total cost for the first year is $100,000 for licensing and $100,000 for development or $200,000.  For 10,000 users, the low code solution would be $10,100,000 and $10 million per year for the life of the solution.  The custom development solution would be $1,000,000 for the initial development and then only maintenance programming regardless of the number of users. 

Low code is therefore easier to justify for apps with small numbers of users. These might even be so small they would not justify a custom code solution in the first place. 



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 .onmicrosoft.com such as acme.onmicrosoft.com.  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:  https://powerapps.microsoft.com/en-us/infopath/ 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 not require advan