Well, I made a nocode system for a friend that solved all of his production problems and increased his production 10x over 2 years. Might not scale but for him does not have to, and it was a game changer.
All No-code tools owners are building it and scale it up to be able to sell it later with as much profit as they can get, then they get out of it, and the new owner will screw it, then the customers will hit the wall.
I come from both perspectives. The points made by the original video is very good. But the point of understanding that it is an education process that helps you put together the proper structure to maintain your company and evolve all of his processes, including the tools you use to scale, is also important. Many no code/low operations are filled with people who know how to use those tools. Hopefully people will have an open mind to listen to both videos, independent of each other and gain the perspective they would need to make the right choice for their solutions
PS, many traditional developers, take non-technical founders bay on local for a ride. They be great the quality of those tools while they charge them exorbitant fees to fix something that the founders are panicked over and want yesterday.
A few things here to unpack. The statements are strong. However she is not a typical no-code user. First she has coding skills, second, with every decisios, she says 'hire a dev'. Now, I am not against that, but this is not feasible for many who turn to no-code. The video almost breath, what I call 'a status quo propaganda'. This goes like this. We say we invent something, but at the other end we try to discourage any real change from happening, so long as the audience believe it is possible, the outcome will be the status quo'. Anyway, with the dazzling promise of big money, hiring devs is not a straight forward process. But, I like your comment on how a platform, if allowed, could overtime solve its own limitations. Building Toddle in Toddle is a great statement. I love it, because I have yet to fully grasp how powerful that is. It resembles nature, an organic way of doing., growing, evolving. Now, I don't have the industry experience which gives me a) a unique perspective, b) absolute freedom of original thinking, c) the ability to work towards active change. Why would we build functionality that is standard practice, like signup forms? They do not define the unique capabilities of an app or an idea. I already have a minimum of 5 things I want to build. Given the huge effort it already has taken, I came to the conclusion, that I would develop for flexibility. I have great experience working with toddlers 😂, that gave me the ability to break down complex things in understandable bits. A skill that can be applied everywhere. Once the look and feel comes naturally, then the challenge is coming up with complex algorithms. I have been part of many platforms as an early user. Thus, hitting roadblocks is an all too familiar thing. If we want to leap forward, no company can do without the commons. It is in the ecosystem that great promises await. The tragedy of the commons is that contribution to it is seen as inferior to paid contributions. It isn't. Potential is nothing without manifestation. In the commons, here building the flexible ecosystem, will in the end give rise to complexity and integrations. It is the difference between short time thinking and long term visions. Toddle might be the tool to shake up things in that space. I see potential for schools working with it. To give prospective users a better feel on how to build a tool or app, you need the most basic workflow, how to abstract the logic, and even how to generalize functionality. Code generation and looking at it, should not matter.if the browser and user can correctly work with it. Any changes should be done in the platform it self. This is where the maintainability of the platform should lie and be the big selling point. Having an app that can't be maintained is quite useless, because it is a big part of the life cycle. When I first opened Toddle, I thought 'yikes' html and CSS. But using the platform it became a refresher and intuitive feel about what the attributes do to your design; to the point , that I now think 'yeah let's toddle'. I already switched from building pages, to components. Because, when you have figured out something, you don't want to figure it out again. If you're not a pro, that's likely to be the case. The ease of making components, learning along the way, and worry later about assembling the bigger parts. Anyway, to conclude. Toddle build in Toddle is the best statement. It already showcases its capabilities, and from that it can only evolve to be more diverse in ideas that sprout out of it. I am willing to take that journey with an open mind.
I would assume NO CODE to be: no experience, no training (learning curve, yes), no high level design, not very many options, not for original unique designs, not your be-all end-all platform. Works for me!
That is usually what people associate with no-code. That is actually the primary reason why we recently decided to stop using that term to describe toddle.
Got her video in my TH-cam feed, and decided to give it a watch, though I knew what to expect - saw similar videos/posts before. Here’s my comment I left under @codingwithdee video (though I didn’t get a reply, unsurprsingly): As a seasoned Webflow developer, I saw this video in my feed and immediately was upset by the clickbaity title - I decided to watch the full video and here are my thoughts:
1. The video should be renamed “No Code MOBILE App Development is a Trap” - you can build web apps and even scalable ones. The title is a clickbait and I really hate it. Some people might call me “nitpicky”, but Dee never mentions “mobile” in the description and title - even in the video, for the most part. She makes no-code look bad in general. I believe it’s a really bad thing to do. 2. While I didn’t have personal experience with building mobile apps, I do agree with Dee on one point - these platforms aren't that much honest in their marketing. I think it’s the issue even with non-mobile no-code related platforms, sadly. That being said, it’s not like they are blatantly lying - you can, in fact, build production-ready apps with these mobile app no-code development platforms. However, they do not tell you about all the nuances you might encounter such as lack of customization (which is fine, even Dee admits it). So calling “no-code mobile app development” a trap is a stretch. 3. No-code in general isn’t bad as Dee tries to make it look like - moreover, as I’ve mentioned before, she talks SPECIFICALLY ABOUT MOBILE APPS. I use Webflow and it is amazing! Does it have limitations? Obviously, as any other platform, but you can build so much with it - by utilizing 3rd party and integrated apps too, you can build web-apps even. A popular combo stack is WWX - Webflow + Wized + Xano. You can build production and scalable apps. Sure, not everything can be built with this stack or no-code platforms in general, and it makes sense. It’s not a panacea. 4. Anyway, people must do prior research and learn about limitations of tools they use. It’s hilarious to see people coming expecting a panacea from every tool they use - then they go to Reddit and Twtiter and start shitting on a tool. I’m not saying that Dee lies about stuff in the video - she does not, and I believe here, I’ve heard about no-code mobile app dev platforms, they aren’t astoundingly great, but they do the job for the most part. Many apps can be built with them. Not all, not super custom, yes. But still many. And I believe it’s amazing. Sure, these companies kinda lie in their marketing about possibilities, but it’s not like these tools are garbage or a TRAP. 5. I’ve seen many people complain about Webflow on Reddit and (a few times) in Telegram group chats related to the tool, that it is bad, trash, garbage, and so on. Turns out, in 99% of cases, that these people didn’t learn about the tool, didn’t do prior research, just deep dived into it and expected everything on a platter without moving a muscle - hilarious! These tools, Webflow too, aren’t ideal, but the amount of possibilities they give to the users is really empowering. I have way more thoughts about this video and similar ones - maybe I’ll make a video addressing them one day, but for now I think this long-ass reply is enough. I just want to add that coders should stop gatekeeping development from other people - no one is stealing your jobs, and even if they do, then you need to step up your game and adapt. Gosh, the amount of elitism is insane. The comments just reek of it. Disgusting, honestly. P.S: Keep in mind, that I’ve talked only about APP DEVELOPMENT here - there are so many other things like websites/frontend development, automation/integrations (n8n is amazing!), etc.
Here is the things, I agree with most of what she said. I've built websites using WordPress, Wix, Webflow etc and also write code and I think most nocode projects hit a wall at some point unless you don't have much complexity. When it comes to complexity, from low medium to small, they are great and can be OK but from there, I wouldn't advise anyone to use it...
1. Not sure that's true any longer. You can build whatever you want in toddle and publish it as a native app with a wrapper. 2. The honesty issue is a thing. Platforms need to be honest about where they fall short. 3. We challenge you to find an app with a frontend that can't be built in toddle :) 4. Agreed. 5. Also largely true. We need to make programming more collaborative to reduce the workload on devs so they can focus on more complex problems than changing the border radius on a button.
Great reply. "No Code is trap" is the kind of video I would have made had I decided to give up after a couple of days of looking into no-code and being riddled with coder scepticism & frustrations and gone looking on Reddit and for blog posts to support that initial conclusion. However, I didn't do that - I stuck it out in the belief that if it was "real", the benefits would be worth it and I can tell you it has been worth it and my experience has been the polar opposite of hers. She makes some relevant points, especially about the mis-marketing with some no-code tools of making it sound like everybody can do it, you can learn it in an afternoon and build the next unicorn app in a week in your spare time - this is nonsense, as is the 20X-50X speed of development promise compared to code - maybe after a year mastering a tool you can manage 3-5X compared to code - still a massive benefit. For me, as someone whose done it for over 30 years, no-code has given me my love back of software development, something I'd lost with coding. And of course Toddle is the best of the lot!
No-code surely is the future, but only for coders who can see what is going on. Or certainly for those who are determined.. just one push. If 1 project is made using No Code.. the person wont stop before 100. Specially Me.
3:06 I think this is exactly the problem with low/no code. It provides the ability to do a LOT less than you can do with code and there's STILL a significant learning curve. I see some comments mentioning it not being good for mobile etc etc. But in my own experience (using a low/no code platform to build a very complex application for the better part of 3 years), the real issue comes in when requirements change. All the weird, janky, loophole-y things that these platforms require in order for them to work come crashing down when there's a change in requirement (even if these things aren't bad in themselves, they are sometimes EXTREMELY niche, and completely non-obvious). The point is not necessarily that the platforms can't work but the time investment to learn it, figure out its weird idiosyncrasies, and EVEN have the dev team of those platforms directly work on requested features (it may seem unfair but the immaturity of these platforms DO count against them in more serious projects) - that time investment just generally isn't worth it for what are usually non-transferrable skills. Ultimately to get what you want, to REALLY get what you want, it requires skills learned outside of the platform. Oft times, coding skills.
toddle is based on the learnings from the popular code frameworks like React, Vue, Svelte etc., meaning developers can jump right in using their already acquired skills. And toddle is built in toddle, so complexity is not really an issue here 😊
We are using Webflow to pixel perfect design and then we export the code, and this is exactly what we want. Webflow code is optimized and perfectly readable
I think no code tools should consider its users as layman as possible instead of considering them as experienced developers this will make life much more easy
I think clean code would be important if you don't want to be locked in by vendor. If you can download the "clean" code you can develop it any time even if the platform die.
This has come up a lot. Pretty much exclusively from people who have never inherited a large codebase. There are a few platforms that have attempted this, but the feedback has generally been that it doesn't work. Like in the original video. Instead toddle is going open source, so even without toddle the company you can still self host everything: toddle.dev/blog/toddle-is-soon-open-source
@@toddledev this info will make me check out toddle an hour from now. This is the first I'm hearing about toddle, but I really your response to the lady's video.
I've been watching 10rs of coding tutorial, but was really get me nowhere, only since doing after no code, I can literally started understand it something behind code...I just hope this must be goes even to experienced coders aswell...
Softr just did their best to clearly demonstrate why no code is waste of time if you want to actually build anything outside of a very small application or hobby project. $167 per month for 100 users? 😅 All these no code platforms are just preying on those who don’t have the technical coding skills, locking them in, and then rocketing the pricing. Won’t be long before Toddle follows suit, I’m sure.
toddle is also in the process of making the runtime and editor open-source which means that if you don't like our prices you can host everything your self toddle.dev/blog/toddle-is-soon-open-source Our founder also recently wrote about why, going forward, we have chosen to no longer refer to toddle as a no-code tool toddle.dev/blog/no-more-no-code
Well first and foremost looking at the video the original video content creator produced - she is definitely not being 100% honest - she is definitely not a new developer who has never created mobile apps - if that was the case she wouldnt be talking about custom widgets etc. Do Check out her other videos that clearly demonstrate her experience as a software developer. So here is the thing as much as folks may or not like it - Low Code/No-Code is here to stay alright but its not to be misconstrued to be hitting developers below the belt because that can never happen - code and coding can never stop or be replaced. So the developer would fancy making his/her frustrations be vented out with messages that decry Low Code and No-Code Platforms per se. There is no such thing that software programmers need to worry cos these LCNC platforms are not going to replace you ever but probably will make your work a lot easier for less mission critical applications that need to built within a short duration of time with less resources.
If you mean the OP's thumbnail that says "no code will fail," I agree. A large percentage of web pages on the internet were built with no code, so I would say that no code has already succeeded. And no code is exactly what most startups need instead of paying huge amounts of money for traditional developers when they don't even know if their idea is profitable.
It is subliminal marketing. You now thinks of toddle as different from the platforms mentioned in the video. This subtle neural programming is making you want to sign up for toddle. It is also possible he just forgot to uncheck mirroring again.
AI will definitely play a big role in software development in the future but there is nothing today that indicates that it will replace software developers.
@@toddledev rsssss. street performer. You are right! Many people have no ideia how business works. Even for the internet to operate, you will depend on your ISP
@@victormor555d Paying for a good engineering team can bankrupt a small business or startup and most of their needs can be met with no code. Also, there is a huge shortage of excellent, experienced programmers to hire for such a team. I think most companies have to rely on a mediocre team but even they can be expensive.
“Code looks wrong” - comming from someone with no flutter experience at all says … well nothing😂 Tbh id never use nocode and I rly dont believe in a future of nocode. But her takes were off in parts and I really like ur take and the transparent way u talk about this. Again I dont see a future for no code. It doesnt safe time for developers - as its not for devs. But it takes a lot if time for non-devs to get into it and as those people lack the base knowledge off anything they even with nocode often fail to create a usable product. Especially in less time then a dev could. In the end it makes more sense to hire a dev and let him do a proper job.
toddle is different. It is a “nocode” platform built for devs. Its primary goal is to make web development more efficient. We are building toddle in toddle which is why we can do so much with a team of only 8 people.
Are toddle users called... toddlers?!
oh no XD
Well, I made a nocode system for a friend that solved all of his production problems and increased his production 10x over 2 years. Might not scale but for him does not have to, and it was a game changer.
I'm sure you did.
All No-code tools owners are building it and scale it up to be able to sell it later with as much profit as they can get, then they get out of it, and the new owner will screw it, then the customers will hit the wall.
Not all. That is why toddle is going open source
My bank account 10000% disagrees with her video title.
I come from both perspectives. The points made by the original video is very good. But the point of understanding that it is an education process that helps you put together the proper structure to maintain your company and evolve all of his processes, including the tools you use to scale, is also important. Many no code/low operations are filled with people who know how to use those tools.
Hopefully people will have an open mind to listen to both videos, independent of each other and gain the perspective they would need to make the right choice for their solutions
PS, many traditional developers, take non-technical founders bay on local for a ride. They be great the quality of those tools while they charge them exorbitant fees to fix something that the founders are panicked over and want yesterday.
There's always two perspectives which is why discussion is healthy and should be encouraged.
A few things here to unpack. The statements are strong. However she is not a typical no-code user. First she has coding skills, second, with every decisios, she says 'hire a dev'. Now, I am not against that, but this is not feasible for many who turn to no-code. The video almost breath, what I call 'a status quo propaganda'. This goes like this. We say we invent something, but at the other end we try to discourage any real change from happening, so long as the audience believe it is possible, the outcome will be the status quo'.
Anyway, with the dazzling promise of big money, hiring devs is not a straight forward process. But, I like your comment on how a platform, if allowed, could overtime solve its own limitations. Building Toddle in Toddle is a great statement. I love it, because I have yet to fully grasp how powerful that is. It resembles nature, an organic way of doing., growing, evolving. Now, I don't have the industry experience which gives me a) a unique perspective, b) absolute freedom of original thinking, c) the ability to work towards active change. Why would we build functionality that is standard practice, like signup forms? They do not define the unique capabilities of an app or an idea.
I already have a minimum of 5 things I want to build. Given the huge effort it already has taken, I came to the conclusion, that I would develop for flexibility. I have great experience working with toddlers 😂, that gave me the ability to break down complex things in understandable bits. A skill that can be applied everywhere. Once the look and feel comes naturally, then the challenge is coming up with complex algorithms. I have been part of many platforms as an early user. Thus, hitting roadblocks is an all too familiar thing. If we want to leap forward, no company can do without the commons. It is in the ecosystem that great promises await. The tragedy of the commons is that contribution to it is seen as inferior to paid contributions. It isn't. Potential is nothing without manifestation. In the commons, here building the flexible ecosystem, will in the end give rise to complexity and integrations. It is the difference between short time thinking and long term visions. Toddle might be the tool to shake up things in that space. I see potential for schools working with it.
To give prospective users a better feel on how to build a tool or app, you need the most basic workflow, how to abstract the logic, and even how to generalize functionality. Code generation and looking at it, should not matter.if the browser and user can correctly work with it. Any changes should be done in the platform it self. This is where the maintainability of the platform should lie and be the big selling point. Having an app that can't be maintained is quite useless, because it is a big part of the life cycle. When I first opened Toddle, I thought 'yikes' html and CSS. But using the platform it became a refresher and intuitive feel about what the attributes do to your design; to the point , that I now think 'yeah let's toddle'. I already switched from building pages, to components. Because, when you have figured out something, you don't want to figure it out again. If you're not a pro, that's likely to be the case. The ease of making components, learning along the way, and worry later about assembling the bigger parts.
Anyway, to conclude. Toddle build in Toddle is the best statement. It already showcases its capabilities, and from that it can only evolve to be more diverse in ideas that sprout out of it. I am willing to take that journey with an open mind.
Thank you a lot for making this reaction video. It always really helps to have a second opinion on things.
Glad you enjoyed it!
Whichever tool perfects no code and pro code is the future ✨️
We think so too.
@@toddledev✨️
I would assume NO CODE to be: no experience, no training (learning curve, yes), no high level design, not very many options, not for original unique designs, not your be-all end-all platform.
Works for me!
That is usually what people associate with no-code. That is actually the primary reason why we recently decided to stop using that term to describe toddle.
Got her video in my TH-cam feed, and decided to give it a watch, though I knew what to expect - saw similar videos/posts before.
Here’s my comment I left under @codingwithdee video (though I didn’t get a reply, unsurprsingly):
As a seasoned Webflow developer, I saw this video in my feed and immediately was upset by the clickbaity title - I decided to watch the full video and here are my thoughts:
1. The video should be renamed “No Code MOBILE App Development is a Trap” - you can build web apps and even scalable ones. The title is a clickbait and I really hate it. Some people might call me “nitpicky”, but Dee never mentions “mobile” in the description and title - even in the video, for the most part. She makes no-code look bad in general. I believe it’s a really bad thing to do.
2. While I didn’t have personal experience with building mobile apps, I do agree with Dee on one point - these platforms aren't that much honest in their marketing. I think it’s the issue even with non-mobile no-code related platforms, sadly. That being said, it’s not like they are blatantly lying - you can, in fact, build production-ready apps with these mobile app no-code development platforms. However, they do not tell you about all the nuances you might encounter such as lack of customization (which is fine, even Dee admits it). So calling “no-code mobile app development” a trap is a stretch.
3. No-code in general isn’t bad as Dee tries to make it look like - moreover, as I’ve mentioned before, she talks SPECIFICALLY ABOUT MOBILE APPS. I use Webflow and it is amazing! Does it have limitations? Obviously, as any other platform, but you can build so much with it - by utilizing 3rd party and integrated apps too, you can build web-apps even. A popular combo stack is WWX - Webflow + Wized + Xano. You can build production and scalable apps. Sure, not everything can be built with this stack or no-code platforms in general, and it makes sense. It’s not a panacea.
4. Anyway, people must do prior research and learn about limitations of tools they use. It’s hilarious to see people coming expecting a panacea from every tool they use - then they go to Reddit and Twtiter and start shitting on a tool. I’m not saying that Dee lies about stuff in the video - she does not, and I believe here, I’ve heard about no-code mobile app dev platforms, they aren’t astoundingly great, but they do the job for the most part. Many apps can be built with them. Not all, not super custom, yes. But still many. And I believe it’s amazing. Sure, these companies kinda lie in their marketing about possibilities, but it’s not like these tools are garbage or a TRAP.
5. I’ve seen many people complain about Webflow on Reddit and (a few times) in Telegram group chats related to the tool, that it is bad, trash, garbage, and so on. Turns out, in 99% of cases, that these people didn’t learn about the tool, didn’t do prior research, just deep dived into it and expected everything on a platter without moving a muscle - hilarious! These tools, Webflow too, aren’t ideal, but the amount of possibilities they give to the users is really empowering.
I have way more thoughts about this video and similar ones - maybe I’ll make a video addressing them one day, but for now I think this long-ass reply is enough.
I just want to add that coders should stop gatekeeping development from other people - no one is stealing your jobs, and even if they do, then you need to step up your game and adapt. Gosh, the amount of elitism is insane. The comments just reek of it. Disgusting, honestly.
P.S: Keep in mind, that I’ve talked only about APP DEVELOPMENT here - there are so many other things like websites/frontend development, automation/integrations (n8n is amazing!), etc.
Here is the things, I agree with most of what she said. I've built websites using WordPress, Wix, Webflow etc and also write code and I think most nocode projects hit a wall at some point unless you don't have much complexity. When it comes to complexity, from low medium to small, they are great and can be OK but from there, I wouldn't advise anyone to use it...
1. Not sure that's true any longer. You can build whatever you want in toddle and publish it as a native app with a wrapper.
2. The honesty issue is a thing. Platforms need to be honest about where they fall short.
3. We challenge you to find an app with a frontend that can't be built in toddle :)
4. Agreed.
5. Also largely true.
We need to make programming more collaborative to reduce the workload on devs so they can focus on more complex problems than changing the border radius on a button.
Great reply. "No Code is trap" is the kind of video I would have made had I decided to give up after a couple of days of looking into no-code and being riddled with coder scepticism & frustrations and gone looking on Reddit and for blog posts to support that initial conclusion. However, I didn't do that - I stuck it out in the belief that if it was "real", the benefits would be worth it and I can tell you it has been worth it and my experience has been the polar opposite of hers. She makes some relevant points, especially about the mis-marketing with some no-code tools of making it sound like everybody can do it, you can learn it in an afternoon and build the next unicorn app in a week in your spare time - this is nonsense, as is the 20X-50X speed of development promise compared to code - maybe after a year mastering a tool you can manage 3-5X compared to code - still a massive benefit. For me, as someone whose done it for over 30 years, no-code has given me my love back of software development, something I'd lost with coding. And of course Toddle is the best of the lot!
Thanks for the kind words.
If you did no code for 30 years, when did you actually code 😂 Smells like bull
@@gabrielstiffler1488 yeah whatever. Read the comment again then you might comprehend what I said 🙄
@@nocodecoder4160 the attitude of a senior developer for sure. Aham
Happpend to me as well! No code you have to build your idea around the limitations of the platform and that can itself kill the product
we built toddle so that you don't have to settle
Yea you’re kind of validating her point! No code apps are limited
I am 100% validating her point.
She is absolutely right.
That is why we built toddle.
And why we stopped referring to it as a nocode tool
@@toddledev boom 💪
36 comments? I'm a bit offended. Aren't people excited to see a TH-cam reaction battle about dev topics?? 😄
Right?
No-code surely is the future, but only for coders who can see what is going on. Or certainly for those who are determined.. just one push. If 1 project is made using No Code.. the person wont stop before 100. Specially Me.
3:06 I think this is exactly the problem with low/no code. It provides the ability to do a LOT less than you can do with code and there's STILL a significant learning curve.
I see some comments mentioning it not being good for mobile etc etc. But in my own experience (using a low/no code platform to build a very complex application for the better part of 3 years), the real issue comes in when requirements change. All the weird, janky, loophole-y things that these platforms require in order for them to work come crashing down when there's a change in requirement (even if these things aren't bad in themselves, they are sometimes EXTREMELY niche, and completely non-obvious). The point is not necessarily that the platforms can't work but the time investment to learn it, figure out its weird idiosyncrasies, and EVEN have the dev team of those platforms directly work on requested features (it may seem unfair but the immaturity of these platforms DO count against them in more serious projects) - that time investment just generally isn't worth it for what are usually non-transferrable skills. Ultimately to get what you want, to REALLY get what you want, it requires skills learned outside of the platform. Oft times, coding skills.
toddle is based on the learnings from the popular code frameworks like React, Vue, Svelte etc., meaning developers can jump right in using their already acquired skills.
And toddle is built in toddle, so complexity is not really an issue here 😊
We are using Webflow to pixel perfect design and then we export the code, and this is exactly what we want. Webflow code is optimized and perfectly readable
That is a great option for static websites but not so much for web apps.
That is a great option for static websites but not so much for web apps.
Great insight here. I'm on the fence on so many tools for my idea.
There are a wealth of tools. If you are looking for one that can take your app 100% of wherever you want to go, you have come to the right place.
Man please get your mic further from you because the BREATHING is just bad
I think no code tools should consider its users as layman as possible instead of considering them as experienced developers this will make life much more easy
I think no-code tools generally do. This is why we stopped using the term all together. toddle is not designed to be a beginner tool.
I think clean code would be important if you don't want to be locked in by vendor. If you can download the "clean" code you can develop it any time even if the platform die.
This has come up a lot. Pretty much exclusively from people who have never inherited a large codebase. There are a few platforms that have attempted this, but the feedback has generally been that it doesn't work. Like in the original video.
Instead toddle is going open source, so even without toddle the company you can still self host everything: toddle.dev/blog/toddle-is-soon-open-source
@@toddledev this info will make me check out toddle an hour from now. This is the first I'm hearing about toddle, but I really your response to the lady's video.
I've been watching 10rs of coding tutorial, but was really get me nowhere, only since doing after no code, I can literally started understand it something behind code...I just hope this must be goes even to experienced coders aswell...
Softr just did their best to clearly demonstrate why no code is waste of time if you want to actually build anything outside of a very small application or hobby project.
$167 per month for 100 users? 😅 All these no code platforms are just preying on those who don’t have the technical coding skills, locking them in, and then rocketing the pricing. Won’t be long before Toddle follows suit, I’m sure.
toddle is also in the process of making the runtime and editor open-source which means that if you don't like our prices you can host everything your self
toddle.dev/blog/toddle-is-soon-open-source
Our founder also recently wrote about why, going forward, we have chosen to no longer refer to toddle as a no-code tool toddle.dev/blog/no-more-no-code
Well first and foremost looking at the video the original video content creator produced - she is definitely not being 100% honest - she is definitely not a new developer who has never created mobile apps - if that was the case she wouldnt be talking about custom widgets etc. Do Check out her other videos that clearly demonstrate her experience as a software developer. So here is the thing as much as folks may or not like it - Low Code/No-Code is here to stay alright but its not to be misconstrued to be hitting developers below the belt because that can never happen - code and coding can never stop or be replaced. So the developer would fancy making his/her frustrations be vented out with messages that decry Low Code and No-Code Platforms per se. There is no such thing that software programmers need to worry cos these LCNC platforms are not going to replace you ever but probably will make your work a lot easier for less mission critical applications that need to built within a short duration of time with less resources.
i think penpot geenrates great readable code
penpot is a design tool. It is a very different problem
bro didn't want to hear you breathing the whole time
Maybe filter out the breathing sounds next time, with headphones on it is quite noticeable when your not talking.
The swallowing noises are especially irritating.
No code low code helps much yes it good but not very good.
what a smug fucking thumbnail holy hell
Which one of them ?
If you mean the OP's thumbnail that says "no code will fail," I agree. A large percentage of web pages on the internet were built with no code, so I would say that no code has already succeeded. And no code is exactly what most startups need instead of paying huge amounts of money for traditional developers when they don't even know if their idea is profitable.
If you're so smart, why's the thing behind you backwards? 🧐
It is subliminal marketing. You now thinks of toddle as different from the platforms mentioned in the video.
This subtle neural programming is making you want to sign up for toddle.
It is also possible he just forgot to uncheck mirroring again.
@@toddledev 😱
Yes it is a trap. It is a trap that you need to pay them for their services
I don't see the point of no code. It is going to be replaced by AI.
AI will definitely play a big role in software development in the future but there is nothing today that indicates that it will replace software developers.
Point is it’s better to hook ai written code together and debug that with AI and build, instead of circumnavigate the limits of the nocode tools
just learn react and nextjs, problem solved
This is only true if you are using a no-code tool because you don't know how to code. toddle is built to make software development faster for everyone
Never base your business on someone else's business.
Not a lot of options left then.
Almost every business has suppliers.
Maybe personal trainer or street performer.
@@toddledev Skill issue, with a good engineering team you don't need to base you core business on the business of others.
@@toddledev rsssss. street performer. You are right! Many people have no ideia how business works. Even for the internet to operate, you will depend on your ISP
@@toddledev Most businesses' core tech stacks are open source.
@@victormor555d Paying for a good engineering team can bankrupt a small business or startup and most of their needs can be met with no code. Also, there is a huge shortage of excellent, experienced programmers to hire for such a team. I think most companies have to rely on a mediocre team but even they can be expensive.
“Code looks wrong” - comming from someone with no flutter experience at all says … well nothing😂
Tbh id never use nocode and I rly dont believe in a future of nocode. But her takes were off in parts and I really like ur take and the transparent way u talk about this.
Again I dont see a future for no code. It doesnt safe time for developers - as its not for devs. But it takes a lot if time for non-devs to get into it and as those people lack the base knowledge off anything they even with nocode often fail to create a usable product. Especially in less time then a dev could.
In the end it makes more sense to hire a dev and let him do a proper job.
toddle is different. It is a “nocode” platform built for devs. Its primary goal is to make web development more efficient.
We are building toddle in toddle which is why we can do so much with a team of only 8 people.
@5:10 He explains you need to code, oh well
In unusual situations, yes