2 ms·

Personally, It Feels like this will change the whole ai assistant industry the way chatgpt and claude. But again it requires multiple examples the way vercel di

Personally, It Feels like this will change the whole ai assistant industry the way chatgpt and claude. But again it requires multiple examples the way vercel did it for themselves at vercel.com/templates. Even perplexity, scira work with beautiful ui generation for visualizing data to the user but they have to do it manually as far as i know. I'm currently building coldran.com to compete with customer chatbots but with better experience and how customers can interact with teams to get better experience and features as fast as possible. But I'm genuinely curious why would anyone use this instead of building their own unique ui because of branding reasons other than that this seems cool. Internal Dashboard Chatbots can allow people to interact with some api endpoints which other components use within the website with a prompt and then the ui appears ~ that would be cool like creation of projects or changing the git connection from one repo to another without changing the pages. but this has a market but people are clueless about the usage ps: i haven't used tambo at the moment but this is very cool

grouchy 1y ago
Hi, thanks for the feedback. Good luck with Coldran. To answer this question: > why would anyone use this instead of building their own unique ui 0. Under our component library is tambo-ai/react, which are just React hooks, so you could build your UI from scratch (we had a user do this over a weekend). They apologized, "sorry I didn't use your ui components". 1. Most of our components are just for managing sending messages, showing chat state, etc. The rendered or intearcted with components are up to the developer and often pulled from their existing app (chart, forms, tables, etc.) and styling is up to them. 2. All of those provided UI components are the “copy and paste” model (like shadcn). You can easily update their styles to match your UI or customize them by simply changing the tambo.css file we add to your project. > Internal Dashboard Chatbots can allow people to interact with some api endpoints which other components use within the website with a prompt and then the ui appears ~ that would be cool like creation of projects or changing the git connection from one repo to another without changing the pages. We have this experience inside our dashboard https://tambo.co/dashboard https://tambo.co/dashboard you should try it!
- nermalcat69 1y ago
  Thanks grouchy will look forward to using tambo for my stuff :)

grouchy 1y ago

Hi, thanks for the feedback. Good luck with Coldran. To answer this question: > why would anyone use this instead of building their own unique ui 0. Under our component library is tambo-ai/react, which are just React hooks, so you could build your UI from scratch (we had a user do this over a weekend). They apologized, "sorry I didn't use your ui components". 1. Most of our components are just for managing sending messages, showing chat state, etc. The rendered or intearcted with components are up to the developer and often pulled from their existing app (chart, forms, tables, etc.) and styling is up to them. 2. All of those provided UI components are the “copy and paste” model (like shadcn). You can easily update their styles to match your UI or customize them by simply changing the tambo.css file we add to your project. > Internal Dashboard Chatbots can allow people to interact with some api endpoints which other components use within the website with a prompt and then the ui appears ~ that would be cool like creation of projects or changing the git connection from one repo to another without changing the pages. We have this experience inside our dashboard https://tambo.co/dashboard https://tambo.co/dashboard you should try it!

nermalcat69 1y ago
Thanks grouchy will look forward to using tambo for my stuff :)