“Every time you write a new code, you should do so reluctantly, under duress, because you completely exhausted all your other options.” - Jeff Atwood @codinghorror

Hence the growing popularity of the no-code software.

A quick thread 👇

1/

NO-CODE IS EATING THE WORLD

The concept isn't new (remember Microsoft FrontPage?) but the capabilities that the no-code and low-code tools offer today change the way individuals and businesses approach building digital products.

WHY IT'S INTERESTING? 👇
2/

No-code tools let you build things without writing code. Websites, mobile apps, online stores – all that (and a lot more!) can be built without any prior coding experience.
3/

Even though the “no-code” label is often an oversell (many platforms are "just" low-code and still require some low programming effort), the capabilities offered are game-changing, especially at the first stages of product development.
4/

Key no-code platforms:

•@Shopify: e-commerce
•@canva: design
•@airtable: databases
•@webflow: web development
•@zapier: process automation
•@bubble: mobile app development
5/

LOOKING AHEAD

•Gartner states low-code platforms will be responsible for more than 65 percent of all app dev activity by 2024
•Forrester expects the low-code market to represent $21bn in spending by 2022
•No-code market will be valued at $46bn by 2023 ($8bn in 2018)
6/

From a development perspective, low-code software should be seen as the next big thing after frameworks and APIs. A productivity hack that allows us to do more with less.
7/

From a business perspective, no-code tools allow business owners to put more effort into what really drives results: business strategy, market traction, community-building, sales and marketing.

The product itself is no longer a roadblock. Or an excuse.
8/

For a deeper analysis of the no-code movement, definitely read this great piece from @alexandre_dewez and @thibault_brnrd:

https://t.co/0DYI1MLmeF

And for more tech updates and news, join our weekly newsletter:
https://t.co/66v5kD4FZ5

More from Startups

1/ Tuesday was my last day as CEO of @CircleUp. I’ve been CEO since starting the co. in 2011 with my co-founder @roryeakin.

This is a thread about what happened, why and my emotions about it. For more detail:

https://t.co/vYImcm1bTM

Much of this I have never talked about.

2/ My goals: I hope it helps founders feel less lonely than I did. Little public content about the challenges of transitioning exists, but I longed for it. I’m not here to provide a playbook- just to share my experience. Hope it might build greater empathy.

Here goes….

3/ Why: When I tell people that I’m transitioning to an Exec Chairman role their first question is always: “why?” Short answer: co. pivot + fertility issues + health issues + a false sense that grit was always the answer = burnout. Long answer: is longer so hang in there with me

4/ Over a 12-18 month period that ended in late 2017 I ran my tank far beyond empty for far too long. You know that sound your car makes when it’s sputtering for more gas? It was like that. Worst year of my life. Since then it has felt like bone on bone.

5/ Here is what happened:

Professionally: pivoting a Series C company was a living hell in and of itself, as I’ve talked about before.
There are a *lot* of software shops in the world that would far rather have one more technical dependency than they'd like to pay for one of their 20 engineers to become the company's SPOF expert on the joys of e.g. HTTP file uploads, CSV parsing bugs, PDF generation, etc.


Every year at MicroConf I get surprised-not-surprised by the number of people I meet who are running "Does one thing reasonably well, ranks well for it, pulls down a full-time dev salary" out of a fun side project which obviates a frequent 1~5 engineer-day sprint horizontally.

"Who is the prototypical client here?"

A consulting shop delivering a $X00k engagement for an internal system, a SaaS company doing something custom for a large client or internally facing or deeply non-core to their business, etc.

(I feel like many of these businesses are good answers to the "how would you monetize OSS to make it sustainable?" fashion, since they often wrap a core OSS offering in the assorted infrastructure which makes it easily consumable.)

"But don't the customers get subscription fatigue?"

I think subscription fatigue is far more reported by people who are embarrassed to charge money for software than it is experienced by for-profit businesses, who don't seem to have gotten pay-biweekly-for-services fatigue.

You May Also Like