I don’t see the point in debating protocols when “the suckiness” always comes down to UI/UX
UX that works for async comms and real time comms can be “backed by” HTTP. One does not literally need the data model to conform to the presentation in mind.
“Email” view might be a good default. “Chat view” could be a toggle for when the group is online at the same time.
UX needs a rethink in general. What a designer finds trendy in the moment is user hostile. I want flexibility and customization at the presentation layer. Give me an API key and I’ll build my own UX in Docker containers, thanks.
UX that works for async comms and real time comms can be “backed by” HTTP. One does not literally need the data model to conform to the presentation in mind.
“Email” view might be a good default. “Chat view” could be a toggle for when the group is online at the same time.
UX needs a rethink in general. What a designer finds trendy in the moment is user hostile. I want flexibility and customization at the presentation layer. Give me an API key and I’ll build my own UX in Docker containers, thanks.