41–50 of 390 posts
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.
Earlier quoted context omitted.
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…
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.
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.
[flagged]
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.
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.
[flagged]
The recommendation thing is a nice benchmark, but if you're building hyper-specific tools - why would people recommend them to anyone? If you build a tool for an accountant that does some very niche thing only they're bothered by, why would they recommend to the analyst or receptionist in the company?
I'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…
> 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.
You can just use it and be content.
[flagged]
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. Fo…
And I have first hand knowledge of well-known companies building their own tooling because the SaaS offerings have a bad price/feature ratio.
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.