> I haven't seen any real competitor of YouTube, or Figma, or Google, or Instagram created solely with AI.
Is a ridiculous set of products to expect competitors for. First all but 1 rely heavily on network effects. YouTube is a low cost provider. Think about it, they provide unlimited high quality video storage for free. They process 500 hours of content every minute. Google and Instagram have a huge network all users benefit from. AI can't help you bootstrap this network.
The only one that's fair is Figma, and considering Figma is down 30% from IPO price (much lower from ending day close), it's fair to say there are competitors to Figma, including the LLMs themselves.
That begs the question: what is product? Is "an app for designers to change style and communicate with developers" the product? Or is the product "to make websites look pretty and well organized"? The former, Figma is great. But if the product is the latter, LLMs are a real threat. No one would bother building a "better Figma" today, why would they? They would just solve the problem Figma purports to solve
Yeah, I agree that YouTube, Instagram, and so on are a high bar. Not even the people who created these companies twenty years ago would be able to replicate the success of these products. My goal with this article was to highlight the hidden complexities behind any meaningful product. For example, how will I store the user info and settings? What if the user regrets buying my product? What if it is too complex? Who are the target users? And so on. Many questions that no single prompt can satisfactorily give us answers to without putting real thought into the thing, and none of this is shown in the demos we see around. Anyway, I loved all the insights I got here. Thanks for taking your time to write a reply.
I also think you under appreciate the value of toy software. We’ve spent 20 years talking about serious practices for making serious software but what if the next 20 years is about making personal toys that scratch our own itch? Perhaps LLMs fill this need quite well and they aren’t suppose to replicate what already exists.
The next Google won't be a search engine with 10 blue links. Why would anyone create slightly better legacy apps.
For instance, Claude is 100% a competitor to Salesforce and there are go to market companies like Clay that manage outreach of a salesforce. Small companies can easily spin out a simple system that can source people to reach out, track follow ups, help w copy and even coordinate email.
That’s because no one wants to admit that their product is vibe coded… But there are plenty of vibe coded products out there making money from actual users.
It’s a great question, but I don’t think the article answers it.
Not in any academic sense, but in a real-world sense a software product is something that as a user you can rely on to solve a problem. Rely is doing the heavy lifting in that sentence.
You can rely on a vendor’s product if (a) they’re going to be around for a long time, otherwise the investment into adopting it isn’t worth it; (b) the vendor is committed to solving your problem in an ongoing way - meaning they understand enough of the domain (ideally more than you do) that they’re going to be a partner even as your own needs evolve; (c) they deliver the product in a dependable way - high uptime and security.
So it comes down to “can you depend on this software over time?”
A product is much more than the software and its reliability. The business side is just as big of a lift. You need to build a business, not just a product. A business includes understanding the value proposition, not just a potential solution in the form of a tool. It includes understanding how the software fits in to the target customer's workflow, and how it provides real value. You need to be able to communicate that value proposition to the customers, investors and your employees, amongst other stakeholders. Later, this transforms into understanding the sales cycle and how to use marketing to grow your users. The business side has always been the hard part. Software was always easy to build. The hard part is knowing what to build that really provides value.
I hate the ‘product’ word. In the 90’s I was involved in a travel startup, and the software people would be talking about ‘product’ meaning the website that we where building, and the travel people meant what we where offering in the way of hotels, insurance, flights and excursions.
The word ‘product just left everyone confused.
If one uses a word like platform, application, prototype, offering, ‘products’ this makes it clearer than just the generic ‘product’. It’s even better if goal is applied as well. For example Flight finder Application, or Video Playback Platform.
> I hate the ‘product’ word. In the 90’s I was involved in a travel startup, and the software people would be talking about ‘product’ meaning the website that we where building, and the travel people meant what we where offering in the way of hotels, insurance, flights and excursions.
In that case (but IMO it applies to almost everything that's not selling a software or technical solution per se) the product IS the hotel/insurance/flights/excursions package. There is no other way. The website was never the product, it was just a channel. The difference is that especially back then the only way to use that channel was to build it by yourself. And that's something that actually happens for big enough brick&mortar stores: they do have an internal department that manages the stores, buy/rent the spaces, furnish and decorate them etc.
This just reads like someone's cross at the AI hype and wanted to take a shot, but missed.
The underlying point --that network effects exist and determine the success of a product-- has always been the case, long before AI made it possible to vibe code a rough Instagram clone in a weekend.
Anyway, if you want a successful new product, the path to success (obviously) isn't likely to be copying an existing behemoth, but offering something new, unique and valuable. That's always been the (exceptionally difficult) challenge, and AI doesn't help with this. But I think we can be confident that in the future, as humans do create new, unique, and valuable products, some of them will probably be vibe coded.
You may say that, but it seems to me that by definition vibecoding things will make them less unique because the technology is best suited to reproducing best practices even when those are cumbersome. Your best case scenario is a nontechnical person with a bright idea vibecoding something far beyond their ability to understand, and that's a recipe for implementation problems that'll harm the value of the novel thing being created.
You can still create enormous value modelling things that are well understood, and even boring. Most LOB SaaS wasn't created from deep Google-level engineering, it was taken in modelling an ugly workflow in CRUD and creating customer records, job scheduling, worker assignments, quotations, recurring contracts, invoices, inspection checklists. Most Construction Tech startups for instance today is this.
>A real product has real users, a real market and solves real problems.
This misses the mark.
A product is something which can be exchanged with others, transferred into their agency, for them to own and use according to their free will.
They don't have to use it or indeed 'be a user' - it is up to them whether or not utility is derived. The only requirement is that it is exchangeable and that agency has been transferred in such a manner that all parties involved in the exchange are satisfied with the transfer of agency.
A project is some activity which has an expectation of changing state over time.
Project management means projecting the scope and sphere of that activity into the future, in order to change its state in such a way, hopefully, that something exchangeable is produced. Product management means, making sure a satisfactory exchange occurs between the creator of a product and its new owner.
So many people get this wrong.
It is not a product if it's a project. It is only a product once it has been exchanged with another entity for their purposes.
You can have many, many projects which will never become products, because they won't be exchanged with others. You can have products which are valued by their owner in ways unintended by their creators. The value and utility is arbitrary to whether or not something is a product - the only requirement for something to become a product is that it is exchanged.
Successful product(S) are exchanged at scale. A single product can be very successful if the scale of that exchange is high. A lot of products can be very successful if the number of exchanges is great.
Until the exchange occurs, it's not a product. It's a resource. Inventory.
Side projects become products only once they are exchanged.
There really are plenty of Google analogs. There are plenty of chatbot analogs. Any one of us can recreate Instagram or X. These competitive analogs simply have not become products, because they have not been exchanged. Products which harness human collectivity have the problem of not being exchanged at scale until the collective decides to participate in the exchange, i.e. recommend their friends sign up to join them.
The problem with easily started new side projects is that they are not so easily exchanged at sufficient scale.
Not sure I understand the need for the exchange at scale. If I build a tool that lets a single person automate a tedious calculation then as long as they can depend on me maintaining it then it’s a product as far as I’m concerned.
Yes, I guess I wasn't clear: it's a product if it is exchanged - at all. At any scale. (There was a missing 'any' in my original statement.)
You can sell a single product for an enormous price, you can sell 1,000 products at a low price - the only thing that matters is that the two parties agree to conduct the exchange at any scale and, most importantly, that it actually occurs.
Common to both high-end scale and low-end scale scenarios, is that the exchange occurred and all parties agree to it. That's the only thing that makes something a product - the exchange.
Not sure how you're missing it. He's making a distinction between the concept of a Project and a Product. I agree with the distinction and he seems to be saying that the author has the wrong concept of what a product is but to answer your parent comment is saying that there's no difference between a vibe coded thing and a 'real' product so long as there has been some satisfactory transfer of agency and an exchange between user and product creator at any scale. So he's essentially saying that the author may be conflating vibe coded PROJECT (with a vibe coded PRODUCT) and that if so comparing a vibe coded PROJECT with any 'real' (whatever that means) product is an unfair comparison and on the flip side if they're comparing vive coded PRODUCT with a real PRODUCT then they're one and the same thing from the perspective that there was an transfer of agency and utility has been exchanged between user and product creator. I happen to agree with parent comment. It's an airtight argument that it doesn't matter how yu made it. The distinction between vibe coded and 'real' product is fuzzy at best. The real distinction lies between a PROJECT and a PRODUCT.
It doesn’t matter one bit how you made it, as long as you’ve got someone who is willing to exchange with you, for it. That is the only factor in determining whether something is a product or not.
Nobody wants to know how the sausage is made. Vibe coding is just sausage-making.
My office has cut down SaaS costs by a couple of tens of grand a year, simply by making our own versions using LLMs.
It is not that we didn't have the expertise to do so to begin with, but it would simply have been too expensive and time consuming. That was solved once the models became good enough.
There's a lot of money in the SaaS world, where the products are both unglamorous and one-trick pony-ish. Making your product LLM-proof can be challenging today, unless you happen to own a lot of data or lots of compute, and those two are the drivers behind your product.
The issue is most of these demo are created by developers. Most of the developers don't have interests or skills in product and design. So they use AI to write code, not build product.
Another mistake everyone making is not building better and bigger products. What is used to take a month to develop is now possible in few days but most don't put the same effort as before to make bigger and better products. They just do they same as what they used to do before but quickly. This is a mistake. AI uplifted everything so products built with AI should go to next level.
I'm an indie mac app developer. My first product took me 6 months to develop without much AI. I just released my second app ( https://www.vinaa.ai/ ) but took the same time to develop as I wanted it to be the best AI chat app. So I spent a month building my own markdown renderer in TextKit as existing library are not fast enough. I wouldn't done this if I don't use AI.
Maybe what these llms open up is the ability to create personal tools to get xyz job done, rather than creating companies with polished products. Perhaps for the latter you'd still need some combination of team, timing, etc.
But the question of should I spin up my own website in a few minutes or use wordpress for my blog is now open. Your personal tools can compete with what's out there and you may decide what you build in one session is more compelling than what the "pros" are offering.
And for personal tools you are much more forgiving for the mistakes if it gets whatever task you want done.
I think a product should answer a specific need, it cannot be fully defined internally, it is an expression of some need in the environment which makes it a legitimate product. A product with no viability soon ceases to be a product. Generating code is not the same with answering a need, it is orthogonal. Good products have market fit, not necessarily are themselves well written apps.
The vibe-coded demos everyone's tired of are code with no environmental need pulling on them.
The problem is that getting your first user or first $1 is not particularly easier with even the best LLMs to help you. Distribution is brutal — Google doesn’t want to index new sites, Twitter doesn’t want to distribute lowbie posts, right here HN’s /new queue is mercurial ..
What happened to HN's new queue? What changed? I only watch homepage so I wouldn't know.
Also, dang ought to make a new tab "Trends" (or just name that "AI") and move all AI/LLM/etc posts there. We might possibly see something other than AI then.
> So building is faster, but marketing—not so much
Producers are AI/agents now but consumers are still human beings. Maybe it will be different when it will be: by the AI, for the AI, of the AI… etc and humans will be safely out of the consumption loop.
I don't disagree but for some of the examples given (YouTube, Instagram, X.com) a huge entry barrier is the network effect. Even if AI could perfectly clone these products in a day, that still doesn't translate to instant market share.
If the things created with AI lack originality, they are nothing more than clones, rather than prototypes. While I agree with the majority of the text, I really don't understand why the amateurish efforts of so many are taken so seriously, to the point where people actually obsess over them. The marketing of these outputs by individuals or organizations with no prior connection to the industry (especially on platforms like YouTube, Reddit, HackerNews, etc.) is driven solely by self-interest. These ideas only excite the laypeople and the naive. For a professional or anyone who actually knows how things work, these are—as the name implies—just tools for now, not the be-all and end-all.
In real terms a product is the delivery of a service or other item of value. Specifically within the realm of software it is the promise of the delivery of software that will do what it says it will do, and then maintain or fix it where it falls short.
E.g. it's now about the delivery of a service rather than the challenge of building it (e.g. the moat) and then the delivery of service of it afterwards. Non functional requirements like data management and security, legal requirements and hosting are still valuable things that aren't front of mind for most developers creating their own tooling.
But is the definition of the product really just something that has loads of users. If so than the best "product engineers" are just people with gigantic following since every url they share would get traction.
Imo a better distinguisher of demos and products is: "is your thing CAPABLE of solving a real problem" (even if it isn't doing so at a scale atm). Google+ was a product (not a super successfull one), eventhough it didn't have many users. Conversely, a viral interactive gimmick can attract millions of users in a day without really being a product at all.
A product is just a software output packaged for sale. Most products these days are actually services, where delivery of the application is as important as its development. One man’s prototype is another man’s MVP. You can’t No True Scotsman your way into discounting the fact that low quality software can still make money.
Since everyone has access to the same tools, what exactly has changed about building a new business? Are people really expecting brand new companies to just displace the existing ones? What separates one company from another looks the same as always to me risk tolerance, etc. Now with the added benefit of a lot more competitors, plenty of who can't actually execute, all making noise in the market.
Why hasn't someone upended LinkedIn? It is not because the product is incomplete. It is because LinkedIn is the incumbent with millions of users and an ecosystem and culture and gravity around it.
This article is riddled with logical fallacies. And this is a very Silicon Valley-esque, growth-minded, narrow way of thinking about this new world we live in.
I maintain half a dozen products, some of which enjoy only a handful of dedicated users, and I consider them all a resounding success. We are living in a new future of readily available custom software for extremely niche use cases.
> Don't feel bad if you don't have anything to show up with all the free intelligence available nowadays. Almost nobody has.
But I can empathize with the author's attempt at "vibe writing" something meaningful, considering that they seemingly don't have anything better to "show up with".
What is a product? So you take two natural numbers `a` and `b`, and you want to sum `a` for `b` times, or vice versa. Then things become complicated if you want to do that quickly...
I think it ultimately just comes down to laziness. People are increasingly loathe to make multi-year plans and stick to them, for various reasons.
Building something like a YouTube competitor is theoretically doable by a small team. It’s vastly more possible with AI tools than it was a decade ago.
But the “muscle” of doing difficult things has atrophied for many people, in large part because the AI tools themselves reduce your ability to actually do the work. If day after day, you just prompt an AI to make things for you, do research for you, etc. then you gradually stop working that muscle yourself.
It makes me think that the ideal usage of AI tools might be a deliberately limited one: do everything on your own, but check in with the AI once a week for review.
In term of business, the era of "MVPs" have long sailed already, probably 95% of every projects released now is done so lazily that you can know in the first 5 seconds that the company will die in the coming months.
I agree with the point generally but:
> I haven't seen any real competitor of YouTube, or Figma, or Google, or Instagram created solely with AI.
Is a ridiculous set of products to expect competitors for. First all but 1 rely heavily on network effects. YouTube is a low cost provider. Think about it, they provide unlimited high quality video storage for free. They process 500 hours of content every minute. Google and Instagram have a huge network all users benefit from. AI can't help you bootstrap this network.
The only one that's fair is Figma, and considering Figma is down 30% from IPO price (much lower from ending day close), it's fair to say there are competitors to Figma, including the LLMs themselves.
That begs the question: what is product? Is "an app for designers to change style and communicate with developers" the product? Or is the product "to make websites look pretty and well organized"? The former, Figma is great. But if the product is the latter, LLMs are a real threat. No one would bother building a "better Figma" today, why would they? They would just solve the problem Figma purports to solve
Yeah, I agree that YouTube, Instagram, and so on are a high bar. Not even the people who created these companies twenty years ago would be able to replicate the success of these products. My goal with this article was to highlight the hidden complexities behind any meaningful product. For example, how will I store the user info and settings? What if the user regrets buying my product? What if it is too complex? Who are the target users? And so on. Many questions that no single prompt can satisfactorily give us answers to without putting real thought into the thing, and none of this is shown in the demos we see around. Anyway, I loved all the insights I got here. Thanks for taking your time to write a reply.
I also think you under appreciate the value of toy software. We’ve spent 20 years talking about serious practices for making serious software but what if the next 20 years is about making personal toys that scratch our own itch? Perhaps LLMs fill this need quite well and they aren’t suppose to replicate what already exists.
That list is a pretty high bar but you can make it as low as you like and it’s still crickets.
Read the second half of my response.
The next Google won't be a search engine with 10 blue links. Why would anyone create slightly better legacy apps.
For instance, Claude is 100% a competitor to Salesforce and there are go to market companies like Clay that manage outreach of a salesforce. Small companies can easily spin out a simple system that can source people to reach out, track follow ups, help w copy and even coordinate email.
That’s because no one wants to admit that their product is vibe coded… But there are plenty of vibe coded products out there making money from actual users.
It’s a great question, but I don’t think the article answers it.
Not in any academic sense, but in a real-world sense a software product is something that as a user you can rely on to solve a problem. Rely is doing the heavy lifting in that sentence.
You can rely on a vendor’s product if (a) they’re going to be around for a long time, otherwise the investment into adopting it isn’t worth it; (b) the vendor is committed to solving your problem in an ongoing way - meaning they understand enough of the domain (ideally more than you do) that they’re going to be a partner even as your own needs evolve; (c) they deliver the product in a dependable way - high uptime and security.
So it comes down to “can you depend on this software over time?”
A product is much more than the software and its reliability. The business side is just as big of a lift. You need to build a business, not just a product. A business includes understanding the value proposition, not just a potential solution in the form of a tool. It includes understanding how the software fits in to the target customer's workflow, and how it provides real value. You need to be able to communicate that value proposition to the customers, investors and your employees, amongst other stakeholders. Later, this transforms into understanding the sales cycle and how to use marketing to grow your users. The business side has always been the hard part. Software was always easy to build. The hard part is knowing what to build that really provides value.
I hate the ‘product’ word. In the 90’s I was involved in a travel startup, and the software people would be talking about ‘product’ meaning the website that we where building, and the travel people meant what we where offering in the way of hotels, insurance, flights and excursions.
The word ‘product just left everyone confused.
If one uses a word like platform, application, prototype, offering, ‘products’ this makes it clearer than just the generic ‘product’. It’s even better if goal is applied as well. For example Flight finder Application, or Video Playback Platform.
> I hate the ‘product’ word. In the 90’s I was involved in a travel startup, and the software people would be talking about ‘product’ meaning the website that we where building, and the travel people meant what we where offering in the way of hotels, insurance, flights and excursions.
In that case (but IMO it applies to almost everything that's not selling a software or technical solution per se) the product IS the hotel/insurance/flights/excursions package. There is no other way. The website was never the product, it was just a channel. The difference is that especially back then the only way to use that channel was to build it by yourself. And that's something that actually happens for big enough brick&mortar stores: they do have an internal department that manages the stores, buy/rent the spaces, furnish and decorate them etc.
This just reads like someone's cross at the AI hype and wanted to take a shot, but missed.
The underlying point --that network effects exist and determine the success of a product-- has always been the case, long before AI made it possible to vibe code a rough Instagram clone in a weekend.
Anyway, if you want a successful new product, the path to success (obviously) isn't likely to be copying an existing behemoth, but offering something new, unique and valuable. That's always been the (exceptionally difficult) challenge, and AI doesn't help with this. But I think we can be confident that in the future, as humans do create new, unique, and valuable products, some of them will probably be vibe coded.
You may say that, but it seems to me that by definition vibecoding things will make them less unique because the technology is best suited to reproducing best practices even when those are cumbersome. Your best case scenario is a nontechnical person with a bright idea vibecoding something far beyond their ability to understand, and that's a recipe for implementation problems that'll harm the value of the novel thing being created.
You can still create enormous value modelling things that are well understood, and even boring. Most LOB SaaS wasn't created from deep Google-level engineering, it was taken in modelling an ugly workflow in CRUD and creating customer records, job scheduling, worker assignments, quotations, recurring contracts, invoices, inspection checklists. Most Construction Tech startups for instance today is this.
>A real product has real users, a real market and solves real problems.
This misses the mark.
A product is something which can be exchanged with others, transferred into their agency, for them to own and use according to their free will.
They don't have to use it or indeed 'be a user' - it is up to them whether or not utility is derived. The only requirement is that it is exchangeable and that agency has been transferred in such a manner that all parties involved in the exchange are satisfied with the transfer of agency.
A project is some activity which has an expectation of changing state over time.
Project management means projecting the scope and sphere of that activity into the future, in order to change its state in such a way, hopefully, that something exchangeable is produced. Product management means, making sure a satisfactory exchange occurs between the creator of a product and its new owner.
So many people get this wrong.
It is not a product if it's a project. It is only a product once it has been exchanged with another entity for their purposes.
You can have many, many projects which will never become products, because they won't be exchanged with others. You can have products which are valued by their owner in ways unintended by their creators. The value and utility is arbitrary to whether or not something is a product - the only requirement for something to become a product is that it is exchanged.
Successful product(S) are exchanged at scale. A single product can be very successful if the scale of that exchange is high. A lot of products can be very successful if the number of exchanges is great.
Until the exchange occurs, it's not a product. It's a resource. Inventory.
Side projects become products only once they are exchanged.
There really are plenty of Google analogs. There are plenty of chatbot analogs. Any one of us can recreate Instagram or X. These competitive analogs simply have not become products, because they have not been exchanged. Products which harness human collectivity have the problem of not being exchanged at scale until the collective decides to participate in the exchange, i.e. recommend their friends sign up to join them.
The problem with easily started new side projects is that they are not so easily exchanged at sufficient scale.
Not sure I understand the need for the exchange at scale. If I build a tool that lets a single person automate a tedious calculation then as long as they can depend on me maintaining it then it’s a product as far as I’m concerned.
Yes, I guess I wasn't clear: it's a product if it is exchanged - at all. At any scale. (There was a missing 'any' in my original statement.)
You can sell a single product for an enormous price, you can sell 1,000 products at a low price - the only thing that matters is that the two parties agree to conduct the exchange at any scale and, most importantly, that it actually occurs.
Common to both high-end scale and low-end scale scenarios, is that the exchange occurred and all parties agree to it. That's the only thing that makes something a product - the exchange.
Not sure how that’s helpful in the context of the question the article poses: What is the difference between a vibe coded thing and a “real” product?
Not sure how you're missing it. He's making a distinction between the concept of a Project and a Product. I agree with the distinction and he seems to be saying that the author has the wrong concept of what a product is but to answer your parent comment is saying that there's no difference between a vibe coded thing and a 'real' product so long as there has been some satisfactory transfer of agency and an exchange between user and product creator at any scale. So he's essentially saying that the author may be conflating vibe coded PROJECT (with a vibe coded PRODUCT) and that if so comparing a vibe coded PROJECT with any 'real' (whatever that means) product is an unfair comparison and on the flip side if they're comparing vive coded PRODUCT with a real PRODUCT then they're one and the same thing from the perspective that there was an transfer of agency and utility has been exchanged between user and product creator. I happen to agree with parent comment. It's an airtight argument that it doesn't matter how yu made it. The distinction between vibe coded and 'real' product is fuzzy at best. The real distinction lies between a PROJECT and a PRODUCT.
It doesn’t matter one bit how you made it, as long as you’ve got someone who is willing to exchange with you, for it. That is the only factor in determining whether something is a product or not.
Nobody wants to know how the sausage is made. Vibe coding is just sausage-making.
My office has cut down SaaS costs by a couple of tens of grand a year, simply by making our own versions using LLMs.
It is not that we didn't have the expertise to do so to begin with, but it would simply have been too expensive and time consuming. That was solved once the models became good enough.
There's a lot of money in the SaaS world, where the products are both unglamorous and one-trick pony-ish. Making your product LLM-proof can be challenging today, unless you happen to own a lot of data or lots of compute, and those two are the drivers behind your product.
Do you mind sharing the SaaS you were able to replace? If you don’t want to share the name, category would be interesting as well.
The issue is most of these demo are created by developers. Most of the developers don't have interests or skills in product and design. So they use AI to write code, not build product.
Another mistake everyone making is not building better and bigger products. What is used to take a month to develop is now possible in few days but most don't put the same effort as before to make bigger and better products. They just do they same as what they used to do before but quickly. This is a mistake. AI uplifted everything so products built with AI should go to next level.
I'm an indie mac app developer. My first product took me 6 months to develop without much AI. I just released my second app ( https://www.vinaa.ai/ ) but took the same time to develop as I wanted it to be the best AI chat app. So I spent a month building my own markdown renderer in TextKit as existing library are not fast enough. I wouldn't done this if I don't use AI.
> developers don't have interests or skills in product and design
I've found the opposite to be trie very often.
That is actually a good thing. There is a term for this - https://blog.pragmaticengineer.com/the-product-minded-engine... Before that this is optional but now that coding is automated, this is becoming an essential skill.
Maybe what these llms open up is the ability to create personal tools to get xyz job done, rather than creating companies with polished products. Perhaps for the latter you'd still need some combination of team, timing, etc.
But the question of should I spin up my own website in a few minutes or use wordpress for my blog is now open. Your personal tools can compete with what's out there and you may decide what you build in one session is more compelling than what the "pros" are offering.
And for personal tools you are much more forgiving for the mistakes if it gets whatever task you want done.
I think a product should answer a specific need, it cannot be fully defined internally, it is an expression of some need in the environment which makes it a legitimate product. A product with no viability soon ceases to be a product. Generating code is not the same with answering a need, it is orthogonal. Good products have market fit, not necessarily are themselves well written apps.
The vibe-coded demos everyone's tired of are code with no environmental need pulling on them.
The problem is that getting your first user or first $1 is not particularly easier with even the best LLMs to help you. Distribution is brutal — Google doesn’t want to index new sites, Twitter doesn’t want to distribute lowbie posts, right here HN’s /new queue is mercurial ..
So building is faster, but marketing—not so much
What happened to HN's new queue? What changed? I only watch homepage so I wouldn't know.
Also, dang ought to make a new tab "Trends" (or just name that "AI") and move all AI/LLM/etc posts there. We might possibly see something other than AI then.
> So building is faster, but marketing—not so much
Producers are AI/agents now but consumers are still human beings. Maybe it will be different when it will be: by the AI, for the AI, of the AI… etc and humans will be safely out of the consumption loop.
It's just stuffed full of AI slop products, same as before AI but now with AI.
I think there are people you can pay to ensure your post gets to the front page.
You are not indicating that's dang, are you? I'd never believe that :D
No of course not. Just residential proxy botnet groups with Telegram addresses.
I don't disagree but for some of the examples given (YouTube, Instagram, X.com) a huge entry barrier is the network effect. Even if AI could perfectly clone these products in a day, that still doesn't translate to instant market share.
And the resource you need to host so much data
If the things created with AI lack originality, they are nothing more than clones, rather than prototypes. While I agree with the majority of the text, I really don't understand why the amateurish efforts of so many are taken so seriously, to the point where people actually obsess over them. The marketing of these outputs by individuals or organizations with no prior connection to the industry (especially on platforms like YouTube, Reddit, HackerNews, etc.) is driven solely by self-interest. These ideas only excite the laypeople and the naive. For a professional or anyone who actually knows how things work, these are—as the name implies—just tools for now, not the be-all and end-all.
In real terms a product is the delivery of a service or other item of value. Specifically within the realm of software it is the promise of the delivery of software that will do what it says it will do, and then maintain or fix it where it falls short.
E.g. it's now about the delivery of a service rather than the challenge of building it (e.g. the moat) and then the delivery of service of it afterwards. Non functional requirements like data management and security, legal requirements and hosting are still valuable things that aren't front of mind for most developers creating their own tooling.
But is the definition of the product really just something that has loads of users. If so than the best "product engineers" are just people with gigantic following since every url they share would get traction.
Imo a better distinguisher of demos and products is: "is your thing CAPABLE of solving a real problem" (even if it isn't doing so at a scale atm). Google+ was a product (not a super successfull one), eventhough it didn't have many users. Conversely, a viral interactive gimmick can attract millions of users in a day without really being a product at all.
A product is just a software output packaged for sale. Most products these days are actually services, where delivery of the application is as important as its development. One man’s prototype is another man’s MVP. You can’t No True Scotsman your way into discounting the fact that low quality software can still make money.
A miserable pile of requirements!
Since everyone has access to the same tools, what exactly has changed about building a new business? Are people really expecting brand new companies to just displace the existing ones? What separates one company from another looks the same as always to me risk tolerance, etc. Now with the added benefit of a lot more competitors, plenty of who can't actually execute, all making noise in the market.
For a second I thought this was going to be about abstract-algebra/category-theory
A product is something you can pitch to an investor for money. All else is irrelevant.
Why hasn't someone upended LinkedIn? It is not because the product is incomplete. It is because LinkedIn is the incumbent with millions of users and an ecosystem and culture and gravity around it.
The most successful products are Cartesian.
If you build it they will come is a lie from a movie. But alas, AI didn't change that
A real product must have its own to problem solve. Real users are evident for it
Whilst I agree with the sentiment, there is some irony that the blog itself looks to be vibe-coded too.
i am curious. what makes you think this blog looks "vibe-coded"?
Does a product include the ability to acquire and retain customers?
> If nobody is using the thing you built, you don't have a product, you have a toy
Hard disagree. I think the articles goes in a good direction when it comes to the question but this ending is short of a satisfying answer
This article is riddled with logical fallacies. And this is a very Silicon Valley-esque, growth-minded, narrow way of thinking about this new world we live in.
I maintain half a dozen products, some of which enjoy only a handful of dedicated users, and I consider them all a resounding success. We are living in a new future of readily available custom software for extremely niche use cases.
> Don't feel bad if you don't have anything to show up with all the free intelligence available nowadays. Almost nobody has.
But I can empathize with the author's attempt at "vibe writing" something meaningful, considering that they seemingly don't have anything better to "show up with".
What is a product? So you take two natural numbers `a` and `b`, and you want to sum `a` for `b` times, or vice versa. Then things become complicated if you want to do that quickly...
I think it ultimately just comes down to laziness. People are increasingly loathe to make multi-year plans and stick to them, for various reasons.
Building something like a YouTube competitor is theoretically doable by a small team. It’s vastly more possible with AI tools than it was a decade ago.
But the “muscle” of doing difficult things has atrophied for many people, in large part because the AI tools themselves reduce your ability to actually do the work. If day after day, you just prompt an AI to make things for you, do research for you, etc. then you gradually stop working that muscle yourself.
It makes me think that the ideal usage of AI tools might be a deliberately limited one: do everything on your own, but check in with the AI once a week for review.
A product is something consumable.
In term of business, the era of "MVPs" have long sailed already, probably 95% of every projects released now is done so lazily that you can know in the first 5 seconds that the company will die in the coming months.
product is operation of the ring that is on the outside of the brackets in distributive property
"A miserable little pile of secrets."
Productkind ill needs a savior such as you.
it pretty nice
But enough slop have at you!