Tag: lowcode

LINK: “Salesforce adds low-code tools so everyone can automate their CRM workflow”

Probably the most important aspect of the new tools announced today is that they are based on the Lightning Design System, and so form part of the entire landscape of tools used to build Salesforce CRM applications. In earlier generations of the Salesforce platform, people often came up against what insiders used to call a ‘declarative cliff’, where they would come up against one small element that couldn’t be done via point-and-click, and then the whole process would have to be coded from scratch. Because the new tools are part of a single platform, the objects and process flows they create can be fine-tuned in Lightning App Builder, or handed over to a developer for more in-depth coding as required.

Original: https://diginomica.com/2018/09/13/salesforce-adds-low-code-tools-everyone-automate-crm-workflow/

LINK: “The Future of Software Is No Code”

Today, companies like Quick Base, Mendix, and Zudy are pioneering a similar movement, attempting to transform code into visual interfaces. Much like in the shift from assembly code to FORTRAN, the underlying code is still there, but it can be represented more simply. These low-code/no-code platforms are beginning to disrupt how software powers enterprises.

Original: https://medium.com/s/story/the-future-of-software-is-no-code-7140bd0c30e3

LINK: “Why You Need To Know About Low-Code, Even If You’re Not Responsible For Software Delivery”

Low-code development platforms are emerging as a key strategy to accelerate app delivery to support digital business transformation. And they have the potential to make software development as much as 10 times faster than traditional methods.

Original: https://go.forrester.com/blogs/why-you-need-to-know-about-low-code-even-if-youre-not-responsible-for-software-delivery/

Two pieces on low code

The low code debate seems to have really kicked off.

Matt Skinner off of FutureGov blogs a critical piece:

The low code platforms we’ve tried place a big emphasis on making the lives of developers simpler (or redundant). Unfortunately, we notice this is at the expense of user experience. Low code makes it harder to take a user-centred, design-led approach.

When creating, you have to follow the platforms’ chosen UI components and design out of a prescribed box. Once completed, you can then tweak to meet your users needs. As the platform uses its own functionality, you are also restricted by what’s been created so far. It’s a world of functionality first and user needs later, which never ever ends well.

Paul Brewer from Adur & Worthing blogged himself in response:

After careful consideration, we went for what I think was a good, pragmatic compromise. Our chosen open standards platform (this is a must), providing a “low code” development environment, has a fixed enterprise licence fee that means we can not only build unlimited apps for ourselves, but can build apps for any public sector body operating in our geography at no additional cost. Development time is much faster than it would otherwise be, and the skills required are significant, but lower than other development environments.

Worth reading both in full to help you decide if low code fits into your strategy.

LINK: “Out of the shadows [on low code in local gov]”

At Adur & Worthing, our use of low code is core to our service design programme and the main tool used by our central digital team in change projects. We don’t go this way every time — we’re not purists — but time and again, we prove to ourselves it’s the better way.

Original: https://medium.com/@pdbrewer/out-of-the-shadows-189ffdd79522