I'm going through the video and it is definitely a wonderful implementation. Thank you so much for this.
I'll want to ask however, why shouldn't frameworks like streamlit be considered when building applications like this? If at all it can also be considered when building something of such, what are the necessary things to consider or look out for?
Sure, you could be using Streamlit, Chainlit, Gradio, etc. In fact, some of my previous projects are using these. But when you want to build some advanced UIs, I think it's better to rely on frameworks like React. In this video, we just wanted to show you how to do that, but of course, you could replace our UI with streamlit :)
Streamlit is good for prototyping; this project is more complex.
Here, we needed multiple UI components that work independently from each other, API calls, multimedia file handling, and most importantly, a chat interface that we can customize.
Streamlit is limited and abstracts a lot with calls such as st.Button, st.Title etc.
For building simple dashboards, to view charts, metrics, tables, or have input forms, Streamlit is good enough. For more complex use cases, consider using a frontend framework and having the UI separate from your API.
The approach we've followed here is to reflect real production projects. You'll have a Server (API), a Frontend UI, and other services deployed independently.
I'm going through the video and it is definitely a wonderful implementation. Thank you so much for this.
I'll want to ask however, why shouldn't frameworks like streamlit be considered when building applications like this? If at all it can also be considered when building something of such, what are the necessary things to consider or look out for?
I really anticipate you response.
Sure, you could be using Streamlit, Chainlit, Gradio, etc. In fact, some of my previous projects are using these. But when you want to build some advanced UIs, I think it's better to rely on frameworks like React. In this video, we just wanted to show you how to do that, but of course, you could replace our UI with streamlit :)
Oh! Thank you, sir
Hey, thanks for your question.
Streamlit is good for prototyping; this project is more complex.
Here, we needed multiple UI components that work independently from each other, API calls, multimedia file handling, and most importantly, a chat interface that we can customize.
Streamlit is limited and abstracts a lot with calls such as st.Button, st.Title etc.
For building simple dashboards, to view charts, metrics, tables, or have input forms, Streamlit is good enough. For more complex use cases, consider using a frontend framework and having the UI separate from your API.
The approach we've followed here is to reflect real production projects. You'll have a Server (API), a Frontend UI, and other services deployed independently.
This is wonderful. I just love the implementation and will definitely try it out.