When Brad and I started GTconsult we did so under a “No Code Philosophy”. We had both lived through consultancies who knew no better and as soon as they had a project would pull out Visual studio and start C#ing as much of the project as possible, irrespective of whether the SharePoint Platform they were building on had the inherent functionality already included or not. We saw the problem with upgrades requiring expensive refactoring projects. We lived through trying to support these platforms. We knew this wasnt the right approach, and so we allowed only Front-end code on SharePoint, making our solutions transportable. This approach allowed us to tranfer our skills quickly to Office 365 development on SharePoint Online. This story resonated with clients who enjoyed this approach. These same client got to using SharePoint and Azure and got used to provisioning quick solutions to solve business problems, they demanded more and they demanded faster turnaround, whilst the requirements specifications got vaguer as they realised that they could make the tools work for them.
It was then we realised the need for Low Code solutions, the ability to rapidly develop a solution on the platform that could work like the phone apps of old, as a MVP (
Minimal viable product) and then expand the solution from there.
The accessibility of the APIs in SharePoint and the use of frameworks allowed us to achieve this approach successfully. It was no surprise to use when the SharePoint Framework was introduced essentially provisioning this capability and at the same time making it a new best practice for SharePoint.
So how do Low Code Frameworks work. –
What are the benefits of this approach –
Whilst these arent the only benefits they pack a punch. we believe that this approach is the new way of working in the fast moving “digital transformation” world that we find ourselves in. The good old days of being given a specification, working through a large project for a couple of months in a waterfall approach to deliver a product that might no longer be relevant are gone. That is not to say you shouldnt plan what you are doing, in fact you should spend more time planning the best configuration of your low code solution, so that once you have amazed your client and are extending the solution it is stable and well architected.