shawn
shawn•2mo ago

AI chat app for the web (+ AR/VR)

Started building this for a hackathon about a month ago. Decided to keep going after the deadline. Still some work to be done, but its stable enough to release. Feel free to try it out yourself for free! https://www.qbe.sh/
No description
12 Replies
shawn
shawnOP•2mo ago
shawn
shawnOP•2mo ago
Built mostly using the agent component, feel free to check out the code if you're interested (fully open source): https://www.github.com/bentsignal/QBE
Draco
Draco•2mo ago
WHOA That looks awesome Is that built for the Apple Vision Pro? or Horizon OS?
shawn
shawnOP•2mo ago
Thanks! Its a WebXR app, so it should work well on both. That video is from the Quest 3. Unfortunately I don't have access to a vision pro, so can't confirm how well it will work on there.
Wayne
Wayne•2mo ago
Wow
Draco
Draco•2mo ago
Still, extremely awesome man, hope you win
shawn
shawnOP•2mo ago
Ayyy thanks! I haven't decided if I'm going to enter it into the resend hackathon yet. I do have another project idea I might enter tho!
Kevin07
Kevin07•2mo ago
Love this! Holding out for as long as I can to enter the VR world, but really would love to experience this 😄
shawn
shawnOP•2mo ago
Its a messy world right now. My app is so buggy on the quest its barely even usable. Don't think we're quite as close as zuck thinks, but someday!
Jumping Back
Jumping Back•2w ago
Shawn I am very curious as to why many people using agent components and still having schemas for message and thread and have other functions which agent comp provides
shawn
shawnOP•2w ago
They don’t let you modify the message or thread tables that come with the component, so if you want to store any data that isn’t supported by the component, you have to create your own table and handle it separately. I was curious about this at first as well (I believe @ian explained it to me originally). iirc, the reasoning for not allowing users to query, mutate, or edit the component tables directly is so that updates to the component don’t break your app. If you could query it directly and they decide to change something down the road, it could mess with your queries. The mutation case is a bit more obvious. I believe the general guideline is that if there isn’t a function to do something provided by the component, you probably want to store that data in your own table
Ruin9999
Ruin9999•3d ago
Damn! Nice layout!

Did you find this page helpful?