Web applications: The age of low/no code solutions?


Bernhard Klug

Bernhard Klug

Digital Consultant & Transformation (Mostly it’s online marketing and branding.)

Although no-code solutions are becoming increasingly functional, professional programmers continue to be the driving force behind many aspects of modern applications. We will discuss the advantages and drawbacks of low-code and no-code platforms as well as custom development, pointing out when each approach is most appropriate.

Development platforms benefits and shortcoming

Low code and no-code development allow you to develop and deploy applications faster and within smaller budgets compared to traditional software development.

Low-code implies a mix of software coding and noncoding to create an application.
You can compare high- and low-code options to building a home from scratch or using pre-fabricated modules. Using prefab parts, you can create beautiful houses, but they may not be as flexible in terms of function or design.

The benefits of pro code

Custom software is controlled by the business that uses it. The organization owns the source code and therefore has control over the application’s architecture, security, and features.

Enterprise-class apps depend heavily on scalability and performance, which are hard to achieve with low-code. Also, it’s not easy to modify the platform’s functionalities.

Let’s explain some main terms.

What is WordPress, Webflow, JAMstack, and a Content Management System?

WordPress is a content management solution (CMS) that allows users to easily develop and maintain websites, blogs, or even a SaaS. It is considered to be the most successful CMS, with approximately 35% of all websites running on it.

Es wurde kein Alt-Text für dieses Bild angegeben.
JAMstack is a way to create websites and web apps. JAMstack combines multiple services and platforms to build faster, more secure websites and web apps. JAM is a software stack made up of three core technologies: JavaScript, APIs, and Markup.

WordPress may be a good foundation for building a website. Yet, the blogging platform has its limitations. When it comes to creating more complex web applications, upgrading to a more robust software architecture will offer you better performance and scalability going forward. WordPress responds to requests from a single source, runs PHP, asks the database for information while a static page is “just” loaded.

Webflow is a design and development platform that can be used with little to no programming knowledge. While it can create incredible websites and applications, one can also export static pages from Webflow.

Is it better to build an application on JAMstack?

Building a web application on JAMstack makes a lot of sense. The biggest advantages are scalability, performance and security. Static websites only load the data they need and require no back-end server to render the website after it has been built.

Despite the benefits JAMstack offers, the biggest drawback is that you will need to have programming skills to add any new features or make even minor changes.

Future E-Commerce architecture? Maybe Shop-layer.
Shopify, WooCommerce & BigCommerce are the biggest names in e-commerce, but many companies are also considering JAM architecture as an alternative to creating their ecommerce systems.

With some e-commerce service provider, it is possible to build a decoupled ecommerce platform on JAMstack. This means that when users browse product listings, there is no need to make any database queries to gather data about the products—it is already done for us when the code is compiled.

When it comes to E-Commerce, speed, reliability and security are the name of the game.
But with all the upsides come challenges, too. You’ll encounter long build times, particularly for bigger pages. Dynamic data is much harder to handle, especially if you’ve been locked into something. A/B testing can be challenging because client-side JavaScript used by analytic tools is quite heavy.

Headless/Decoupled CMS with WordPress?

A JAMstack is only a software stack, it can be used with any CMS in a headless approach. But does it make sense? You won’t get to enjoy the benefits of a CMS, an easy-to-use publishing platform and the thousands of available plug-ins and themes.

I would recommend this approach only if you are currently running WordPress and do not want to change your back-end user experience. For rebuilds or newly built sites, other content management systems such as Ghost or Strapi will be easier to build upon.

What’s the best choice?

The JAMstack approach provides fast, secure, and scalable new ways to create websites on the web but what good is that if you can’t use your favourite CMS or are forced to recreate important features?

You may want to check out getShifter.io, or WP2Static for an alternative approach delivering a static site generated from WordPress.

For the majority of projects, a common CMS like WordPress, Wix or Shopify for E-Commerce will still be the best choice. However, new tools are beginning to emerge that make building on JAMstack easier and more accessible for developers and maybe even designers.


say hi

Just send a mail, and we will get back to you.


Bernhard Klug

Bernhard Klug

Digital Consultant & Transformation (Mostly it’s online marketing and branding.)

say hi

Just send a mail, and we will get back to you.