Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Your app subscription is now my weekend project (rselbach.com)
393 points by robteix 20 hours ago | hide | past | favorite | 285 comments




First of all, I’m skeptical about these being free. Time isn’t free, and the tokens to make these projects certainly weren’t free.

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.


How are you completely disregarding the data integrity and privacy aspects of rolling your own tools?

I vibecode an app that only I use and store data locally. That means my data never leaves my device, I never have to share my email with anyone, never have to enter my credit card info anywhere

You buy SaaS and you have to then login, share credit card info, and have your data stored in the cloud somewhere with godknows what security practices

That’s worth more than the cost of any tokens


> You buy SaaS and you have to then login, share credit card info, and have your data stored in the cloud somewhere with godknows what security practices

I'm speaking more about fake SaaS "we have an app and we charge monthly for it and license it." Obviously, a tool with cloud-based storage and sharing will be a different beast.

But do you trust a vibe coded app to do cloud-based storage and sharing better than a company or an indie developer? If you need these functions (like sharing a todo list between two users), you have a lot more concerns than "does it boot".


If I vibe coded it? Absolutely. I can definitively answer what S3 buckets are in use, and that public access is disabled! Like, that parts really really not that hard, and people keep fucking it up. Plus the threat model for the Todo so that my small friends/family group uses is totally different from the problems google keep faces.

But that's cheating because I do this stuff professionally. Would I trust a vibe coded Todo app my uncle's son Jimmy who smoke a lot of pot uses? I'm not saving my bank account number to it, but I'd have no problem using it for reminders that my aunt's birthday is coming up so I need to buy a gift. If it gets popular within in the family unit, uncle will have me talk to his son and take a deep look at it anyway, try and encourage Jimmy to go back to school and look for a job and all that stuff too.

Plus, theres nothing stopping the company and indie developer from vibecoding as well.


Another way to look at this is that you're giving away all of your source code as context, and probably a lot of things you don't necessarily want to share, if you aren't using self-hosted models.

Especially with agents that slurp up files, have access to databases, etc. You're literally giving access to your computer, your network and your data to third parties and letting them run code.


During development you don't use prod data, though. So I don't see much problem here, even if I'm developing something where I would store sensitive data later.

(If there is a bug though which I would want to debug and if I were not a developer, then your concerns are more valid)


> During development you don't use prod data, though.

I’ve seen projects where testing is done in prod and also projects where API keys for some external services (e.g. Mapbox) are shared across prod and dev. Or cases where credentials end up in GitHub repos due to ease of use and how inadequate secret management solutions can be.

Luckily that’s not the majority of projects, but I bet it happens a lot more elsewhere. Definitely a bunch for your average outsourced/freelance/scrappy/non-funded project.

Whether anyone will actually use your secrets or even code that’s sent to these large AI shops, though, that’s another question. You might as well question using GitHub cause it’s owned by M$.


honey pot that shit. attackers, security companies, GitHub themselves, are all crawling GitHub for leaked credentials and will tell you that they've been leaked. GitHub very much knows what a GitHub API key looks like. So you stick a GitHub API key with the least useful permission you can think of into your secrets file. If that file ever gets uploaded to GitHub, they'll cancel the key and email you about it, so then you know the rest of the keys in that file have been leaked as well.

Data privacy is a real concern, but any SaaS provider worth their salt is using Stripe or similar for payments, not rolling their own. That's not as good as not providing the info in the first place but that makes it much less likely that your CC info is going to turn up in an S3 bucket with bad permissions or something.

Yes, but at this point I'd almost rather have my CC info exposed than my personal info. There is law and consequence for fraudulent charges that protects me from loss (if not inconvenience) but there is basically no protection for playing fast and loose with my PII--in fact, it's the opposite! They sell it!

I haven’t thought about it this way but yeah I totally agree. Most of the major consequences from my CC info getting leaked can be dealt with without major long term impact to my life. The same cannot be said about PII currently

privacy.com let's you generate per-merchant credit card numbers and put limits on them, limiting the damage a leaked CC number can do.

To my mind, this is the huge bit that should not be overlooked.

So much infrastructure is there to support doing "it" in the Cloud, for all definitions of "it." If we can vibe-code bespoke one-offs to solve our problems, a lot of that Cloud interaction goes away... And that stuff is expensive and complicated.

Hypothetically, open source app stores (I'm counting apt here) address this, but then it's someone else's solution to my problem, which doesn't quite fit my problem perfectly.

This approach to software engineering could be what 3D printing is to tangible artifacts (and I mean that including the limits of 3D printing regarding tangible artifacts, but even still.)


> That means my data never leaves my device

I mean, if you vibecoded it you don't actually know that, do you?


Until vibecoding agents somehow develop the capability to sign up for a cloud storage API and pay for it on their own, you can probably be pretty sure about that.

An exfiltrator would have a blind upload box sitting somewhere the poisoned prompt knows about

vibe code manifest.xml to disallow network access. If you're really paranoid, you can use Google search to look up the permissions names instead of relying on an LLM to do it.

Most apps rationale for subscriptions is "Ongoing development" without an option like jetbrains etc. to fall back to a perpetual license. In practice, regardless of whether an app needs ongoing development or not, this is the best way to try to guarantee continuous income and make a living off of a project I guess.

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.


One-time purchase software would become dramatically more sustainable if platform churn could be ground to a halt. Most types of software achieved peak usability and functionality somewhere between 5 and 25 years ago and there wouldn't be much reason for anybody to upgrade if their one-time purchases continued to work in perpetuity. A substantial number even prefer e.g. Word 2000 or Photoshop CS1 over their modern incarnations but can't use those for either technical or legal reasons.

Instead, the reverse has happened and platform churn has risen to new highs, necessitating subscriptions.


Maybe we should just freeze development in lots of designated areas and declare victory (I know this isn't a practical suggestion, but still...).

Eg in desktop OS's. Apple for example makes everyone miserable by re-breaking macOS every year. To what point?


nvi hasn't meaningfully changed in almost 20 years. It's OK for software to be finished.

Apple certainly churns APIs quite often. And now my Tahoe install has broken window management, one of the most core features of a modern OS

Yesterday's submission explained the choice of subscription precisely due to the need if ongoing development: https://news.ycombinator.com/context?id=46716385

Part will be for new features, but no doubt that another big part will be for platform support over time. There's just too little backwards compatibility guarantees nowadays from the big players. We need more Microsofts in that sense!


> Instead, the reverse has happened and platform churn has risen to new highs, necessitating subscriptions.

... Even for desktop Linux users? I can't say I've felt it. I switched almost 4 years ago and it just keeps feeling better and better (in a "Luigi wins by doing nothing" kind of way).


Linux desktops (not the kernel) are actually among the worst when it comes to platform churn. It's one of the reasons why Flatpak, AppImage, Snap, etc require relatively complex machinery and runtimes and whatnot to function. The churn is just masked by package managers.

It's come across to me so far that this just results from application developers targeting a specific DE and not really thinking about compatibility, or even really whether they need specific functionality provided a specific way.

Would be nice to see the XDG stuff like portals etc. better respected, though, yeah.


> It's come across to me so far that this just results from application developers targeting a specific DE and not really thinking about compatibility, or even really whether they need specific functionality provided a specific way.

They are, but it's not their fault - Wayland removes so much functionality that X had, and delegates that to the WM/DE.

I tried to do a small personal app last year for myself that intercepted and injected events for keyboard and mouse. Not possible in Wayland (so I switched to X instead) - that is delegated to the WM/DE.

There's hundreds of these tiny little cuts that cause friction for app devs.


DE stuff is part of the picture, but there’s churn outside of those too. glibc, which is used in practically everything, is the classic example but across the whole of the Linux desktop sphere, it’s unusual for libraries to maintain compatibility.

The only reason why Linux desktops work at all is thanks to package managers and their maintainers doing the heavy lifting of keeping applications and the libraries they use in lockstep. If it weren’t for that random programs would be breaking every other update.


if snaps were masked by apt, there wouldn't be such an objection to them.

It is not irrational on the part of the developer -- I've definitely felt this too. The problem comes from the fact that practically everyone has subscription fatigue these days, and each of us probably has only a few pieces of software we truly care about enough to want to support them out of the goodness of our hearts.

But everyone wants us to pay $10/mo. It just isn't sustainable from a consumer perspective.


> 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 so few actually deliver $10/mo worth of value. If 1password and Fastmail

Funny you mention Fastmail. I was happy most of the past decade until this week. I just had my email blown up by their new Paddle billing system with a ton of billing invoices since they decided it was no longer ok that I pay them a lump sump every 2 years, and that I must go onto monthly now. Initially I thought they were hacked but nope, just terrible communication.

I emailed them a few days ago and they only confirmed that Paddle is their merchant of record and they have been migrating accounts over slowly.

Tonight the CEO sent out a blast saying resellers need to be on monthly billing with their new system at new pricing.

Sorry Fastmail, I paid for 2 years back in October (I think this is my 3rd cycle with them). If you want me on monthly billing then you will wait until October 2027. That is a ‘you’ problem not a ‘me’ problem if you undersold the subscription this cycle.


All bootstrapping founders should read the above post to understand why you should never build B2C.

> that's the standard of value other SaaS companies have to beat and very few do.

Of course it isn't. Just because some products or services are great value, doesn't make other products bad value. They can be anything from good value, to average value to low value.

And products / services are of course not comparable just because they are subscription based, or used on a digital device.

Gas has a fantastic value, one liter can transport me and my things a long way in short time. So does that mean that I can never buy a bottle of wine or some coffee outside of my home? They are after all liquids, and neither coffee nor wine can compare with the great value of gas.


> Just because some products or services are great value, doesn't make other products bad value.

Sorry, but no. If they're worse value than my email and password providers which my digital life revolves around and who only charge me $5/mo each, then yes those products are a bad value.

I pay $3,000/yr for Altium, $200/mo for Claude Max, $60+/mo for ad-free streaming, and begrudgingly $50/mo for Adobe so I'm not against paying thousands a year in nice fat profit margins if they provide actual value, like a shit ton of GPU compute time or a well made piece of professional software. "Value" here is obviously subjective relative to the beholder, but IMO the vast majority of SaaS I look at are hardly worth two bucks a month, let alone tens.


> "Value" here is obviously subjective relative to the beholder

Agreed, but the confusing part is that you don't seem to be saying "to me, those services only provide X amount of value, and I'd rather have $Y than that" -- you seem to be saying that if 1password and Fastmail were more expensive, you might be willing to pay the asking price for some of those services you currently consider bad value.


You’re absolutely right! If Fastmail or 1password charged more for their services, the bar for what I consider good value would be different. Those two services are _absolutely_ worth more to me than they currently charge and I’d be happy to pay.

But they don’t, which is why I use them as my baseline. If my email provider and password manager - two services with damn near infinite vendor lockin - can do it, no one has any excuse.


Which is your choice, obviously, but you can see why people would find it strange -- it seems like you're potentially just leaving value on the table for an arbitrary reason. The price of Fastmail doesn't affect the value you would get from some unrelated product, so surely that other product is either worth the asking price or not worth it regardless of how much Fastmail is charging.

> If they're worse value than my... password providers... who only charge me $5/mo

In that case, people who run Bitwarden for free are screwed. In fact, looking at how much I use the web browser Chrome, and how much I get out of that, and the fact that I pay $0 to Google to use it (inb4 I'm the product because I'm not paying for it), paying money for anything digital is terrible value!

What you've discovered is that prices are all made up. If we think about how to price a product, say a chair, from first principles, you'd take the cost of the raw materials, the time it takes you to turn those raw materials into the finished product, add a %age profit on top, and call it a day. In the real world though, that's not how pricing things works. You have a product, which costs $X in raw materials, and then you just... make up a number, $Y. Hopefully, $Y is much greater than $X, and you're able to make a great living off selling your chairs. Maybe you're called Eames and people will pay you $5,500 for your chair/lounger, maybe you're Office Depot and sell them for $129. Maybe you're not very good at chairs, so they're not level and then you can't give them away, not even to your friends.

Life is not an optimization problem. You can optimize for value, but then you'll find yourself in Walmart at 1am realizing that the 3-pack is cheaper per-roll than the 30-pack that night for some reason, and getting angry over that.


> What you've discovered is that prices are all made up. If we think about how to price a product, say a chair, from first principles, you'd take the cost of the raw materials, the time it takes you to turn those raw materials into the finished product, add a %age profit on top, and call it a day. In the real world though, that's not how pricing things works. You have a product, which costs $X in raw materials, and then you just... make up a number, $Y. Hopefully, $Y is much greater than $X, and you're able to make a great living off selling your chairs. Maybe you're called Eames and people will pay you $5,500 for your chair/lounger, maybe you're Office Depot and sell them for $129. Maybe you're not very good at chairs, so they're not level and then you can't give them away, not even to your friends.

It's just common-sense though - if the market is willing to pay me $100/widget, why would I sell it for `($10 cost to manufacture + 35% markup)`?

The new lower bound for simple side-hustle apps now is virtually zero. All you need is a computer, electricity, internet and (optionally) $20.


> What you've discovered is that prices are all made up. If we think about how to price a product, say a chair, from first principles, you'd take the cost of the raw materials, the time it takes you to turn those raw materials into the finished product, add a %age profit on top, and call it a day. In the real world though, that's not how pricing things works. You have a product, which costs $X in raw materials, and then you just... make up a number, $Y. Hopefully, $Y is much greater than $X, and you're able to make a great living off selling your chairs. Maybe you're called Eames and people will pay you $5,500 for your chair/lounger, maybe you're Office Depot and sell them for $129. Maybe you're not very good at chairs, so they're not level and then you can't give them away, not even to your friends.

That's not at all how I think products are priced. That sound's like something you'd tell a kindergartner to shut them up.

> You can optimize for value, but then you'll find yourself in Walmart at 1am realizing that the 3-pack is cheaper per-roll than the 30-pack that night for some reason, and getting angry over that.

I have never found myself in a Walmart at 1am* nor have I ever gotten angry at toilet paper (I get the Charmin ultra from Costco like a normal person). You need to re-calibrate because you sound like an Inland Empire methhead. Pro tip: you want to shoplift the detergent. That tends to trade better with the other methheads.

* Not entirely true, but that's just because the Reno Walmart stocks up on Burning Man supplies and Gerlach only sells shitty playa bikes.


I think you need to recalibrate because charmin is fucking lol

Who am I to argue about toilet paper with a user named goopypoop!

I assume you use vintage fire hoses from the Birmingham campaign to clean down there?


well it's hard to find quality chamois these days, but tbf since i joined the human centipede i haven't looked back

Then you cannot ever buy a cup of coffee, because it's also very bad value compared to Fastmail. Or a beer.

> The vast majority of SaaS I look at are hardly worth two bucks a month, let alone tens.

Then why are you looking at them,


Availability is a big thing.

I don't order a coffee to my house because I can make coffee at home.

But if I'm at another city, then paying for a coffee beats not having it.


I don’t buy cups of coffee unless it’s on vacation, brewed by a great barista with years of experience. Instead I have a $600 roaster, a $100 burr grinder, and a $10 Turkish coffee pot that have produced many thousands of good cups of coffee over more than a decade. Including the cost of bulk beans, I probably spend about as much on my caffeine addiction as 1password and Fastmail combined. Seems like a decent value to me?

I think your value system is completely broken if you think I can’t have a beer just because they cost more than fastmail. Some beers are better value than others but I enjoy having a beer. I don’t enjoy logging into some overpriced SaaS to do something that Claude can do for me now instead.

> Then why are you looking at them,

How can I evaluate their value if I don’t even look at them?


It certainly was when the options were pirate or buy, and the prices per year were much higher than $10/mo gets you.

The BIG difference is that we didn't felt entitled to use everything that is fashionable or switch apps every couple of months.

We would do a research across several magazines, local computer clubs, and the few lucky ones that had online access, some BBS or Usenet groups, then buy that one package and live with it for a couple of years, regardless of their limitations.


And so the solution is… paying Anthropic $200/mo…

All of the projects OP mentioned could be vibe coded for <$10 worth of GLM-4.7

The inference is cheap, but the context window costs for iteratively debugging architecture issues add up fast. Things like state management or migrations usually require feeding the whole stack back in multiple times, which blows past that budget pretty quickly in my experience.

"Man, it kind of sucks that LLM only does one thing and that my compiled applications stop working after I turn off my LLM service"

37Signals tried that with once.com . Given they're now giving those away for free and haven't said a thing about it suggests it was an abject failure. What you're paying for with SaaS is outsourcing - deployment, maintenance, security, reliability etc are someone else's problem.

The code is the easy part but there's ongoing humans needed to make it work. If Agents get to the point they can genuinely autonomously SRE & patch a service everything changes but that still seems a long way off.


Or drop the price to $20 a year instead of $20 a month and and focus on small software updated infrequently. Software as a service has a dirty secret that it was more service than software. The companies became larded with payroll and most never had great gross margins.

Pretty much. A lot of software is just good enough already, just keep security updates going and fix occasional bug people complain for too long.

But that might require just firing some people because that amount of man-hours is not needed any more or moving them to make something new and no investor likes it


regardless of whether an app _does_ ongoing development. there's plenty of examples - especially mobile - of apps switching to subscriptions and simultaneously slowing down development, which is maddening

I think that's where technical issues come in. For a web based SaaS app it's not worth the devs time to make multiple versions available. Even for local apps, I would say most of them have some functionality tied to an API and now you're back to running multiple versions of that server.

I just don't understand this naive argument against subscription. If I have to pay same amount of money, I will pay in subscription than paying one time. So let's say average subscription time is 2 years, they can make $400 onetime or $20/month to get the same revenue. As a consumer I will prefer the second option.

For $40 product, I will rather pay $1/month than $40 once. It keeps the incentive aligned. I think most people just assume that if the devs move away from subscription they would be fine with lower revenue and would charge less.


Even getting an app on the Apple App Store requires a $100/year payment. You either grow users continuously or you ask for a subscription.

> I can’t reimplement it in $30 of tokens or $30 of my time.

Probably not.

I also paid for FreeFileSync (the donation version) instead of rolling my own local backups (across drives), as well as MobaXTerm because I really like their UI/UX and so on. Software that others have developed and supported for multiple years, which has been already tested by a lot of folks thoroughly across their usecases is probably a good bet, doubly so if you can buy it (or I guess choose to support the devs) instead of renting it, the difference being that in the latter case you're not in control.

At the same time, 30 USD gets you about (assuming 85 input and 15 output split, which approximately matches my stats across months):

  * Gemini 3 Pro:  8.57M tokens (7.29M input, 1.29M output)
  * GPT 5.2:       8.36M tokens (7.11M input, 1.25M output)
  * Sonnet 4.5:    6.25M tokens (5.31M input, 0.94M output)
From: https://pricepertoken.com/

(actual figures would change with the input/output proportion, it matters a lot, and also any caching)

Not really enough to build serious software, but definitely quite the bit of help along the way!

Or if you go with subscriptions, it can vary even more, even if will cap how much you can do per day.

For example, if you pay 50 USD for Cerebras Code, you get 24M tokens per day, so that'd be close to 730M tokens per month. They're running GLM 4.7 which isn't SOTA in my experience, but is somewhere around Sonnet 4 and therefore actually quite capable: https://z.ai/blog/glm-4.7 (my experience might not match the benchmarks, but either way it can be good enough for most stuff out there)

For a decent percentage of software development, maybe where you want a feature nobody else out there has, AI can help you get rid of enough friction and lend enough help along the way, to maybe make it worthwhile. The caveat there might be that you have to treat the expense of your own time as something you do for the enjoyment of it (building something, or the delayed gratification of benefitting from using the software).


Biggest problem for SaaS is that people don't have enough time to be informed buyers. Like in theory you should be able to make a $0.99 annual SaaS app that provides some small service really well and sell it to a million people who need it, but that kind of sale is almost impossible. Most people are either missing out on great software they should be buying, or paying for software they don't need.

> the value for “SaaS apps” without clear monthly costs should have always been under scrutiny.

It should have been, but the number of people qualified to offer proper scrutiny has been low, and those people have largely been occupied with bigger things. Or they were making those apps and had a conflict of interest.

The point is that now that vibe coding is at a level where it can identify and put together off-the-shelf components, and there are all these end users that don't really care about standardization (it's not like their SaaS products used open, interoperable standards in the first place), the ability to compete with those offerings has exploded.


I probably didn't market it enough but I specifically made an iOS game last year to be premium, $2.99, as a one time purchase to try and get around the obsession with subscription and freemium/ad-supported models but pretty much didn't get any more than a handful of sales.

At least for games I think it's much too late for the one time purchase model unless you're part of a pro studio making relatively big games.


> First of all, I’m skeptical about these being free. Time isn’t free, and the tokens to make these projects certainly weren’t free.

Yes, but it's almost one time payment. Your own personal use case is usually narrow enough, and you don't need to support different OS/browsers. You can vibe code it and just forget the fact it's coded.

Actually it's the best use case for vibe coding (the strict meaning of this word) - when you don't plan to maintain the codebase anyway.


The time argument is countered in roughly the same manner as when you do home improvement.

Yiu don't pay taxes on the time spent on your own projects.

There is no alternate I've cost, as the time would usually have been spent watching television if not doing these projects.


This argument is brought up a lot against using opportunity cost for private projects, but I don't buy it

If you are dedicating a considerable amount of time on a project, there is of cause opportunity cost, since that's time

- not spend on improving health - not spend on improving skills - not spend on improving other projects

Seldom one decides between a side project and starring into the void


It's the app "stores" that encourage and push for that.

You pay less tax to them when you do subscriptions rather than one time payments, if I recall especially with Apple Store (something like 30% first year, 15% the second year of subscription).

This is why 120$ over 10 years (1$/month) is more profitable to companies than 120$ in a shot.


The problem with one time purchases is that they don’t allow for rent seeking behavior - the cornerstone of any sufficiently sustainable greed model

Well, for non-standalone apps you also need some degree of ongoing support, at the very least to patch the security bug in your app or update libraries that have those.

and when whatever framework or big lib you use decide "well we're making new version, everything you made will break, have fun", that needs engineering too.

Buy once model is pretty much only for standalone, offline apps. Anything online and you have to start to worry about supporting new TLS versions or having to update certificate store (if app for some bizzare reason ignores system one)


how do you feel about licensing where you pay once, get the software, and have access to updates for one year?

if you want future updates, you pay for another year of updates (discounted, of course, for loyalty).

or is it more compelling to just have one clean, flat, lifetime rate?


Why would it only be a year of updates? Just go back to how it was 10 years ago when most software was a 1 time purchase and you got updates until the next major version, then maybe you'd only get bug fixes and security updates until your OS deprecated some API the app depended on.

The industry had arguably more innovative products than exist today and that business model worked totally fine until the platform gatekeepers and VCs invented SaaS because they decided they weren't making enough money and needed to do some rent seeking.


JerBrains does something similar (after paying for a year I get perpetual license for the version released that year). I’m pretty happy and feel under control. I have been paying them for years now and in case they screw up I will stop my subscription and still can download and use old version. Sure I will be missing on some bug fixes but I have used the software for a year already, I can live with those annoyances. It’s not like the new version will be all bug free either.

I think the best way is you buy a software, and that version is supported "forever".

The developer then creates version n+1. The old version is kept supported, but new features go only into the new version, which you can optionally buy again.


Time/energy wise, even with agentic coding, that's probably not the most fun value proposition for smaller/solo dev teams. I now have to maintain a mental model of several versions of my software, track features, refactors, etc across all the supported versions, and make sure my work doesn't overlap too much lest I cause more bugs while keeping everything stable.

I wouldn't charge customers _less_ for that just because it's now a one-time payment.


Workingcopy app is a better model.

You can pay to unlock advanced features and keep them and any new features added in a year, after that any new features are paywalled for another unlock, and another +12 months, perpetually.


hopefully this at least bring us to pay to own software instead of subscriptions

You too can implement a slither of the features you need right now in an insecure form without hosting, support, maintenance or future development.

This reminds me of the people who think they can build docsend in a weekend. No, you cannot. You can build a wee throwaway app with some of the features of docsend. But that is not equivalent to what people pay docsend for.

Businesses and SaaS aren’t just a bunch of static code. Code is a part of them, but it’s actually a minority of the work and the service. It’s very common to see founders fall out because CTOs believe product and company = tech and CEOs do not.

If you’re a technical founder, learning this lesson will separate you from the pack.


There is probably a huge chunk of people who only need a slither of the features of a SaaS but are paying for everything they don't need.

If your particular use of a SaaS is not susceptible to security issues (for example you can use it on your local laptop) then a slither of features that are insecure is exactly the thing for you.

Not everyone is going to replace SaaS with half-baked personal implementations, especially the big companies that most SaaS are aimed at, but it will gnaw out some of the long tail of SaaS subscription revenue for sure.


> This reminds me of the people who think they can build [some commercial app] in a weekend. No, you cannot.

If the article was claiming that you could, you might have a point.

> You can build a wee throwaway app with some of the features of [some commercial app].

Which is precisely and explicitly what the author has done.


“You too can implement a slither of the features you need right now in an insecure form without hosting, support, maintenance or future development.”

Intuit does just that and charges north of $100 per month.


Insecure? What do you think is more secure, trusting a third-party SaaS with your data or processing it on your own server?

This seems like an incredibly defensive take for vibe coding personal apps.

Replacing some subscription app like Any.do, Google Calendar, fitness/diet tracking or basically any other CRUD-centric app, needn't be insecure, and a semi-competent developer can easily host it, continue further development (with or without vibe coding) and secure it. There's huge benefit for software developers that do find themselves using many of these apps with active subscriptions to make their own, tailored for themselves, and cut down their spending.

Yes, when it comes to commercialising such software, more work needs to be done (mostly in support and marketing), but for personal use it's fine. The author explicitly states they don't trust vibe coding enough to turn these into products.

The writing is hardly on the wall for all these companies which make little todo list apps and calendars. The vast majority of people could get a LLM to produce an alternative but the lacking they have in basic software engineering would eventually be a hurdle to further development. Most people will continue spending $1.00/month here, and $2.99/month there. There's no reason why software engineers need to do that anymore, unless paying this gives them access to some sort of content repository (music, books) or actual advanced software.


>There's huge benefit for software developers that do find themselves using many of these apps with active subscriptions to make their own, tailored for themselves, and cut down their spending.

I guess if you're unemployed or in an area with spectacularly low wages, and don't have any ideas of your own that seem monetizable.

>Most people will continue spending $1.00/month here, and $2.99/month there.

If I make 100 dollars an hour as a consultant, and I spend 1 hour to make a local version that never needs any updating on my part to replicate a portion of that functionality I get for $1.00/month, it will take me 101 months to see any profit on my investment of time.

Cut my pay in half and I still need 51 months to see any profit. It would be idiotic for me to waste 1 hour on that.

And let's face it, code when made is a cost center, you will have to keep it up to date (so as to not introduce security hazards etc.) you will never break even much less earn anything for your time.


By that logic, how much did it cost you to write this comment?

And if they simply want something tailored for themselves?

Something designed without content suggestions, ads, influence and constant un-necessary redesigns, for privacy and to retain their own data.

Good for you economically. Some people are unemployed and underpaid. In fact, most are. Half of your post just came across as you broadcasting your economic success.


Now be the teenager with no college degree that you were before you ever made $100/hr. Most of your options then paid < $10/hr, if that. The calculus looks a lot different then.

The vibecoded threat isn't from Devin, the threat is from 15 year old nerds who no mortgage, partner, or responsibilities. Powered by insecurity, pride, and spite, plus a generous amount of teenage hormones. I would love to see What I could have built if I had Claude back when my reflexes were still powered by youth.

Plus, if you made an app that other people were paying $1/month for. Sell yours to people for $2/month (or $0.50/month, you decide!) and you'd recoup your money much faster than 51 months.


> This reminds me of the people who think they can build docsend in a weekend.

The author is very clear that that's not what they are trying to achieve:

"Now, don’t get me wrong, Jabber is not “production quality.” I would never sell it as a product or even recommend it to other people, but it does what I needed from Wispr Flow, and it does exactly the way I want it to."


Reminds me of a guy I know who wants to vibe code all his company tools, his latest target was Ashby

What you say isn't different from what the blog post says: he makes it clear that he wouldn't trust the results to be production-ready and he wouldn't sell nor recommend his vibecoded stuff to others. The only claim is that those are good enough to cover his specific use case, no more and no less.

You over-estimate quality of most SaaS products

Software is a manifestation of someone’s knowledge of and experience in and ideas about how a thing should work. We learn from the software we use, we benefit from everyone else’s ideas, we benefit from the hundreds and thousands of hours other people put into understanding a problem to design a solution. My workflow is better because of the incremental improvements made by developer after developer year after year. Would we have Claude Code if our foredevelopers hadn’t spent thousands of hours deep in thought, obsessing over every last detail?

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.


I like to say "my code is 200% vibe-coded; the tricky bit is figuring out which 100% to keep".

Decisions matter, both technical and product ones. LLMs don't make as good technical or product decisions as I would, and the way I work with them tries to maximize my strengths and the LLM's strengths. I don't know if I succeed, but it's better than "make me an app like X" as a prompt.


Your quote caused me to consider vibecoding through the analogy of an LLM-human system as a subtractive synthesizer: the LLM is the oscillator, and the human is the filter.

> I think people will start valuing good software a lot more.

How will people determine what is good software and what is not? Even experienced engineers can't tell just by looking at the final product.

Some of the most solid rock-solid applications I see were built years ago and still look primitive (native Windows 7 controls, etc). Many of the worst, bug-infested anti-user software looks slick and modern.

> Claude code can deliver the first 90%, but we all know it is the last 90% that differentiates.

My experience with trying to complete that last 10% of a CC generated project is that it's all very alien looking; very uncanny-valley vibes, and I have serious velocity issues because of the lack of coherence.


> Building all the software you use yourself, whether by hand or by vibe coding, cuts you off from the world.

No one is doing that. In foreseeable future I don't see people making their own OSs, browsers and drivers. Workplaces never ditched Offices and Windows for the open source counterparts and they are certainly not going to do that for vibe coded solutions.

You can rest assured.


Making your own software is a good way to escape enshittification and influence.

I switched from Spotify to buying MP3s and using my own audio client, because I'm fed up of a company telling me which music I should listen to every single time I open the app. It costs more, but I own the music and I escape the constant redesigns, price increases and influential behaviour.

Most apps are very simple and there isn't too much to learn, especially if you're building it to scale to a userbase of yourself. I can't see the need for a ton of CRUD apps which demand subscription fees personally. If you build them yourself, you get to keep your own data, build it out the way you want it, keep it that way, and use computers as a person using a tool as opposed to a customer buying a product.


I did MP3s on my plex server for a while but with endless new music added to my playlists it became a hassle and Apple Music was just convenient and Shazam adding any song I hear and like is just too easy...it also plays perfectly on my Apple Watch over cellular when I go for a run, but everyone has their own use case and where they want to spend their time...

That's understandable. I have quite minimal music taste so my setup worked for me. I only listen to music at home when I'm not doing anything else and it's mostly classical so there doesn't tend to be too much to add at any given time.

A minimal web client audio player with some basic database tables in the back for organising and searching does me fine.


Opensource has been available since before the internet. What is `git clone ... make install` if not "vibe coding"

Your entire post is self selection bias and survivorship bias.

SWE field is one of the most cognitive dissonant social groups; cries foul at the slightest whiff their free speech and agency is being put upon; seeks to reduce blockers to their productivity, fewer PMs! Less management!

Now complains about users using their machines without having to block on an SWE.

Insert that quote about how someone will not see the obvious if their paycheck relies on them ignoring the obvious.

Here come LLMs and all they can accomplish with a few arithmetical rules instead of the arbitrary semantics of an SWE; watch as SWEs block social evolution away from disrupting software engineers.

As an example; "protected memory", among many other individual software problems, is an access control problem mired in old semantics relative to OS monoliths.

Didn’t see you all halting as you decimated travel agent jobs, retail jobs, etc etc. Technology advancement must now stand still after centuries of evolution? The self selection bias is as obvious as Trump's.


dimator captured the point I was hoping to make, more eloquently than I could hope to. I defer to their comment: https://news.ycombinator.com/item?id=46725512

That said, to address your broader point: me, personally, I am thrilled that the barrier to entry for building software has been all but eliminated. The joy of creation belongs to us all.


you couldn't have missed GP's point any more if you tried. ignoring the ad-hominems about SWE greed:

these tools have been trained on decades of people "obsessing over every last detail". what GP is arguing is that we're detaching from that: you prompt, you get something that works, it doesn't matter how it got there. we're now entering the world where the majority of code will be vibed. So whatever our foredevelopers came up with, that will be the the final chapter of craftsman-produced, understood, code. whatever the previous generation actually learned about software engineering, that's at an end too, because why bother learning when i can prompt.

there's no stopping this transition, obviously. the next generation of tools will be trained on the current generation of tools' generated code. we're passed the "termination shock" of sofwtare understanding.


Oh I got it just fine. I was knocking their point artisanal software will make a comeback.

Am an EE and have argued against all the developer gibberish and self aggrandizement for years. It's just electromagnetic geometry of the machine to me.

Most software out there is all the gibberish devs need to do their job. Burns a lot of resources clinging to it. Completely useless to using a computer how most users will.

Vectors as a uniform layer of abstraction, rather than arbitrary namespaces a programmer finds cheeky, will obsolete a bunch of gibberish.


It’s all fun and games until it happens to you…

>Didn’t see you all halting as you decimated travel agent jobs, retail jobs, etc etc.

You have to remember that SWE's are the same group that screams "communism" the first moment you mention the word union and they should have the right to make as much money as possible with no restrictions.

This of course leads to the obvious lack of self reflection in their responses when something threatens their future income.


Labor unions align themselves well with Marxist thought and both are pretty based.

I'm not a SWE because I like money. I'm an SWE because I love programming.


"Transportation, like software, is accumulated knowledge. The horse embodied centuries of breeding, training, and hard-won understanding about terrain, endurance, and failure. People learned from the horses they rode. Travel improved through incremental refinement, generation after generation. The automobile didn’t appear in a vacuum.

Building all your transportation yourself—whether by breeding horses or assembling a Model T—cuts you off from that accumulated experience. You lose the benefits of thousands of hours spent by others thinking carefully about the same problems.

I have no objection to Model Ts for personal use, but I wouldn’t be one-tenth the traveler I am without constant exposure to well-bred horses.

Some worry cars make horses obsolete—who needs breeders if anyone can buy an engine? I’m more optimistic. As cars proliferate, people will value good horses more. A Model T gets you the first 90%; it’s the last 90%—judgment, robustness, and adaptability—that differentiates."


Building (or vibecoding) a markdown editor for a single user and their specific use case, for a 100 users, and for 10,000 users takes different amount of time and effort. In the pre-LLM days people with resolve to make 1-user version were likely to polish it for 100-users and somewhat likely to get it to a stable place when it can satisfy thousands of users.

Today on /r/macapps/ there’s a wave of apps that look good at the first glance but get abandoned before they achieve even a 100-users maturity level.


> In the pre-LLM days people with resolve to make 1-user version were likely to polish it for 100-users and somewhat likely to get it to a stable place when it can satisfy thousands of user

And then put it on an app store and put all the vital features behind $15/mo subscription.

Which is totally justified! I understand the time and energy needed to get a product polished for 10,000 users. But thanks, I will take my vibe coded one.


Contrastingly, Minimal (minimal.app) is a markdown notes app made by me for me (for one person!) improved to support 100 thoughtful writers, improved again to support thousands, then tens of thousands… now 6 years later I continue to ship meaningful updates (OS parity, new features, better designs for existing features, greater stability and performance, and occasionally entirely new patterns).

What made the difference? For one thing, I know better than to ignore the future. A small success in 2020 was like a seed planted amidst an infinite future, and I knew to water the seed. Secondly, I continue prioritize this fulcrum between complexity and utility, where the app gets better by getting simpler wherever possible (most people neglect this fulcrum as not offering much “business opportunity,” failing to realize it is the foundation of all business opportunities). Finally, I just love it, and appreciate that others love it too.

(For those interested, you’re welcome to join the beta at minimal.app/#beta on Apple devices and contribute to the roadmap.)


Lots of people threw small apps on their Github accounts for their own convenience in having a backup, and in case other people might be interested, but realistically never expected to get one more user. I have several scripts, Chrome extensions, and the like in my Github that fit that description. The difference is that coding agents let you write a one-user app at a much larger scale than before.

Unless your name is “Legion”, you’re a single user, not a 10-thousand.

i mean, sure. but the point is, you yourself are often a solo user of these little productivity apps. if you're not using team-based features then a lot of these things aren't worth paying for.

I didn’t mean collaboration features. I clumsily used 10,000-users as a measure of the app completeness.

"10k user completeness" might be full of "features" you don't want that clutter the ui and add entropy.

You know how you think and know your goals so a customized, focused solution would be better than something for the general masses.


I read the same tired opposing arguments all the time; I thought of it the moment I read the title. "My time isn't free, so I'll pay the tax" is true, however most of these individuals spend hours a day watching the news or doing anything else but being productive or spending time with family/friends.

If you aren't working 24/7 while handling a family and telling yourself your time is worth more than a small fee, you are just being lazy. I'm the same way, I am incredibly lazy and will constantly tell myself that my time is worth more. This is usually until I realize I'm spending way to much of my "money" to "save time". HourlyWage(time) = money, if I'm saving time by spending money I'm losing time. This is a basic concept and I defy anyone to show me otherwise.

We live in a time where instant gratification is the main driver behind most decisions, devaluing our currency each and every fee we succumb to... as money is time, and if time is being "saved" by spending time (in the form of money) we are now applying a future debt to the work we are doing today. You might work 40 hours one week, where at least 4 hours of that week goes to paying your streaming bill, another 8 for Internet and Phone, as well as another 2 for the coffee you didn't make that week, another hour for your notetaking app on your phone, 30 minutes for your subscription to watch funny youtuber release content early, another 2 hours for you glut of productivity apps, etc. These things all work to keep you a wage-slave till the day you eventually croak with a menial 401k.

It's embarrassing we reduce ourselves to this.


Get a better hourly wage. About an hour of my month pays for all of my entertainment and software subscriptions. Another couple of hours pay for a year of iPhone. Coffee? Another hour per month maybe? We are worlds apart in our arithmetic and I don't even earn that much.

If people enjoy spending their unpaid hours building clones of paid software that's fine, but it's fine because they enjoy it. It's not minimally worth it. The time I waste on YouTube and the news etc etc is sorely needed and enjoyed downtime. If someone has enough energy to build instead of vegetating, more power to them. I prefer to save my energy for the stuff I value. (Which is actual work, helping family and games)

EDIT: another thing to consider is that each hour I spend fully pursuing my occupation pays me an hourly wage but also pays me in career growth. This compounds massively over time in higher and higher wages. Building throwaway apps generally does not. Why would I waste energy on work that doesn't compound? I'm all for serendipity but not as a financial argument.


The people who pay for the apps vs people vibecode them are largely a different demographic.

Linux is free, but most people don't mind to pay the Windows / macOS tax.


Exactly! It’s like I saw you selling pre-cut fruit for $7 so I decided to cut my own fruit every week.

I think the difference is I was buying pre-cut fruit for $7 every week so I spent two days and now my fruit magically cuts itself forever.

He turned an ongoing expense into a one time expense. And bonus he likely had fun doing the labor.


It's more like he was renting a knife to cut fruit for some reason and now, and instead of just buying a knife, he built one from scratch.

(1) Let's hope he doesn't cut himself if the knife breaks apart while in use.

(2) Why is it so hard to just buy knives these days? Why does every knife maker suddenly feel entitled to charge rent?

I'm all for DIY instead of hiring others, but the insanity here is the rent vs. buy thing going on in the industry.


In some cases, that’s true, but sometimes you need to update cutting rules because of law changes, or you saw different way of cutting for example. There are cases where this is not one time investment. What I agree with that cutting-it-yourself became significantly cheaper

Not for long. Tools to create tools will get more popular. My 70 year old mother can login to Replit and vibe code anything (and has thankfully stopped asking me to help her). We’re close to something like that for phone apps and then it’s game over for us devs.

Well Replit supports building mobile apps also: https://replit.com/mobile-apps

Game over, devs


Linux is free, but it doesn't come bundled with hardware that might not work with it.

Linux is free, but you pay for it with your time.

And calling Windows and MacOS a tax is a complete misunderstanding of what a tax actually is.


> Linux is free, but you pay for it with your time.

People like to repeat this thought terminating cliché because they think it makes them sound smart and insightful, to doubt that a free thing is really free. But it's an uniquely naive opinion.

On Windows or MacOS, it's more often than not that, when you meet a problem, the only thing you can do is throw your hands into the air, and suffer the problem. This is paying with your time. Every single time you have to sit and wait through a forced update, this is paying with your time, in the realest sense of the word. You give your time for continued use of the product, and nothing else.

What people mean with the idiotic folk-wisdom is that you spend lots of time with the internals of Linux.

That's not true, but let's assume it is. The internals of Linux are likely a thing you'll really want to learn in depth if you're professionally into any computers science related job, because the market has settled on that.

If you're not, it's also something you'll want to learn, because Linux's design makes a single skill you learnt applicable in a lot of different workflows. So stuff you learnt while troubleshooting, you may adapt in other situations.

You don't pay with your time, you invest your time. Like all investments, it has an initial cost and dividends. It's a pretty good investment.


The days of compiling kernel module to have your adsl modem working or copy/pasting modelines in an xfree86config files have been over for well over 15 years anyway.

You don't fiddle more in Linux than you do in MacOs or Windows nowadays and that screen recorder tool he had to spend time vibecoding is embedded in the desktop already, the rest of the apps are 2 clicks away from being installed.


Exactly. But it is hilarious that, in the only OS where investing your time in learning something that will almost always be useful in other ways (as opposed to spending your time submitting to a quagmire of bugs), this is described as a "spending".

I made the same realization two weeks ago. Posted about it here, where I rebuilt bare bones todoist with a habit tracker, goal setting and more within a few vibe coding sessions: https://news.ycombinator.com/item?id=46633092

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).


> 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.

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.


Depends on how you define "production".

People in general would recoil in horror if they knew how many essential operations are backed by a mess of Excel sheets with formulas and VBA nobody understands anymore.

All it needs is the maker mindset of being just lazy enough to be bothered by a repetitive task and the courage (and permission) to use an Agentic LLM to figure out a fix for the issue.


> People in general would recoil in horror if they knew how many essential operations are backed by a mess of Excel sheets with formulas and VBA nobody understands anymore.

Yeah, but that mess is deterministic! With a little bit of rigour, someone with no experience of that specific mess but knowledge of excel from a previous employer will dive in, make a small change, see if the results are messed up, back it out, try again with a different change, and repeat until they get what they want.

Good luck asking an LLM to modify something made by a different LLM 5 years ago.


Deterministic but also very fragile. Excel _still_ doesn't have unit tests or linters.

Someone can accidentally type a static number in place of a formula and it may stick there for years.

Or Excel decides that a name of a gene is a date: https://www.theverge.com/2020/8/6/21355674/human-genes-renam...

Or Excel silently losing important health data: https://www.bbc.com/news/technology-54423988

None of these would've happened with a vibe-coded bespoke tool. A basic elementary level unit test would've caught them instantly.


Eh, that really depends on how well the LLM understands edge cases of the particular need. Quite often these cases are hidden deep in files nobody understands any longer and will never get in a training set.

You end up with a system that works right up to the moment it doesn't and fails spectacularly and expensively.

This is one of those reasons you always hear about sweeping medical/hospital records systems being upgraded going tens or hundreds of millions over budget. The edge cases are demons.


Well of-fucking-course you don't vibe code your salary management system =)

Just normal non-coder jobs have massive amounts of repetitive crap that could easily be automated - and already has been automated with Excel - to a degree.

Now Agentic AI lets them automate the rest - or if they're real smart they use an agentic AI model and create an application to do it that doesn't require a LLM subscription.


someone will cry if you lose money or data.. the rest.. vibe code away!

It will be interesting to see if Apple/Android provide a platform for vibe-apps.

It's somewhat like the Shortcuts system on steroids.


> It will be interesting to see if Apple/Android provide a platform for vibe-apps.

They could have done a low-code/no-code platform ages ago, but they didn't. They don't want their users creating their own apps instead of buying, because that would cannibalise their income from hopeful app devs selling 5 units at a 30% cut.


> It will be interesting to see if Apple/Android provide a platform for vibe-apps.

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.


> And then on the afternoon of New Year’s Day, I vibecoded Jabber.

Might have a bit of difficulty naming it that (https://en.wikipedia.org/wiki/Jabber.org).

Edit: I apparently wasn't at all the first to think of this (https://github.com/rselbach/jabber/issues/5).


My first thought as well, there is (or was) also Cisco Jabber which I wouldn't touch with a ten feet pole. It's generally a good idea to Google the name of the software you're about to publish online at least once.

What this tells me is that these should never have been a subscription.

A trial, and then a $5 or $10 one time purchase. If ever you're missing some feature that gets added in a later version, then maybe a $5 upgrade.

But why would a simple text or video editor need a monthly subscription?


> Then just yesterday, a friend of mine was telling me how he got tired of paying for Typora and decided to vibecode his own Markdown editor

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.


Yeah, I was confused by that as well. Typora is sold as a perpetual license for 3 devices at $15. I don't understand why their friend would be tired of paying for it.

Yeah. Part of why this is possible is simply that there are tons of subscription apps out there that were never really justified in requiring a recurring payment and are actually fairly trivial.

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.


Most users expect everything to be cloud these days. In the cross-stitching community (which is mostly older non-technical folk), the amount of people that get mad every day because the most popular app is local-only, is phenomenal. What do you MEAN they smashed their device, bought a new one, and all their WIP projects aren't there anymore?

The subscription craze is getting worse where often the features I need are locked behind a recurring fee costing hundreds to thousands of dollars over its useful lifetime, or are only available in 'enterprise' versions where the sales people laugh me off for not having $30k to spend and won't even let me trial the software (because inevitably I'll just RE it and make a crack)

The most recent example is I wanted a simple home security system with presence detection and a private control panel, none of the free ones hit my requirements, or require custom hardware, or lock you into a cloud, or assume you can spin-up some containers - or are super enterprise grade stuff.

Within about 2 days I had an android app for my tablet, Google FMDN integration, fingerprinting of my other devices, all controllable via Telegram from any of my phones with alerts that "just work" wherever I am and include an inline gif snapshot.

What I wanted didn't really exist as any individual product, so I absolutely see the appeal of DIY vibe-coded stuff, and a day of the build time was optimizing the OpenGL motion-detection pipeline with shaders & DMA which in itself was good to learn about.


What I fear is a pollution of the open source space with tons of tailored apps that have a lot of overlap, but none of them get meaningful contributions because the maintainer will most likely respond with wontfix to almost everything (if they respond at all).

I build in the open, but what I build is just for me. If someone wants to fork it and modify it, they can go ahead - pretty much all of my stuff is MIT licensed by default.

But I'm not going to start adding features to my bespoke utility to fix someone else's problem.


Shrug, it's hard to have an open app where everyone wants to add/change something and not have it turn into a Turing machine that attempts to do everything.

Sometimes you just want an app does X and Y, but not A, B and Z.


Was reminiscing about the early iOS App Store days when many apps were free and often hobby projects. Some hooked up google ads to make a nice easy profit if they stumbled on a particularly good early app idea. I don't really find apps like that anymore, or at least they don't really get shared the same way. Maybe this is a return to that in a sense.

I also don't think any particular idea is off limits for making a profit, if you do something and you do it well, you can charge a fee. But if the free hobby version is better then you best find a way to justify the price.


This is a fun article and approach.

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.


I had to download file attachments from a specific niche web forum that's behind login. I could've went looking for a browser plugin or a 3rd party tool to do it.

Once again, it took me about an hour while watching my shows to get a custom one made.

The first version operated by me downloading the pages one by one to a directory, the Python app parsed the html, downloaded the files and renamed according to thread name.

After a few iterations the tool just grabs a cookies.txt file exported from Firefox and can take any thread URL, browse through it, skipping existing files and determining if everything is already downloaded

I could easily have it just watch a set of threads for new content and download automatically, but the current system is fine =)


That’s pretty great, I’ve done something similar by hand many moons ago. It was very tedious.

I need a simple S3 compatible API to store some files with basic auth and ssl certs using let’s encrypt. Nothing crazy, Garage is overkill, Minio is overkill. I may see if Claude code can handle that for me using python or something.

/btw, I work in consulting and the above project would have a budget of probably $100k and a schedule of 3 months. I see a lot of change for swe consultants coming.


I'm doing something very similar (creating my own apps for personal use), but I'm creating iOS apps primarily.

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


I had never written an iOS app until a couple months ago and was initially very put off when I hit the same wall. The alternative is to host on a cheap VPS and find some way to prevent other people from using your app. When you cost it out, it's close enough to the 100 bucks a year for the Apple account. However, the kicker for me is the side loading process. Way too much headache compared to a deploy script that has my changes running nearly instantly.

Are you using features that can't be replicated with a PWA?

I actually created a PWA first, but it was just even more rough around the edges than the vibe-coded iOS app.

I wanted something that felt like an app, so would use iOS design elements, have widgets, use on-device storage (for offline use), etc. Apple, very intentionally I believe, makes a lot of these things harder than they need to be.


Never mind "vibecoding" (whatever it is) - quite a few free, paid or subscription apps can actually be improved for your own purposes by recreating them in a spreadsheet.

> Reel does exactly what I wanted Loom to do: I can record my camera, I can move it around, and I get to trim the video after it’s done (I don’t remember being able to do that with Loom).

But that’s not what Loom is about.

It’s about streaming the video.

Before:

Capture something with likes of quicktime.

Transcode it so that it doesn’t take a few gigabytes. This takes considerable time and resources (though OBS can do it while recording, not after).

Upload somewhere to share. Wait while it is uploading.

Loom takes care of all those steps so when you press stop you can immediately share the link with someone.

Hope other use-cases in the article are not as misrepresented as this one


I think author has a point when he didn’t needed all those extra features.

But then they did made a bad choice for paying for loom. They could have just learned (or used llm) to make a bash script to use ffmpeg for capturing screen to a file. Or OBS is a pretty good solution as well. And a ton others


Loom does also have a trim and edit after recording feature, I use it all the time

As well as auto closed captioning, and commenting, and automatically cutting out filler words and empty silent portions, and auto summarization of the contents, and many other features that I use all the time and find useful. But that’s fine, OP probably just doesn’t use that stuff.

The also have a nice trimming feature where you can trim the video by editing the transcript

The "Your" shouldn't have been stripped from the title IMHO.

Depending on how you read the owner of an app subscription (the provider or the subscriber) maybe 'My' is better.

I believe it's a play on "Your margin is my opportunity".

Reminds me of the dream of the Lisp-o-sphere : where anything and everything (and its source) is at your fingertips and editable at your whim (this is what RMS wanted to do with GNU).

There's also a story about Emacs at Amazon, where secretaries would code up elaborate things to automate their stuff. It tells you how silly our world is : we're happy with shitty uninteractive systems, languages and OSs, only so that we can fix it with the next version of "genius" AI systems which can barely do anything more than remove pain of dealing with the insane bloat.


Lower the barrier to MVP while raising the bar on the level of quality that warrants MRR. Rising tides and all..

I can hire a contractor to build a carport, or whack one together with some supplies from the Big Box store. More roofs being built with more price points to serve the market.


I agree with your point on surviving the market, but I also suspect vibe coding give rise to lemon [1] projects that only intend to get quick money and don't care about recurring revenue.

My wife was preparing for a specific exam and found an AI-powered mock exam app. The trial version was polished, but after she paid for full access she realized most contents are of low quality and some basic functionalities are broken. I imagine with LLM one might easily create such lemon products in infinite niche markets even without much domain knowledge, scam out some money from new users, and care not about survival.

[1] As in https://en.wikipedia.org/wiki/Lemon_(automobile)


it's really cool now using your technical skills and with the help of AI to build these project, i do it all the time but for a reason, it can be a good project to add to a resume or you need it to work the way you want it to be, or to cut costs in certain situations, i mainly do that to cut costs. but it's really not free, nothing is free, It may not have cost you anything in terms of money, but it definitely cost you ur time, which in my opinion is way more valuable than a $10 subscription.

Are many people really paying dozens of dollars a month for things like Markdown editors?

I get that this is tempting but it just means you'll slowly get dependent on things that will eventually break in ways you will have no capacity to fix. And disaster recovery is most certainly a manual task.

> you'll slowly get dependent on things that will eventually break in ways you will have no capacity to fix

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.


Right but most of the time, in my experience they keep the lights on.

Keeping the lights on is fine.

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.


Yep. At one point I expected the software I needed to work for a reasonable time range, possibly up to a decade. Best if you could buy it once and use it from then on.

Now crap has turned into revenue sucking subscriptions, at most yearly licensing, feature flutter. And the worst is being bought up by VC/PE and milked for anything useful and thrown away.


> Now crap has turned into revenue sucking subscriptions

So much this. Each subscription is literally a small percentage of your revenue. You can't reinvest it ... it's just gone. Hopefully it enables more productivity ... but most likely, it is only marginal.


Why wouldn't I be able to fix these things? If I managed to build a thing from scratch (with Opus 4.5), I don't see why I wouldn't be able to fix it and maintain it in the future (maybe with Opus 4.7 or even better future models?).

Why would they "eventually break"?

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).


If it's tied to web APIs, libraries, or OS version feature APIs that are deprecated it will suddenly stop working.

Non-subscription paid software will rot the same way too, so there's no change.

With a agentic llms I can just tell it to fix it. With a commercial solution I'm fucked and either have to find something else or pay for a license (or keep paying every month).


If you build enough things, you will also gain the experience to fix those things

Which is exactly why whenever I have an idea I just tinked with ClaudeCode for an hour or so until I have exactly what I need. It takes less time than trying to compare 10 similar products, none of which have the exact specifications or features that I need.

List of projects mentioned before: https://news.ycombinator.com/item?id=46716805


I am finding the same thing! I used to use a window management tool long ago called something like Zooom (it lets you press hotkeys and it 'picks up' your window and you can easily move it around). I fell in love with it like 20 years ago, but it was barely maintained. Someone then created a similar app called Hummingbird - which was great, but it had some issues and again maintainability wasn't great.

So I decided to vibecode an app for myself and wouldn't you know? It took me a few hours and it's INCREDIBLE! No more relying on someone else to maintain something, I can simply build my own solutions, whenever I want!


This reminds me so much of Maggie Appleton blog post on "Home-Cooked Software and Barefoot Developers" [1]

We have so many people who are so excellent and fast and developing nowadays that we can even afford the time to build things for our community, friends and even just for ourselves.

It has probably always been like this, but I am just personally observing a higher-degree of people doing and talking about it. Even just the small-web/neocities bobble points into this.

[1] https://maggieappleton.com/home-cooked-software


I'm very bullish on vibe coding generally, but I dont expect this will become a trend.

Most people don't make or maintain their own things, period. Vibe coding will mostly cannibalize expensive B2B contracts from a pre-LLM era where integrations and maintenance were expensive.


I think it's a question of how polished the process is. Imagine a new fully functional app popping up in your phone after a single prompt. Then, imagine you can edit this app while you are using it by saying what you wish it should do.

There might be a lot of people interested in all kinds of small apps for their particular hobbies, interests, jobs, etc


Turning a paid sub like WisprFlow into your own weekend build (Jabber) is a great move, but you can take it further by finding open-source alternatives that already implement the features you're replicating. For dictation and speech-to-text like what WisprFlow does, there's Handy[0], a free, open-source, offline speech-to-text app that runs locally with Whisper models.

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.

[0] https://github.com/cjpais/Handy

[1] https://github.com/junaid33/opensource.builders


So basically steal code from OSS, oh no I meant "get inspired by" OSS code without actually contributing anything. This is just gross as a developer imo.

We're big believers in personal software: even with OSS alts existing, building your own in your stack is valuable. Before AI, you'd read code from other apps, understand the implementation, and reimplement it yourself. This just makes that easier and faster.

My projects (Openship/Openfront[0]) are the first on the chopping block. We're creating modular OSS alts for every vertical (barbershops, hotels, etc.) for folks to take, remix, adapt, or fork into their tools. Chances are your AI model is already trained on similar OSS and building from it anyway. We make finding the exact code reliable. Check out our ethos to learn more [1].

[0] https://openship.org

[1] https://opensource.builders/ethos


For most OSS code there is no responsibility to share your changes when you're not distributing them to other people. More so there are plenty of OSS licences that simply allow other people to do just this.

You can't "steal code from OSS". The original code is still OSS.

For all the naysaying I wanted something that was “like languagereactor and anki put together” a few days ago and had it done in about two hours. And it runs on-device, because much of the time the whole reason for a cloud is to justify the subscription. And I can just install an apk (for now, I guess Google wants to steal that from us).

> I’m still skeptical of vibecoding in general. As I mentioned above, I would not trust my vibecoding enough to make these into products.

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.


Also you dont need the architecture to scale to millions of users. So it can be a bit more rough and OK to be inefficient.

And you don't need to build in user management, Stripe integration for payments, build a landing page, advertise it or anything.

You can just use it and be content.


>user management, Stripe integration for payments

FWIW, `better-auth` solves that and LLMs know how to integrate it.


I don’t think this will be a significant issue because I’m willing to bet the vast majority of people would rather spend their weekend doing something else.

This is the same for me and I've not written code for years since I was a kid in school.

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.


can you share which paid webapp you were using and maybe a link to your version's github?

The App was TeuxDeux.

I haven't published it publicly yet, as i use it personally and it's a little flakey still, but will look to do in the future once I finish adding all the features.

My version is much more feature rich than TeuxDeux and I made it for Free in Google AI studio over the past two months, between other things. I'd just type a prompt and then go do some other stuff, it has taken quite a lot of revision but I haven't written a single line of code and i've been using it daily to manage my tasks since the start of December.


The vibe-coding part is most in discussion here, so it's easy to overlook the financial part.

I build small web applications for my personal needs all the time by just regular programming, and I'm saving so much money by using them and not some proprietary app. Not even mentioning the advantages that it is completely bespoke, runs local and gives me peace of mind data-wise.

Some wise man once said that personal computers are a bicycle for the mind. Programming your own programs is the most pure way you train on that bicycle.


I think it depends on the project size and how much your time is worth. Vibe coding might be able to save some time, depending on how well it can solve the problem without needing correction.

Just sucks that instead of buying a piece of software now we're going to send $100/mo to an AI giant so we can build our own crappier bespoke apps.

I agree that spending money on claude code is stupid. But the default opencode models are free. I used one last night to replace the ad-filled alarm clock android app I use with a 90% ai written one.

I see the sceptical comments, but no one says this "vibe-coded" projects/apps/tools will be ready for your customers. It basically scratches the itch for the given users/company/whatever. Also, it doesn't have to be fast, stable or handle 1_000_000 concurrent users. You don't have to worry about that.

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.


I own a number of brands that sell on Amazon, and I've always used an app called HighFive that automatically sends the email you've almost certainly seen that asks you to rate something you bought (without it you have to click a button on each order to send it).

It's always been free, but because of a change to the way Amazon charges third party app devs, they were going to start charging next month. Since the whole app is just a couple of API calls and storing a record of which orders you've sent the request to already, Claude Code built it in 5 minutes.

In general, the Amazon Seller UI is a cluster (especially since I have one account for each brand, so I constantly have to switch between them). There are lots of subscription apps to make your Amazon data more useful and accessible, but Claude Code with access to the Amazon APIs pretty much replaces all of them. I spend very little time in the actual Amazon UI now and mostly just ask my trusty assistant for the info that I need.


> automatically sends the email you've almost certainly seen that asks you to rate something you

Just FYI, most of us maintain blacklists of sellers who do that and would never give business to one again, even if it requires paying more. If I bought something from you, that is not permission to email me anything other than a tracking number. Ever. If i like it -- i'll review it mysef. If i dislike it -- i'll email you. Note the direction of comms here.

Making you click a button per-order was perhaps Amazon's way to add friction to this -- to avoid poor users being spammed with endless review requests. I am sad that someone automated the friction away. I hope that one day amazon starts charging sellers a nontrivial fee per such email sent.


There's only 50 weekends in a year. And there's a limited amount of years. I'd rather pay $10 and spend the weekend sailing.

> There's only 50 weekends in a year.

That's sad for you. Do you spend the other two weekends dead for tax purposes?


This hits close to home. I've been building tools for bookkeepers and accountants as a side project, and the calculus you're describing - where a subscription becomes a weekend obligation - is exactly why I've tried to keep things genuinely useful rather than sticky.

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.


I doubt LLM-generated software is going to replace more traditional software any time soon, especially when accuracy is pretty important (such as accounting). One thing I learned from years as a PM in a very data-centric organization is understanding data, how it is generated/stored/cut/etc. is very important to getting accurate results.

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.


i think the same, i think backend where data is more prominent is not going anywhere soon. llms produce very bad data structures.

but from good apis, good data, good interface they can generate quite nice frontends.

i guess, frontend as job is going to have a hard time.

also, writing code is not cognitive load, its always reading code. and llms just increase that. so i mostly try to avoid using them.

but i do like researching with them. context free. like googles ai mode, etc. not from my code editor cause then they get biased and suggest stupid sh8t all the time.


https://www.databricks.com is doing this already with data as well as multiple other companies

And I have first hand knowledge of well-known companies building their own tooling because the SaaS offerings have a bad price/feature ratio.


You can pivot your knowledge into building bespoke tools for the same people, just a LOT faster.

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?


It’s easy to overlook what I think is the real value of these “home-built” tools.

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.


> which can be as low as $20 per month for a ChatGPT Plus subscription

That's way too much money. The opencode default models are free


Loved the article, thanks for sharing. I’m curious if you’d share your setup. I haven’t made any macOS apps before, primarily because I never wanted to really learn XCode and obj-c. I like swift but still prefer simpler editors like Zed/VSC vs. What XCode offers.. so when you’re building these are you doing it in XCode or in another tool like Claude Code/codex/gemini CLI?

cheers


I've been using Cursor with the Swift Extension. Works really nicely, but sometimes I switch to Xcode to do some tasks such as testing that it works to build.

Seconded, I would be interested in knowing people's workflows + experiences developing MacOS and iOS apps with claude, etc.

From the repo here, it looks like its just using swift command line tools, which might just work well enough with cursor/vscode/etc. for small projects. You won't have Xcode's other features but maybe thats fine for an agentic-first development workflow.


Not OP, but I use Xcode with Claude Pro and it is going fairly well. I also am creating my own personal-use apps instead of paying for monthly subscriptions. I know a bit of Swift, and had been trying to learn it while also using LLMs. At this point, I've decided to also not make these real projects and just vibe-code exactly what I want.

> I’m often asked to make small videos showing some support agent how something works

Fwiw, Google has had a free in-browser tool for this for ages, makes capture really simple on any device with a browser: https://toolbox.googleapps.com/apps/screen_recorder/


Zapier also has a free product which works well - https://zapier.com/zappy

I'm surprised people were paying for software like this, and with subscriptions no less.

Yes, the options presented were overpay for something or roll your own. Could you not try to find a better alternative first?

Yeah, a little bespoke editor is exactly the kind of thing I'd've been happy to fork over a one-time cost for, but never a subscription. Interesting!

why even pay for that, just use a free model from Opencode, most of them are pretty good for simple tasks. I haven't paid a cent in vibe coding for ages.

I was hoping that the current LLM/Agent/Vibecoding wave would lead to a revival of open source contributions, but I am not sure that is happening yet

The incentive for sending in patches was that you needed to fix a bug in software you were using for your own use case, so you might as well send the authors the patch, and they'd keep maintaining it all for you. But if you can vibe-code your own solution, you don't need to use somebody else's software, so the patch doesn't get made, much less submitted.

The other thing is, LLMs tend to generate terrible code that pisses off open-source maintainers. So I'm not sure even LLM-made patches will make it into open source much.

This might be the death of traditional open source. Vibe-coded-only open source may be the next generation. Which I'm fine with, as long as we can start regulating software, so that vibe-coded tools are banned for safety/privacy uses unless they follow a software building code.


I think it's happening, some of them are even making it to the front page of HN, like the "I built 50 calculators" a few days ago. I'm still working to release some of the things I've built over the last month:

- A nice little single-file web "random slideshow" to replace an aging one I bought. - A fairly feature-complete read-only SQL console. - A development SMTP server (like Mailhog) https://github.com/linsomniac/smtphotel - A work status dashboard that I'll probably release once I have run it a bit longer. - A fairly extensive Docusign-like webapp. - A retrospective meeting runner. - A cron "swiss army knife" helper. - A "social calorie tracker" (I'm unhappy with the existing ones out there).

These are all things I've vibecoded in the last month, and are more than I could have coded in my spare time in 6 months or more.

For me, the renaissance is here.


For me it makes sense because coding agents have made software development fun again, so I do more of that than playing games or surfing the Internet.

So if you can get a good LLM model locally in say 6 months, you may never pay for any subscriptions. Only companies will remain will be old behemoths whose software is contractually bought by other big enterprises.

Other thing I have experienced is my standards have changed a lot, now for $10 subscription I need a lot more, not just some simple editor or a small todolist would suffice anymore. I am not thinking about paying for new software, and in fact I am getting completely burnt out by all the sites looking the same.


A while ago I made the bold claim that I could build "your app subscription" in a week and got ridiculed for it. Now it's down to a weekend and lot less ridicule.

If you were using Loom for just recording, please use OBS instead!

Creating tools for your own workflows has become amazing, especially as a creator of anything it feels overwhelming with how many options there are now.


A few of the tool choices in the article seemed uninformed though, e.g. for markdown editing you have perfectly functional (and open!) tools that are free and powerful with good UX.

I've been using a Wispr equivalent I made myself since 2023. It's wild to me that people pay for it, and I've wondered if I should try to monetize what I use. It is not as slick and polished, but provides essentially the same service: better speech-to-text than the built-in speech-to-text for Macs.

As a rebuttal to “SaaS is still cheaper!” - I like this because it makes coding more of a personal and enjoyable hobby. It also is empowering to the creator and gives them ownership of their creations and what their creations create

I like this approach, at least for personal apps. I have started doing this myself, which also led into me learning to use LLMs better and more productively.

The other side of the coin however is a potential decline in indie hacker products.


Excellent! I've done the same thing. Five prompts to have a working iOS app that solves my problem.

As a non iOS user wouldn't be the hard part getting it on the phone? The last time I checked you would still need apple hardware and 100$ per year for the developer license or something like that.

Technically you can upload it to your phone for free, but you have to re-upload it every seven days, which makes it pretty frustrating.

Good. Good good good. More of this.

I feel like if e.g. Hypercard had lived, this would be a more defacto mode of doing things.


This is where claude code is so good because all the stuff AI is bad at - security, auth, storage - are not a problem if its just you using it locally

Has anyone tried, on a large scale, designing the architecture of an application or writing behavioral tests (which effectively is designing the app through testing) and given the LLM the task of writing the implementation details?

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?


I keep seeing versions of this soliloquy on here, sometimes multiple times every day. They make fine blog posts, it's something to say and something to read, but ultimately remind me more of piling into a Tiktok trend than anything else: everybody's doing it, so I will too!

End of the day, much like when photography went digital (and smartphones got good cameras), yes, there were a LOT more photos taken, but the relative proportion of outsized, lauded photographers remained fairly constant. The upshot is that WAY more people are exposed to the possibility of creating excellence than before, the downside is the market gets flooded with utility and mediocrity. Said excellence never goes away, and the same will apply to software.

The very idea that SaaS (or packaged software, or whatever) "will die" because "anybody" can prompt their way to a "personal tool" (as a mainstream exercise) is so far-fetched to me because the only people who will prompt their way to a tool ARE SOFTWARE DEVELOPERS!

Professionals who need functionality will always pay for it.

Boomer dads who can barely work a DVR will always pay for it.

Business owners who need less friction and more reliability will always pay for it.

IMO, this "I'll just replace Salesforce with my own personal CRM for $200 for a month of Claude" thing is just a hobbyist's pipe dream lol -- not that there's anything wrong with it, some people will do it, but, man, there's a reason that Netflix is Netflix, and Plex isn't Netflix.


Most small businesses don’t need the complexity of Salesforce and people use Netflix for the content, not the software.

I don’t understand why Netflix needs 3500 engineers. They built what needed to be built already.


I did this recently at the company I work at. Someone suggested GitBook, I 'Vibe coded' an internal docs website in under and hour. Does what we need, looks good. Unless the app has a large community/network and is just a SaaS with some offering, it'll be very easy to replace it.

It's interesting, because a few years ago I would have put this strictly under the "not invented here" fallacy, where we'd now be stuck maintaining another project for the foreseeable future. I used to press pretty hard to avoid it.

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.


I can see it going both ways. If knowledge work continues to roughly look the way it looks then I think maintenance is going to be an issue. Both in terms of keeping the spaghetti together but also in terms of all the bad design decisions you get from everyone bolting on their ideas. If however knowledge work becomes just talking to LLMs and occasionally interacting with an on the fly generated UI then maintenance becomes a non issue

We're currently paying through the nose for a shitty intranet solution that could've been just hugo with a markdown editor.

Or a vibe-coded simple website.

But "designed and implemented company-wide intranet" looks good in someone's CV so here we are.


Software itself is not inherently valuable, the value is in running and maintaining its data and any necessary integrations to other systems.

The bar for me to pay for a $10/month software subscription is pretty high, but once I make the decision that it's valuable, the actual cash cost is pretty low. Vibe coding something will never approach the quality of something that someone put enough thought and effort to turn into a product. The main place where I'll write my own software is when it's truly custom to my own needs, AI is a force multiplier for this type of work, but at the end of the day I still have very limited time to run and maintain a lot of custom software and data, so it's not going to cannibalize any of the SaaS I'm willing to pay for.

Obviously for younger software guys with more time than money, the equation will be different, but those were never the make-or-break demographic for SaaS anyway. I don't think the equation has meaningfully changed for SaaS sales due to AI, I see it more as continuously rising bar over the last two decades due to UX expectations, market saturation, limits on human attention and complexity tolerance.


The prevalence of this "personal vibecoded app" spirit makes me start to wonder if an "App" is the right level of abstraction for packaging capabilities. Perhaps we need something more "granular".

Personally I hope we land on "widget" although I'd settle for "thingamabob"

I’ve been doing something similar and thinking about this in the last 6 months or so. It’s pretty crazy.

I made Vissper which is essentially the same. Have a look, it's open source svenmalvik/vissper-oss on GitHub.

"Reel does exactly what I wanted Loom to do: I can record my camera, I can move it around, and I get to trim the video after it’s done"

- tell me you haven't heard of OBS studio without telling me you haven't heard of OBS studio. But on a serious note OP, you should really give OBS studio a shot, it is one of the best video recording tools out there, period!


it doesn't have to be free. it can just be a lot cheaper or open source.

And one day your day job will be someone else weekend project

Only assuming a sufficient number of your customers is happy and capable to vibe-code a product for their set of the requirements that your product solves.

Whats the future of being able to make money selling software with these changes?

Target undeserved businesses with niche problems that have traditionally been ignored by tech companies because those markets have always been considered "too small" to be worthwhile.

I should vibecode my own Onshape.

what is reel doing for osx that quicktime screen recording isnt getting you?

By the same logic it was one git clone away.

You shouldn't pay for most software unless it's stuff like Maya, excel. Paying for a markdown editor is just like paying for an egg slicer.

This is great until it becomes a maintenance nightmare, some people don't mind paying as long as the software always works as expected and is high quality.

Some apps just do not make any sense for monetization and are now raced to zero. If it's not already open sourced then someone will vibe-code an implementation if none exist.

Vibe-coding accelerates the destruction of basic (closed-source) apps charging a subscription for features that offer little to no value whatsoever.


The SaaS business model took things too far anyway. Everything is a subscription and it gets tiring quickly. I am glad that LLMs can replace crappy SaaS with crappy code now.

I replaced a whole bunch of these with one shot prompts for shits and giggles.


So tired of these posts about people jerking themselves off over how good they are because they used AI to shit out some trivial bullshit. Like, I'm glad you're saving time and money. That's what AI now does. It's what millions of other engineers here --already know--. But why do we have to know about it? Is it remotely noteworthy or unexpected? Why does HN continue to upvote this self-serving, gratuitous, bullshit? Do you guys want HN to look like OP for the next [however long] this AI hype cycle takes to reach saturation (probably another 5 years at this point.) Even the biggest AI soyboy will be sick of it by then.

I think there's still an underestimated burden to vibe-coding an app for a non-software engineer. I'm not recommending my parents vibe-code apps to solve problems, so I think the market is smaller.

But Roberto's use-case is definitely more sane than most.


I'm currently assisting three very non-programmer people in-house who did just this.

Their problem is solved, now it's up to me to update the internal guidelines and agent instructions so that the code is at least semi-decent.

None of these are going to "production", they all live on local company controlled laptops and only one of them might access an external API automatically later this spring.

But each of them takes hours of manual work and does it in minutes.


With the current tech, I agree this will still be pretty niche. I'm vibe-coding my own iOS apps, and it still needs a decent understanding of the tech and a willingness to put up with a lot of rough edges.

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.


I assume the learning curve will get shallower over time. Onboarding is better than ever and will only improve. Lots of 70 and 80 year olds on Facebook now, and future Facebooks will verbally handhold you as you log on. "Press the red button that I just highlighted... great job!" etc.

Thats not cheaper than paying a subscription. In fact this is at least 3x-10x more expensive.

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.


$20 claude code subscription for a month can replace the $15 + $10 for each month. How is that 3x more espensive? The user just saved $280 per year, on just two subscriptions alone.

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.


Hey, CC has a way to trigger a notification chime on completion.

(How? Idk, I just asked it to guide me through the short hook process)


Afaik it's built in now.

I get a notification on macOS with the title of the context.


Yup. thats more expensive because each hour of your time is at least 50USD And each hour on weekend that you would have spent with your family etc is probably 500-1000 usd at least, so yeah, it is much cheaper to pay 15 usd for SaaS

Most (all?) of these examples are products where the product is the UX not the functionality. macOS has dictation, there are free screen recording apps and you can use a normal text editor for your blog. There is no need to create a half-assed software that you don't understand and might break unpredictably at some point when there are free alternatives; and even open source ones you can download today.

The interesting question is why the OP had bought these subscriptions in the first place if he was happy with less-polished alternatives.


I must admit that I find this thread very funny. "Spend $200 a month so that you can waste a weekend to make a shitty clone of a SaaS app so that you can save $10" is... somewhat questionable, as far as sensible decisions go. Some people even seem to assume that this is a death kneel of the entire saas app industru, since everybody can just vibe code an inferior knockoff of bejeweled or whatever.

It just boggles he mind how divorced from reality some people are. You could offer $fotm_ai_model with infinite usage, free apple developer account (since you're apparently replacing everything you have with homegrown stuff) and the amount of people wasting their weekends on vibe-cloning their own custom apps would still approximate to zero. This doesn't even get to the fact that the majority of apps already HAVE a free alternative, and it's certainly far less effort to replace increasingly obnoxious apple music with foobar than to build, test and then permanently support your own music player. You also probably want claude code 15 to replace anything non-trivial, otherwise, well, good luck.

I don’t think I’d bother even if my weekend had ten times as many hours as it does, and I’m a code monkey that still mostly enjoys his job.


> I would never sell it as a product

I wonder why people still hold a lot of stigma against something that was built assisted by an LLM.


I don't think it is "a stigma against something that was built assisted by an LLM." I think the author is coming at it in the same way I do with some similar tools: "this is good enough for me, I am the end user, and I don't have the time or desire to iron out a bunch of edge cases or make things for more than one user."

I am rewriting my website. I was using a converted Pelican template. I started the rewrite using variables similar to the template, then about halfway through, I realized, "this is dumb. I am the only user. I care about nobody else. I can hardcode nearly all of this, and if I want a change, change the hardcoded name." An example of this was various social media names.

I have scripts that convert color themes for applications from more popular themes to a theme I particularly like. I hard-coded the input colors and output colors. I could have made a config file, etc, but, that adds complexity and, more importantly *I do not care about other users.*

There is a huge leap between "good enough for me to use for exactly my use case" and release or sell as a product.


I've been evangelizing vibe coding, because we are wielding something much more powerful now than even ~3 months prior (Nov was the turning point).

Now that Prometheus (the myth, not the o11y tool) has dropped these LLMs on us, I've been using this thought experiment to consider the multi-layered implications:

In a world where everyone can cook, why would anybody buy prepared food?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: