I think that many existing apps with huge userbases will gradually lose users as the models become better and better. Their biggest advantage is that people don't like change, and thus having to e.g. export data from some tools etc. seems to be a hassle not worth $5 a month. But as the models get better and the quality of the output will match the quality of the established SaaS but tailor the whole thing to a single user with the ability to make any change they can imagine within minutes, and perhaps deploy to Hetzner and whatnot where they could host all of those apps for a single $5 instead, the exodus will accelerate.
On the other hand, new products will have a much harder time to gather a big userbase. Whenever I'll see a launch of a SaaS asking for $$$, the first question I'll ask myself will be how long it will take LLM to recreate it. And for most cases, I imagine that the time it will take to get 80% of what they have is a few vibe coding sessions (as most newcomers will probably have used LLM themselves to code it up).
I do think you're vastly overestimating people's ability to write software, even with LLMs, and use it in production. The average computer user does not even use a computer as their primary computing device, they use a phone. The barrier to going from idea to phone app on iPhone or Android is relatively high.
Todo list apps, habit trackers, and the like are almost a special snowflake breed. Almost everyone has some different cross-section of needs they care about, and no app is perfect for each individual. So it's natural to say "is there something that matches what I want?" and then reach for tools to make that. The world is your oyster for todo list apps. Of course, the real issue comes from data sovereignty, trust, quality, things like that. When Apple launches a new device or a new iOS feature people want, you get to see which apps will actually implement the new features or which stagnate. They're a natural avenue for vibe coding since they're so particular.
It's somewhat like the Shortcuts system on steroids.
It would be interesting, particularly for Apple, as this would cannibalize fees charged on the App Store. I imagine they could charge for use of the vibe-coding platform, but Apple hasn't been great at figuring out LLMs.
It would be cool if 3rd partly app platform could provide this functionality, but as I noted in another comment, I cannot even install my own vibe-coded apps to my own iPhone. (Without the 100 USD a year developer tax.) So I'm not sure how the architecture would work on iOS.
Vibe-coding accelerates the destruction of basic (closed-source) apps charging a subscription for features that offer little to no value whatsoever.
Second of all, all of these SaaS apps that don’t actually have a need for recurring charge probably should be paid one time. I don’t use Loom — I use CleanShot X and it was a one-time $30 payment and has a lot of great features I benefit from. I can’t reimplement it in $30 of tokens or $30 of my time.
But for an app whose use case doesn’t change and is recurring for no reason? Yeah there’s probably not much value in recurring payments outside of wanting to support the developer. I pay a lot of indie devs out of the goodness of my heart, and I’ll continue to do that.
But the value for “SaaS apps” without clear monthly costs should have always been under scrutiny.
Perhaps LLM's will force developers/companies to change their stance and to stop users from recreating what they have already created, just buy an at-a-time snapshot of their app for a one-time-fee? Probably not but one can hope.
But everyone wants us to pay $10/mo. It just isn't sustainable from a consumer perspective.
And so few actually deliver $10/mo worth of value. If 1password and Fastmail - the two most important services that control my digital life - are each $60/year, that's the standard of value other SaaS companies have to beat and very few do. The ones that do are like NextDNS where they cost $20-30 per year because the people running them aren't greedy lemmings trying to pay back VC.
And this is comparing to being subscribed many years in a row. With SaaS you can unsub and sub only when you need it again.
With your side project - a weekend of your life is invested and you will never get it back.
This is the worst use of your time if you measure it in $. If you make it for fun - sure. In all other terms it is a complete loss.
Hardly doubt that this was the 'most waste of ones time'. For one, it's not like most of us can decide to "work" for 3-5 hours on a Saturday and get any money. I play games on my pc while claude codes for me. I alt tab each few minutes and see if it needs any input. Then I can (not that I do it), read and perhaps learn from the code.
(How? Idk, I just asked it to guide me through the short hook process)
Subscription apps often have to target a wide userbase. However, most users only need a small subset of the entire feature set, and would be better served by a tailored version. This means that vibecoded apps can get away with being much less complex (specific featureset, no login etc), while still being more useful.
I have also created tools with LLMs that are exactly tailored to what I need, and still much more polished than what I could do without LLMs. Will have to think about if there is anything else I can do this with.
If the commercial provider charging you $10 a month breaks it, you also have no capacity to fix it.
Your options are: send them an email, or unsubscribe and use something else.
But if they remove a feature I rely on, I can't put it back.
If they add a feature I hate, I can't remove it.
If they jack the price up, I have no real solution to this.
If they move features I rely on from the standard tier to the 5x more expensive pro tier, I have no real solution to this.
Why, yes, this is an echo of the old argument for open source software.
In what situation would a simple script or helper app just suddenly rot away and stop working?
Of course it's POSSIBLE to vibe together a massive monstrosity of an everything-app, but that's not what the author is doing here (nor me).
cheers
We can now produce products and apps that are tailored to our own preferred ways of working.
Regardless of the cost of generating them (which can be as low as $20 per month for a ChatGPT Plus subscription) or the effort involved (sometimes less than an hour of “vibe coding”), we’ve reached a point where the resulting product can be significantly more valuable than the existing product, service, or subscription it replaces.
That’s the whole point - there’s no need for it to be a product when you can do it yourself, and it’s the death knell of products like this.
You can just use it and be content.
List of projects mentioned before: https://news.ycombinator.com/item?id=46716805
But Roberto's use-case is definitely more sane than most.
However, with a proper framework (e.g., a very opinionated design system, the ability to choose from some pre-designed structures/flows, etc.) I could very much see ad hoc creation of software becoming more widespread.
But typora is actually one time purchase and one of the rare apps that is priced well with good business model.
They have probably best RTL support and I wanted like your friend to write my own focused markdown editor with RTL support using clause and made some progress but realized that the time and cost of doing this is not worth it. I just paid typora a week ago for $15.
But I understand the point and I use Claude to hack together personal tools all the time.
Now I wonder if the maintenance cost for this type of internal system has gone down to a level where that is no longer an issue.
Here's what bugs me: I cannot permanently install my apps to my iPhone because of Apple's walled garden. I need to reinstall every 7 days and constantly re-confirm that I am a "Trusted" developer.
I know I can pay Apple 100 USD a year for a developer account, but I bought this phone outright 7 years ago, I own it. (Obviously, I clearly don't in this case.) /rant
Does that work better for maintainability than letting it decide on its own what the architecture should look like?
If so, what is your setup/workflow?
The cynical approach would be to make the product hard to leave. But that just means you've built a trap, not something people actually want. Eventually they escape and hate you for it.
The test I use: would people recommend this to colleagues even if there's no referral incentive? If the answer is no, I'm probably building something people tolerate rather than something they value.
Where I could see some really interesting results is the marriage of the two. For example, you have a solid data structure that an LLM can generate infinite custom views from.
And I have first hand knowledge of well-known companies building their own tooling because the SaaS offerings have a bad price/feature ratio.
The recommendation thing is a nice benchmark, but if you're building hyper-specific tools - why would people recommend them to anyone? If you build a tool for an accountant that does some very niche thing only they're bothered by, why would they recommend to the analyst or receptionist in the company?
I replaced a whole bunch of these with one shot prompts for shits and giggles.
I vibe coded a webapp that I was paying yearly for and the version I made does everything I wish the app I paid for did as it's 100% personalised to me.
I've been thinking for awhile that this is going to be the future and I'm already starting to think of more things I will create.
Building all the software you use yourself, whether by hand or by vibe coding, cuts you off from the world.
I have no philosophical objection to vibe-coding apps for yourself, but personally, I wouldn’t be 1/10th of the engineer I am if I wasn’t constantly exposed to the work of others.
For some, this trend worries software engineers — who needs software if they can vibe code it themselves? — but I am much more optimistic. I think people will start valuing good software a lot more. Claude code can deliver the first 90%, but we all know it is the last 90% that differentiates.
Not everything has to be a SaaS, but I don't think all SaaS apps can be vibe-coded to a weekend project.
If it is solving my issues and problems, why do preaching about the merits of a proper product or paying. I'll pay for what I see value in, and vibe-code where I don't see the benefit of paying.
Maybe I miserably fail and get back to paying to product. It's all good, I take that responsibility while I start my vibe-coding session.
Once you identify something like Handy, instruct Claude to study how that OSS project actually builds the feature and adapt the logic to your stack. AI is really good at finding the "seams" (those connection points where a feature ties into the tech stack) and understanding the full implementation.
The trick is knowing precisely where the feature lives in the code (files, functions, modules), because AIs often miss scattered pieces and don't capture everything otherwise. That's what I'm working on at opensource.builders[1]: turning OSS repos into a modular cookbook of features you can remix across stacks, with structured "skills" that point to the exact details so the porting works reliably.
kylecazar•3d ago
It used to be that you offer subscriptions only if there are ongoing costs, and a one-time payment if not (utilities, local, etc). SaaS kinda ruined that.
I'd welcome a boom in DIY vibe-coded utilities for personal use.
mr_mitm•46m ago
theshrike79•8m ago
But I'm not going to start adding features to my bespoke utility to fix someone else's problem.