An headless approach to this Library

Feature Request

Will it be more effective if this WebChat SDK just export Hooks or Redux Dispatches to the logic and all UI Components be created and customized by the developer? Is really a pain to make this WebChat looks good, using CSS is weird because overwrites leads to break in new releases as discussed the classes and html markup changes a lot and the code and stylesheet looks so dirty, the JSS approach leads to limited styling.

I know how important accessibility is and all the efforts from the core members of this project is doing but I think an headless approach will be better, providing logic via hooks and the style leaves to the developer using this lib to build, even handling accessibility.

I love how powerfull is the use of custom components, but I think the standard chat isnt customizible enough, even the sendinputBox is really dificult and weird to style and to add custom features to it.

Keep the great work on this SDK, this is just an idea that I think will make this lib even more powerful.

The request proposes exposing hooks or Redux dispatches while leaving UI components, styling, and accessibility to the developer. Start by defining the headless API and scope for customizable components, then establish acceptance criteria covering styling, custom features, and accessibility before implementation.