Low-Code/No-Code Design
Aleksander Jess, Former Copywriter | | Updated | 2 min read
The brief
This episode highlights expert insights on Low-Code and No-Code Design, exploring its impact on modern design processes and efficiency.
The video loads from YouTube (youtube-nocookie.com) after you press play. Watch on YouTube
Key takeaways
- A minimum viable product (MVP) that costs $1 million shouldn't be called one. An MVP exists to validate an idea as soon as possible.
- A common pattern now is to validate an idea with no-code tools, then rebuild it "the old school way" once it is validated.
- The limits of no-code are a weak objection, because an MVP is meant to be limited and test only core functionality.
- For the same or a smaller budget, no-code makes it possible to ship a minimum lovable product (MLP), with the money saved on development going into design.
- According to Iza, Order Group uses Webflow so that clients looking for MVPs get a professional visual identity faster and at limited cost, even though 80% of the company are developers.
What the video covers
In the second episode of Everything in Order, the guest is Iza Mrozowska, then Head of Design at Order Group. After a short personal introduction (kitesurfing and snowboarding), the conversation turns to low-code and no-code, which she supports.
Her case rests on what an MVP is for: validating an idea immediately, and developing it further if it works. A product built on a large budget that finds no product-market fit means the money is lost. If no-code stops being enough as the product grows, the team has still gained traction and the first-mover advantage.
On tools, Retool is her favorite and one of the most versatile. She also points to Product Hunt's Golden Kitty awards, where most of last season's winners were no-code tools with AI built in. One of the standouts was toddle, a visual app builder that resembles Webflow and aims for good front-end quality.
Playing devil's advocate, the interviewer quotes the claim that no-code is "somebody else's code limiting you". Iza answers that an MVP is limited by definition, so she sees the difference elsewhere: a limited MVP or a limited but lovable MLP for the same or a smaller budget.
The last topic is a design talk she gave in Kraków in 2024 about Webflow and other no-code web builders, and why a company where 80% of people are developers uses Webflow.
Questions answered in this episode
Why use no-code for an MVP?
Because an MVP should validate an idea before a large budget is spent. A product built for a big budget that finds no product-market fit loses that money, while a no-code version can be developed further if the idea works.
Isn't no-code too limiting?
An MVP is supposed to be limited and test only core functionality, so the limit matters less than what the budget buys: with no-code, the same money can produce a minimum lovable product.
Which no-code tools come up in the episode?
Retool, Iza's favorite, and toddle, a visual builder similar to Webflow that was one of the Golden Kitty winners.
Why does a developer-heavy company use Webflow?
Iza explains that clients who want an MVP or a faster concept validation get a professional visual identity at limited cost and in less time. She covered this in her Kraków talk.
Let's work together and shape the future
Contact us