This task is a spike for Editing Design to develop an opinion about what they think is the optimal way in which to develop and deploy the talk page improvements we have planned for mobile web (see ===Mobile improvements below) and in the process, converge on a single mobile web talk page view.
Mobile improvements
| Intervention | Ticket |
|---|---|
| Introduce the Reply Tool | T270536 |
| Introduce the New Discussion Tool | T270537 |
| Introduce topic subscriptions | |
| Introduce topic containers | T269950 |
| Converge on a single mobile talk page view | T280417 |
| Introduce a new talk page frame | T269963 |
Principles
At any given point in time throughout the process of introducing the features above and converging on a single mobile web talk page view, the following must be true:
- Junior Contributors must be able to:
- Intuitively know how, and feel confident, responding in an existing conversation
- Intuitively know how, and feel confident, starting a new conversation topic
- Senior Contributors must not experience degradations in their ability to
- Start new conversation topics
- Respond to comments in existing conversations
Approaches
This section will contain, what Editing Design sees as, the feasible approaches for implementing the ===Mobile improvements above while upholding the ===Principles above. Each "approach" should have a set of tradeoffs associated with them.
Approach #1
- Core functionality
- This release packages a few features that are central to the Talk Page experience such as replying and starting a new discussion while building on top of a single mobile talk view
- Considerations
This will require us to choose one of the mobile patterns (Wiki page view), get rid of the overlay, and then design mobile-friendly interface components for replying and subscribing. After we get this out and test it we could build on the design incrementally with the other elements in sync with the updates for desktop. A reason to do this approach would be to design something that is less disruptive to Senior Mobile Web Contributors because we would be offering subtle and incremental changes rather than a complete refresh.
Approach #2
- Do it all!
- Since we are not starting from scratch, we could take a design pass at everything that has already been designed on for desktop view.
- Considerations It might take longer than Approach #1 in terms of getting that first release out but when we do, we'd be done. As mentioned above, this could potentially be more disruptive to the Senior Mobile Web Contributors, however, I believe the number of editors affected here is significantly less than Desktop Web.
Done
- The ===Approaches section is completed