Thanks for your continued work on Extensions! I’ve enjoyed the challenge of the development process of my own Extension thus far. Here are some questions and concerns I have in response to this RFC:
1) Could you explain the UX reasoning for collapsing the chat versus any alternatives you may have explored?
I’m concerned for the potential need to scroll the embedded extension (provided it’s tall enough).
Vertical space can be freed up if the Stream Chat was itself positioned alongside the same menu where the Extensions are listed. Also, the input field for Chat would only appear when the Stream Chat is the selected item. Here’s a mockup of this alternative design:
This approach has advantages over the design included in your post:
- Users of Mobile Extensions have one less click/tap to navigate to an Extension.
- Extensions are discoverable by default.
- Extensions are made hierarchically equivalent to Stream Chat by being positioned in the same navigation menu (possibly leading to higher engagement as a result).
- Embedded Extensions have more vertical space to utilize.
- Fewer visual elements are needed for this design, which is already plenty dense.