I’ll cut to the chase. There is no "best" no code app builder. However, for non-tech founders who want to
create an app without coding, here’s what I’d recommend as the safest option: For web: Bubble For mobile: Draftbit If you think that’s all you need, links
are in the description, go ahead and click into them, I wish you the best. If you’d like to hear my rationale and get
some advice from a humble app developer, keep watching. I’d like to share how I think non-tech founders
can approach no-code app builders to maximize short and long-term gains. They are incredibly useful, but even the best
tools need good strategy and execution. And that’s what I’d like to talk about. In case it isn’t obvious, I’m a fan of
no code for non-tech founders. The idea of people without technical knowledge
developing their own software from scratch is amazing. Before, if you wanted to build a software
MVP, you’d have to pay a developer or learn to code yourself. Then realize it was way too hard and pay a
developer anyways. With no code app builders, you can truly build
your own MVP and validate it for a fraction of what engaging a professional would cost. Here’s the thing, though: There are a MILLION
no-code app builders out there. All of them lead to an MVP. Then what? What do you want to do after MVP? Knowing early on will help answer the following
question: How do you choose a no-code app builder? But Adrian, you already recommended no-code
app builders at the start of the video. Yes, I did. I’ll explain myself before the end of the
video. For now, you’re the one who’s getting
this project off the ground. Whose opinion actually matters at this stage? Here’s a hint. I'd like you to ask yourself what you foresee
happening after getting your idea validated. Do you want to keep working on development
yourself? Do you just want your damn MVP, never mind
what happens after? When you really think about what you want
and how to get there, you own your decision. You also gain valuable insight into how to
deal with developers later on. Yes, like it or not, developers will still
be part of the picture for many, even those going DIY. Again, more on that later, Let's cover the outcomes a non-tech founder
might foresee, and what features they should look for in a no-code app builder. First use case: I just want an MVP as fast as possible Well then, you’ll want a no-code app builder
with the smallest learning curve that still offers the functionality you need. The good news is that for most MVPs, you won’t
need anything fancy. Most no-code app builders will carry you to
the MVP stage. So it really goes back to the smallest learning
curve. Things to look for: The simplicity of the app builder’s interface
A promise that what you see is what you get Lots of common templates you can modify
Whether it provides its own hosting and database support
Ample and comprehensive tutorials in text and video formats
Easy publishing on app stores for mobile apps Something this simple shouldn’t be too expensive Advantage: you get to MVP fast, which means
you test fast and validate fast. Disadvantage: if an idea is validated and
you want to start further development, you’ll have to move to a new platform and start all
over again. My recommendation: Adalo for both web and
mobile apps. Second use case: I want to iterate beyond MVP myself Time to turn your app from a valid experience
to a loveable experience based on user feedback. You know it works. You just need it to work better. Now, I say ‘just’ as if it’s a walk
in the park, but from here it gets harder. You’ll be dealing with more complicated
logic and workflows, and progress can feel non-existent at the start. Ask yourself if you really want to be the
person doing all this. If yes, you should start right: go with the
no-code app builder that offers the most functionality. The features to look for: Ability to create extensive user flows
An extensive library of plugins Built-in backend support, failing that
Ease of third-party API integration (especially payment gateways and databases)
Allowing for collaborators Allowing for custom domains
Built-in SEO tools Frequently updated backups
Native app support for mobile apps Frequent product updates from the development
team Advantage: you won’t be limited by the platform’s
capabilities for a long time Disadvantage: the platform will be limited
by your capabilities for some time. It will have the steepest learning curve and
you’ll be asking lots of questions and looking up what other people have done. My recommendation: Bubble for web and Draftbit
for mobile apps. Regardless of use case Look for strong community and vendor support Here’s an open secret: Developers don’t know everything about the
software we use. We don’t have to. We learn what we need when we need it. If you’re going with a no-code app builder,
that’s what you’ll be doing. We gravitate towards software with a large
community of users and good vendor support. What we don’t know, we can ask! These are sources we like to check: official FAQ
official YouTube page official tutorials
official forums dedicated subreddits
general no-code subreddits Always go through the official FAQ; it gives
a good idea of whether the platform prioritizes user-friendliness or functionality. Make sure there are ample tutorials and active
message boards. If you notice staff members going into public
forums to engage with users, that’s a great sign. Here we see Draftbit’s co-founder addressing
complaints on the no-code subreddit. What if I’m not sure what I want to do post-MVP? It’s not ideal. But it’s definitely something you can decide
on later. Or the market will decide for you anyway. In the meantime, I’d go with the safest
choice: the one that provides the biggest potential for product development, whether
or not you choose to use it. For web: Bubble For mobile: Draftbit For some founders, even if you use the best
options, you will squeeze out all the value no code development can offer your project. That’s when you will truly understand… The limitations of no-code app builders See, with software development, you always
get what you pay for. With no code, you pay less money Instead, you pay in other ways. One, A LOT More Time and Effort
Don't expect it to be as easy as learning how to use Canva. Software development comes with many moving
parts and its own vocabulary. I can’t remember who said it, but software
development is not a coding problem, it’s a thinking problem. What no-code app builders have done is remove
the need for coding. That’s a huge obstacle out of the way, but
what’s left to do still needs a lot of time and effort from non-tech founders. You still need to think like a developer. It might be fun eventually, but it will be
painful first. This is why having a strong community and
responsive vendor is super important. You’ll need it. Two, No Protection for Intellectual Property None. Everything about your app can be copied. In fact, if it's any good, it probably will
be copied. That’s the nature of no-code app builders. Not a big deal when you just want an MVP or
if your app is a minor extension of your business. If you want to start iterating a validated
idea into a full-fledged money-making app, you’ll be a lot more protective of your
software. And the sad truth is that it cannot be protected. It’s like sharing a fridge in the office
pantry. You can label your food, but if someone wants
to steal it, there’s nothing stopping them. Three, Performance Will Always Suffer
It can be fast or it can be complex, never both. When I say fast and complex, I mean fast and
complex for a no-code app. It’s actually still kind of dogsh*t No code app builders need to work for everyone. This means tens of thousands of different
ideas. There is no way to cater to that level of
variation without sacrificing performance. As your app gets bigger, it simply will not
run as fast as it could on a tech stack chosen just for it. Sometimes, it’s not even the platform. Sometimes, it's poor early design choices
that cause bottlenecks. As people, we don’t know what we don’t know. Without the experience to judge how big an app might grow, non-tech founders can easily find themselves in a situation where whatever
they built on day one is unusable moving forward. Where to Go After Outgrowing No-Code App Builders For these reasons, every validated idea that
keeps growing beyond MVP will eventually demand more than a no-code platform can offer. The good news is that If you’re already
satisfied with the app, just keep maintaining it. You’ve created a successful business with
a technical product by yourself. Well done, truly. If you think the idea needs further development,
time to graduate to actual coding. This is the perfect time for an app agency
like Upstack Studio to step in and take over product development. We offer all the things no-code app builders
still cannot provide. In fact, I have to share one last use case: Pay a developer to create a no-code MVP I mentioned earlier that developers don’t
know everything about the software we use. Our strength is in learning and applying significantly
faster than non-tech people. Whatever you can do on a no-code app builder,
believe me, a proper developer can too. Like ten to twenty times faster. It won’t be free, and the idea may still
fail, but you can go to bed, wake up and your MVP will be on the table next to your morning
coffee. And it's still nowhere as expensive as getting
developers to build an MVP with a proper stack. Also, an actual developer can use low-code
app builders, which are much more versatile but out of reach for non-tech founders since
they still require coding. Upstack Studio doesn’t personally offer
this service. We think we are better suited to fleshing
out already validated ideas. All the app builders we recommend officially
offer the services of platform professionals. You get the assurance of backing from the
vendors, and you get cost-effective technical expertise for your MVP. Links are in the description, I make no money
from this, I recommend you just take a look and think: would this help me achieve my goals
faster? If you just want an MVP as fast as possible,
and you don’t mind paying a little for it, this is worth checking out. Takeaways for Non-Tech Founders Going No Code Ask yourself now what you plan to do after
validating an idea with no code Go with the safest no-code app builder if
unsure Look for support from the vendor and a community
of users Accept that limitations come with even the
best no-code app builders Engage a professional once these limitations
stall your app and your business Alternatively, engage a professional from
the start to get to MVP stage stupidly fast That sums up our thoughts on how non-tech
founders should approach no-code app development. We'd just like to end by wishing you the best
of luck on your journey. As developer, I love working with non-tech
founders like you. You're curious and committed, and you align
with Upstack Studio’s philosophy of going lean in the early days (which is a nice way
of saying we're all cheapskates). If and when you do choose to approach a developer,
it will be with a valid idea. And the idea makes the app. No developer on Earth can turn a poor idea
into a good app. But a decent developer can turn a good idea
into a great app. So go forth, my non-tech children, and multiply
those app templates. Flood the web and app stores with crappy potatotypes. Exasperate beta testers with your buggy apps. Then bring me the ones you’d like to develop
further. For those without technical knowledge who
want to create an app without coding, here’s what I’d recommend
For web: Bubble For mobile: Draftbit Before you go multiply, please like the video,
subscribe and hit the bell icon. More content on app development for non-tech
founders coming up, and I’d like you to
