For advice let me use my current product. https://fontofweb.com is essentially Pinterest for web design. It does semantic search against a database of UI screenshots and recordings.
The problem with products like this is that for search to be useful, you need, well... data. And when your data is crowdsourced, you need, well... a crowd. That was the chicken-and-egg situation I found myself in.
So the way I solved it was by painstakingly clipping and recording ~8500 websites myself.
But the great thing about that arduous process is that it forces you to put yourself in the shoes of your typical user. And really, the only way to make good products is to have a deep level of empathy for that user. In my case, that meant streamlining the data creation process itself, the act of pinning a screenshot or recording, because I had to do it over and over again. Making it easier for myself ended up making it better for everyone else too.
Of course, all that data-seeding effort goes to waste if search engines and potential users cannot discover it. So you have to go all in on SEO, especially sitemaps, and on programmatic socials where possible. This is especially true for a product like mine.
A lot of these marketplaces also have relatively homogenous data, which is actually useful, because it means you can present it through templates and publish pages at scale automatically.
Agents can search for design inspiration from production websites using semantic search. Since this inspiration comes from live websites, their design tokens; colors, typography usage, layout data are also available.
Hey! Thank you for your comment! You can actually use an MCP on this basis, but I haven't tested it yet. I'll look into it as soon as possible. Your feedback is valuable.
I daresay we're going to see a burgeoning situations where the software (code) is open-sourced under a permissive or copyleft license, while the associated data, content, or assets (e.g., datasets, models, or databases) are handled under separate, often more restrictive licenses.
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".
The problem with products like this is that for search to be useful, you need, well... data. And when your data is crowdsourced, you need, well... a crowd. That was the chicken-and-egg situation I found myself in.
So the way I solved it was by painstakingly clipping and recording ~8500 websites myself.
But the great thing about that arduous process is that it forces you to put yourself in the shoes of your typical user. And really, the only way to make good products is to have a deep level of empathy for that user. In my case, that meant streamlining the data creation process itself, the act of pinning a screenshot or recording, because I had to do it over and over again. Making it easier for myself ended up making it better for everyone else too.
Of course, all that data-seeding effort goes to waste if search engines and potential users cannot discover it. So you have to go all in on SEO, especially sitemaps, and on programmatic socials where possible. This is especially true for a product like mine.
A lot of these marketplaces also have relatively homogenous data, which is actually useful, because it means you can present it through templates and publish pages at scale automatically.
reply