There's certainly a market. Heck, the chatbot market share likely reflects how good this memory is. Grok and Gemini are good products, but not known for retaining memory, and despite having the distribution, they lose out to ChatGPT.
I do think it's actually a Hard problem, otherwise everyone would have done it. ChatGPT is the king at it, but they're not selling memory as a product, so I assume it's tightly coupled with the chat. Claude can't do it without token guzzling.
And the first thing I set up with AI chatbots is memory. You need memory to work with past conversations, and suddenly you're dealing with emergent behavior and token drain.
The other question is timing.
It's probably a year late. You could easily make a billion dollar company just from this, but just as easily be disrupted by Big AI.
There will probably be a time when this would be unbundled, similar to how telcos and cloud unbundle all kinds of offerings. And that opportunity will come several years later.
It depends on how you productize it. There’s market. The memory itself is a must-have, but you should probably implement it with some advantages and make it domain-specific to be better at something like retrieving, indexing, etc.
I agree that domain-specific memory layers might be the way to go, in which case devs are just better off making their own memory layer for their use case, instead of having a dependency on a third party, don't you think?
Especially now that building a simple memory layer particular to your use case won't take a lot of time and effort. And you can keep making it better as you go forward.
There's certainly a market. Heck, the chatbot market share likely reflects how good this memory is. Grok and Gemini are good products, but not known for retaining memory, and despite having the distribution, they lose out to ChatGPT.
I do think it's actually a Hard problem, otherwise everyone would have done it. ChatGPT is the king at it, but they're not selling memory as a product, so I assume it's tightly coupled with the chat. Claude can't do it without token guzzling.
And the first thing I set up with AI chatbots is memory. You need memory to work with past conversations, and suddenly you're dealing with emergent behavior and token drain.
The other question is timing.
It's probably a year late. You could easily make a billion dollar company just from this, but just as easily be disrupted by Big AI.
There will probably be a time when this would be unbundled, similar to how telcos and cloud unbundle all kinds of offerings. And that opportunity will come several years later.
It depends on how you productize it. There’s market. The memory itself is a must-have, but you should probably implement it with some advantages and make it domain-specific to be better at something like retrieving, indexing, etc.
I agree that domain-specific memory layers might be the way to go, in which case devs are just better off making their own memory layer for their use case, instead of having a dependency on a third party, don't you think?
Especially now that building a simple memory layer particular to your use case won't take a lot of time and effort. And you can keep making it better as you go forward.
[flagged]
[flagged]