[mihaich]

This makes sense, thank you very much for the feedback!

Another demo idea I had is to have an input field where the user can enter a GitHub username, retrieve all the starred repositories, and enable semantic search on the titles and descriptions of those repositories.

The main idea is that users will typically enter their own usernames, and therefore, they are familiar with the repositories they have starred, which provides a better search experience when testing the component.

Let me know if something else would work better for you.

[solardev]

Not the OP, but personally I'd prefer a search on some realistic examples, like maybe the React docs (https://react.dev/learn) or Next docs (https://nextjs.org/docs) that I frequently struggle to search, especially for complex questions like "what kind of caching does Next.js do" or "what is the proper way to do an async clientside fetch".

--------

Some other feedback (just so I don't make a bunch of separate posts):

- Demo #2 404s

- It would be nice to have some way to highlight or summarize the relevant parts of search results, especially when they're "semantically" searched and each result is several dozen words. There's no easy way to skim the results, and it's not really clear to me (as a user) why the rankings are the way they are. It just looks like a bunch of reordered paragraphs that I still have to read all of.

- 20 MB is a LOT to ask a client to download just to run a search bar. Is there any way to run this as a serverside function / serverless?

[mihaich]

Thanks for the feedback! I'll find time to make it better and retry the submission. Now I know it's actually possible to get on the first page :)

Regarding your last point: yes, 20MB is a lot, but the whole point of it is to have it all on client side, within a single component you install. You can already achieve the functionality you mention with the standard MUI's autocomplete. That being said, I'll look into ways to use smaller models.