- Software today is written to cover as many use cases with as many features to target as many users a possible.

- End users very often only use a tiny slice of the program's capabilities, but still pay for the entire program.

This creates a situation where the people writing software see it as a monumental undertaking to get good functional programs (it is), and end users see programs as having annoying learning curves with lots of bloat and "unnecessary" features.

LLMs do an excellent job of fixing this for end users because it allows them to easily create a program that does the handful of tasks that they normally need to use MegaSoftware for. And it's tailor made exactly for the use case. And the LLM can tell you exactly how to use it.

I can give a brief example where I used gemini to create a CAD file transposition tool that utilized a simple GUI tailor made for the files my company works with. This allowed us to forgo a (very) expensive CAD software package to work through converting our archive of files. A probably 2M LOC program could be skipped because we only needed 3k LOC functionality.

I really cannot stress enough how often this is the case, and why SWEs see LLMs as weak tools while end users see them as gods.

There will still be a need for huge software packages in the future, but I know I never again have to pay for a huge class of "here is a large solution space that covers your small scope problem" software.

To bring it home, loveable understands this, an sees that the futures has lots of non-tech people "writing" software. Standard IDEs are not the tools your mom will use to make a "Friends and family birthday reminder" app.

if lovable ever starts versioning those moves, storing reasoning behind edits, even lightly, u got a time-series of product intuition across thousands of users. that’s applied decision memory.

there's a window here to become the place where product sense gets archived and replayed.

All other software?

I'm afraid I stopped believing the author at that point...

Right now, except for some hyperscalers, any similar service has integrated their deployments to some hyperscaler which means any day 2 operations will happen in someone else's computer (supabase, azure/aws, etc). On top of that, you have third party services that you need to integrate and manage their pricing plus auth. That alone is another challenge. Let's not even start with stateful data and migrations which is almost non existent.

The main problem is these tools don't tackle day 2 operations so it will be handled to some developer to make it happen which means exporting your code to some VCS service which I think it's only github. Right there, it's a threat for lovable and others. On top of that, there's not a real feedback loop between manual integration (external dev making it prod ready) and keeping the MVP workflow. Also, there's no real way these services can say "you are free to touch these components without breaking incompatibility with our system, anything else here be dragons".

In other words, You need to own the ecosystem to make more money. Funnel the capabilities to your own ecosystem.

The comments on the Add Ons are spot on, I think:

“Lovable is creating lots of new software founders who will eventually spend lots of money on vendors. That money will flow, but Lovable currently captures zero of it.”

Having a Lovable App Store sounds like an excellent tool.

What are people trying to build where they are getting stuck at 75-90%?

- The churn from companies like lovable is indeed very high, and user frustration is high also.

- There are sub-niches available. Building internal tools is not the same as landing pages is not the same as saas. In the previous website builder market, different players (webflow, squarespace, wix) found and dominated a sub-niche

- The market is way bigger than anyone realizes. Today hundreds of millions for basically early adopters and highly tech-savvy users. This tech can and will go mainstream

- A huge issue with lovable, solved by others like mocha and replit, is the app backend. Lovable took a shortcut and partnered with supabase but that deal will not last. Supabase is losing big on their free tier (had to raise 200M to support it) and both want to capture the margin from the customer. There will be a reckoning.

AI companies are going to be working really hard to ensure that users do not bypass their chat interface because AI APIs don't provide much lock-in factor for them.

myth (a) - software engineers mostly work on software for consumers reality (a) - software engineers mostly work on software for enterprises

myth (a) - it's just crud reality (a) - it's crud but with a bunch of business rules behind it that ai can't grasp

every other shiny 'saas' that's not the reality of the majority of software out there.

However, it also squishes everything into one JS file, making it unwieldy for anything moderately complex. After I fell off the happy path (integrating onnx was basically impossible), I had to spend a fair amount of time reworking it.

I’m probably not the target audience though. And I got the end result faster than I would’ve, and it’s better looking.

I fully support vibe-coding in corporate env., plese bring more :D

The next generation of apps isn’t going to look like the previous gen. No beautiful UIs and fancy CSS. No UI at all.

Instead, everyone will have some kind of platform like Cursor, but instead of just coding, it’s for everything.

Subscribing to new services for your AI to use will be the equivalent of downloading apps from an AppStore to your phone.

Then you can just say things like “fuck this person! AI, give me an OSINT profile of this Redditor!” and since your AI has the osint app it compiles the info instantly and says “here, damn”. No need to open an app, just straight info into your brain as quickly as possible.

AI has clearly made us tired of googling endlessly for info on random websites, so why are we still opening up apps to do various tasks? Because we want to see pretty interfaces? Get real. It’s time for the UNIX philosophy to go mainstream. Start thinking of how your product can minimize time to satisfaction, graphical interfaces get in the way of satisfaction.

The only problem is we currently don’t have a single unifying platform like an iPhone or something to consolidate a user base, but it will come. Start planning for that day so you can launch new services on day 1. It will be a gold rush.

And in the end, a lot of people will find they will struggle with coming up with good AI app ideas, because 80% of their idea was just putting a pretty interface in front of something complex. That’s how you know it was mostly a bad idea.

I wonder what will happen after the honeymoon is over - after people realise that software development is not about writing new exciting code but maintaining things that should have been replaced years ago that are now too important because other people depend on it.

> I remember we were building a micro-app like that and it took at least a month, now it takes 3 minutes.

...please, statements like this have the power to invalidate the rest of the commentary. in 3 minutes you can complete a few prompts not nearly enough to write a piece of software the allegedly takes 3 months to do.

In previous roles, we either used some SaaS platform and would end up designing features based on the limitations of the tools, or we'd spin up a team to roll our own tailored solution. (or, God forbid, use Oracle and pay consultants a small fortune to do it for us).

With lovable, our CTO can validate assumptions and iterate on their own. Even if the code was absolutely garbage and we deleted all of it, this alone saves us a ton of man hours per feature. There's an entire lossy communication loop that's been removed.

Now, the code is only ok. We generate API clients from openapi definitions but it will struggle to properly orchestrate them. It will absolutely not have sane defaults anywhere, and will abuse the "any" type.

You still need a human in the loop, but my back of the napkin calculation is we'd have to hire two full time developers to do the work it's been doing for us.

Obviously positioning, who they're positioning against, how they communicate that, the level to which they're known amongst the market etc all feed in to this, but that'd be a decent starter for ten.

This is an overly simplistic version of where to go with pricing for a brand like this, but that's where I'd begin with creating pricing for them.