3
0 Comments

How much "no" is there in low-code?

Hi nocoders! At what point does a tool require so many technical skills that you'd rather choose another one🙅?

I'm asking because I want to improve the user experience of low-code (I'm a developer).
And so I'd like to understand the non-technical side better 🙂

As an experiment, I've made a video to introduce low-code to friends and LinkedIn-connections: https://youtu.be/LM7bk_jDHWw

So the question is also, whether to focus on creating good explanations 👨‍🏫 or making tools more intuitive to use🛠️?

In both cases, I'd like to understand your pain points with low-code!

posted to Icon for group No-Code
No-Code
on January 15, 2021
Trending on Indie Hackers
I built an AI that turns an idea into a live business in under 10 minutes. Here’s what 1,000 launches taught me User Avatar 89 comments Building a startup costs $0. Your tooling budget costs $500K. Here's why. User Avatar 45 comments Stop losing deals in the gap between "sounds good" and getting paid User Avatar 41 comments Building Noodle, a keyboard-first REST client for the terminal User Avatar 34 comments "Looks Good to Me" Is Quietly Killing Your Feedback Loop User Avatar 33 comments 787 tools for developers. 5 for nurses. Two weeks of tracking 14,000 indie launches. User Avatar 30 comments