Then as soon as their agent hits the first bug "port already in use" they will run... Any brave soul who remains, after spending a whole day solving similar issues back to back, will be like "The port has been freed up, my nginx proxy has been configured, my nginx has been launched with systemd and my app server too! The socket ulimit has been increased, I still can't see my app!!!" Then Claude be like "Well of course, silly human! To achieve this simple task, you would have to update your security group inbound firewall rules, duh!"
Then the user be like "Claude, we fixed everything! I cannot see my app still!" Then Claude be like "You goofball, we didn't even get round to purchasing your domain name, moving it to CloudFlare DNS and configuring the A record, CNAME and AAAA record for IPv6 in your Zone file... Not to mention the MX record. You also need to obtain a signed SSL/TLS certificate from Let's Encrypt, then modify your nginx config to install the SSL certificate... Oh then we'll need to configure your nginx to act as a terminating reverse proxy for your WebSocket connection... Oh actually before we do any of that we should set up your schema validation logic and access control logic on your app server with rate limiting and backpressure monitoring... Then we'll set you up on Git version control with a CI/CD pipeline with precommit and PR hooks to run your test suite and code linting... Then we want to keep the registration and login flow of your app real simple, like stupid simple, so we'll get you a Keycloak instance acting as an OAuth2/OIDC identity provider for authentication with an email verification step which will involve us configuring the realm and creating an OAuth client and setting up the SMTP email server... Too easy!
I’d imagine they’re already working with folks like Stripe, AWS, etc on exactly this at the moment potentially? I guess that’s where Lovable comes in. And now the money makes sense. Do the raise and become an acquisition target so one of the labs doesn’t have to do it themselves.
Yes, they will be able to do this, but it's a lot of work, and Lovable has a pretty good head start.
AWS has $100+bn reasons per year to not let that happen. As techies learned slowly through the evolution of the internet: political power > money > tech.
I think you are doing the equivalent of looking at a hockey stick graph and extrapolating to infinity on where we are headed. We are already hitting the asymptote and the line is starting to go horizontal. Theres plenty of gains to be had by current state of AI, I'm not trying to be a wet blanket. I just dont think those gains are going to be had by "the masses using AI". Its going to be highly technical people doing highly technical things at scopes and speeds previously unimaginable.
Otherwise the single prompt stuff is fodder for a million clones.
Fast food software will be cheaper (but not cheap, McDonalds is considered expensive in many countries).
The value of software will skyrocket and it will be hidden behind an API so to not be copied fast.
Most devs weren't being paid out of that.
I can't bring myself to be bullish or bearish in such broad strokes.
Over the years, I have met and worked with a number of people who were "non-technical", but who nonetheless built their own internal rough software tools with a cobbled-together combination of spreadsheets and SaaS services, connected by something like Zapier. They are a particular kind of person, but I would not call all of them them "technical". They are experienced in their business domain, are detail-oriented, and are persistent in making improvements by any means they could.
I have seen those people be supercharged by AI app builders like Replit and Lovable, even if I don't personally have a need for either.
This might be a matter of definitions: Is such a person "technical" because they value systematizing human processes and put effort into it? Or is such a person "non-technical" because they are not experienced in software engineering best practices, or programming in the conventional sense?
In addition to the nature of the user, I suspect the fulcrum that success and failure rests on for these kinds of apps and tools is long-term maintenance. How frequent? How involved? How breaking are the changes? On this topic, there is a quote I think about a lot (paraphrased, and I forget who said it, or I would credit them):
>AI app builders mean that anyone can experience the joy of building software, but also that they will experience the joy of maintaining software.
Doesn't matter how many Lovable clones there are. Everyone knows the name Lovable.
This caters to the overwhelming majority who cannot use tools like Claude Code or that prefer an all in one solution.
Open source models only help Lovable improve its own margins. They can stop paying the Anthropic or OpenAI tax and tailor the models to exactly their use case and UX.
not really. maybe last year.
That's AI hallucination.