Wikimedia Apps/Team/Android/Communication/fr

Historique
En février 2021, l'équipe Android a sorti la première version des pages de discussion dans l'application mobile. Cela représentait la phase initiale de ce qui allait devenir une partie d'un long projet annuel visant à améliorer la communication dans l'application Android. L'Epic (tout le plan) du travail originel est consultable sous T252556. Vous y trouverez la feuille de route complète de Android.

La page du projet sera mise à jour au fur et à mesure que nous prenons connaissances des limites de la communication depuis Android et que nous nous assurons que nous suivons les conventions communautaires tout en trouvant une bonne expérience de communication sur mobile.

Les fonctionnalités actuelles de communication sur Android incluent les pages de discussions des articles et des utilisateurs, la liste de suivi et les notifications Echo. Bien que ces fonctionnalités soient disponibles, nous savons qu’elles peuvent être améliorées et nous prévoyons de les améliorer durant la phase Communication de notre feuille de route.

Notifications
During this phase of our work, we will ensure that Notifications are easily discoverable and that the notification home center is comprehensive.

Completed


 * In-article notifications Link
 * System level preferences
 * Bell icon and red dot indicator
 * Surfacing IP notifications
 * Refreshed notification home center with search and filter

Messaging interface
Once we have confirmed that users are adequately aware of any notifications they have received from other editors or the system, we will focus on ensuring users can easily start or reply to discussions in the app. It is important that the interface and workflows are comprehensive and easy to navigate for their given contexts and goals.

Proposed Features


 * @ mentions
 * More discoverable talk page entry points
 * Reading focus mode
 * Customizable quick actions
 * Visual distinction between article talk pages and user talk pages
 * An ability to delete conversations
 * Support for accessing project talk pages
 * An ability to sort and search talk pages
 * Improved performance
 * Read and search archived conversations
 * Topic subscriptions
 * Native edit history

Onboarding and guidance
The team will evaluate tooltips, system level notifications and onboarding to ensure the experience is helpful and properly timed.

Connecting communities and interests
This phase of our work is more experimental with the aim of connecting users based on shared interests, responsibly lowering barriers for meaningful collaboration, third party integration and platform parity that doesn't detract from a mobile first experience.

Proposed Features


 * Portal support
 * Campaign support
 * Mass mentions
 * Mute notifications from identified users
 * Community dashboard with the mentorship module attributes
 * Third-party support

Comment suivre le sujet
Nous avons créé notre Epic Phabricator T273253 pour suivre les premières améliorations concernant les pages de discussion dans l'application Android avant de faire notre évaluation globale. Toute remarque est la bienvenue car nous mettons au point la première version et nous allons faire une investigation en profondeur sur la communication via les équipements Android en avril - juin 2021 pour pouvoir implémenter les améliorations l'année prochaine.

February 2022 – @Mentions, Native Revision history, Article and User Talk Page mockups, Customizable Toolbar and Reading Focus Mode Release
During our February releases we made minor improvements to Talk pages to enhance functionality. The improvements includes a drop down menu when users click a user name that lets them choose if they want to go to a talk page or user page. We understand that some users may want to see who they are communicating with before sending a talk page message, whereas other users would like to go directly to a talk page; we hope that this release allows that flexibility. Users are now able to edit talk pages as Wikitext now, which is important for users that may post an error or typo in their talk page message and want to delete or modify it. We also added a pattern to replies that pre-populates the user you are replying to on talk pages when hitting reply. Users are also able to use the @ symbol to mention another user instead of having to use brackets and write out ping. Additionally, when pressing @ and starting to type a name, the app provides a drop down menu of user names. We hope this change will make mentioning other users easier for Android users and also serves to ensure the person they are replying to receives a notification (T297912).

Last year the team released Watchlist, which introduced native diff views to the Android app. To build on this feature our designer created mockups for native revision history, something requested in the community wishlist. The engineers have started developing revision history. While we have started developing the feature we welcome feedback from the community regarding the latest designs of native edit history on our talk page or on Phabricator. We are especially interested to know if it would be helpful to allow filtering by tags, and how prominent the undo button should be. Please keep in mind undo is not the same as rollback, which means all users will see the undo button. We are also considering adding a rollback button for users that have those permissions.

In December 2021 we shared the mockups of Reading Focus Mode and the Customizable Toolbar. The team released both features in February and conducted user testing. The detailed results of the test can be found on Phabricator. The most notable results were:
 * Users understood how to turn reading mode off and on if they desired to make an edit
 * It was difficult to discover reading mode and the customizable toolbar with it being nested in Theme
 * Users had difficulty finding theme once they moved it out of the toolbar
 * It wasn't obvious to use the side icons to rearrange the toolbar

For that reason, the team will rethink our onboarding to these features through the next phase of our work, which is onboarding and guidance. Additionally we will add a more link in the toolbar, which is where users can access the customizable toolbar feature. We would also appreciate feedback on if we should use checkboxes to allow users to select what links are in their toolbar to address the difficulty people had with dragging an icon.

This month we took the feedback and learnings from previous months about how we should improve talk pages in the app and developed the following mockups: One of the changes you will notice is that user talk pages and article talk pages are visually different. On the user talk page we display some of the most recent message at the subject view level and conversely for the article view we show the subjects and not any of the metadata from the message. The intention behind this difference is to make the user talk page feel more conversational and visually indicate the article topics are meant to discuss article edits. To further connect the article talk page topics to the article, we will display an image from the article in the header of article talk pages. User talk pages will show the name of the most recent person that has posted to indicate that the space is conversational amongst users and not necessarily article specific. Previously there wasn't a visual distinction for template messages that often share helpful context and policy for article talk pages, in our proposed designs we drew inspiration from Desktop by distinguishing the top most template message from other talk page topics. In both article and user talk pages, users will be able to view archived messages in the app and subscribe to threads in order to receive notifications when someone has posted an updated to a talk page thread of interest.

We also changed the way users reply and read threads. Replies to a thread were at the same level and indicated with a reply icon. In our new designs, users can expand and collapse replies and we will now support inline replies. Additionally, whereas in the past users replied using a floating action button, with the addition of inline replies, reply actions will be under each post. This month we also fixed a number of bugs which included improving audio and media file support. There were also bugs fixed related to the article layout on this day and ensuring the article doesn't close out when returning from webview. The confusion between Chinese language variant codes has been fixed in T298448. Long references on small screens are now fully viewable T298269.

Closing out our work on notifications, there was a back end issue where notifications weren't being properly associated with the right place in a talk page. As of February, talk page notifications take you to the right place in the discussion T296018.

January 2022 – Talk Page Discoverability exploration, Exposing Project Talk Pages and Accessibility Report
In January we continued our work on enhancing talk pages by exploring pathways to make accessing talk pages more discoverable without it being intrusive. Our explorations for discoverability took into consideration the feedback we received in November and December from new and experienced users. Now that the Android app has Reading mode, a feature where users can hide editing features, when reading mode is off, users will see a talk page bubble that shows the number of active discussions for an article. Once a user clicks the talk bubble they will view a preview in a side panel of the active discussion topics. Users will be able to expand the side panel or click a topic to see the full view of the article talk page. The work can be tracked at T298814and T299033.

As described in T295071, when a user clicked on a username that doesn't have a profile page an error message popped up reading "This page does not exist" with the option to dismiss, which wasn't helpful and was a different experience than Desktop. The team updated the error message to provide more context and it is now more aligned with Desktop experiences.

The team made various tweaks to the app to improve accessibility, which was written about in detail by one of the Android app developers, Cooltey Feng. One of the outstanding items to address as a result of the report is if our experience for users with screenreaders should be improved or standard. The team is looking to consult screenreader users to conduct an evaluation of the app experience and provide feedback. Please comment on our talk page or email android-support@wikimedia.org if you can provide feedback on the app experience while using a screenreader.

Previously when users navigated to project pages in the app, talk page links were broken. As of our January release project talk pages can be properly accessed in the app.

December 2021 – Talk page survey results (experienced users), IP notifications and reading focus mode
As a follow-up to the survey from new users the team investigated ways to improve. One investigation included investigating the possibility of not using the RestBase endpoint for retrieving talk pages and instead using the regular MediaWiki API to get better talk page performance. As detailed in T295687, our team is unable to do so at this time because it requires an improvement of the performance of change propagation and/or cache updates of the REST endpoint. We have put in a request for backend teams to pick this up with the hopes of faster talk page performance in the future.

The team discovered that talk page notifications do not always lead users to the right subject line, rather it takes them to the general talk page. This bug was caused by changes to the DiscussionTools project. The team has been collaborating with the Editing team to fix this bug and the work is documented in T296018. As of December 15, 2021, unregistered editors in the Android app will receive talk page notifications T291481, which is important for reaching anonymous editors.

Users are now able to filter notifications by Wiki and notification type in the home center T294035, while also accessing settings to update preferred language settings in the filter view.



To help collaboration, users can now see their notifications even while offline T287955.

In October the team launched a survey to learn about the desires of experienced users for their talk pages experience in the Android app. We specifically surfaced the survey in the app to English Wikipedia talk page users in Nigeria and India, Arabic and French Wikipedia talk page users in DR Congo, Mali, Morocco and Egypt, as well as Japanese Wikipedia editors and Hindi Wikipedia Editors and received responses from 54 participants. The full results can be found at the bottom of the protocol page. The key takeaways from this survey was that users believe talk pages need better onboarding and education on how to use them and the distinction between article and user talk pages. There were requests for comprehensive communication flows when edit changes occur, and easier ways for users to seek assistance. Users requested an ability to share talk pages, which has been implemented in T295808. The lack of talk page discoverability in the article view was further highlighted in this survey. Respondents to the survey expressed the importance of encouraging users to review an article talk page when making an edit. It was highlighted that users involved in a talk page message should be pinged when someone has replied to them, which doesn't currently happen unless the user replying puts in the ping command for the user they would like to reach. Further, positive reinforcement and support for deleting and archiving messages that are no longer relevant were also surfaced as desired features.

What was very evident in our research was the flexibility needed so that our users unique needs are met when they are reading an article and prefer not to see editing tools compared to when they may want to edit and have a desire for specific editing tools or talk pages. With the requests for flexibility in mind, the team will release and test a customizable toolbar, which will allow users to choose which quick actions appear in the bottom bar in article view versus which things should go to the overflow menu and reading focus mode, a feature that hides the bottom quick actions toolbar on scroll as well as the edit pencils and call to actions. Reading mode will be off by default but accessible via Themes. The team will ensure users are able to recall how to turn read mode off so that we don't impede anyone's ability to edit.

November 2021 – Talk page survey results (new users), EditNotices and release of notifications home center
Building on the work we did to notifications last month, our team improved the notifications home center by adding [phab:T288068|search and filter]] functionality. We also improved the readability of the home center and added a new tabs called mentions, which includes all notifications that are generated by an action from other users, the categorization follows the policy that defines mention notification types. The team ran T2933447a usability test of our existing talk page experience on usertesting.com with new users to understand how discoverable talk pages are and if users understand how to differentiate between user and article talk pages. Additionally, we wanted to know what elements work well even in low context. Finally, we hoped to identify possible opportunities for improvements that we could surface to experienced users in the survey we ran in app. Our test users edited on Arabic, French, Hindi, Indonesian and Japanese Wikipedia.

From the test we learned the following things worked:


 * Users understood how to create new topics and reply to threads
 * Participants mostly understood that the article messages were from other users.
 * Participants described what a revert is, in their own words, well
 * Link in the footer: Some participants accessed talk pages via the link in the footer intuitively
 * Discovery of notifications: the work on the new placement for notifications paid off, people had no issues discovering the bell icon

From the test we learned the following things do not work well in our existing experience:


 * Users had a difficult time finding the link to article talk pages in the overflow menu, some participants tapped the edit pencil to access talk pages
 * There was a slow performance when attempting to submit on when using talk pages on Japanese Wikipedia
 * Users didn't understand the distinction between how to use article talk pages and user talk pages
 * There was a disorientation when tapping items within notifications home and navigating to Commons talk pages
 * Lack of understanding for the diff view and of edit summaries
 * At times there were no active keyboard and the reply button was missing

Based on the results of the test, the team generated investigative tasks, which can be found linked to this epic on Phabricator.

We fixed some bugs which includes presenting edit notices and fixing a bug where users lost their open tabs.

October 2021 – Outcomes of the ABC test, more updates to notifications and the launch of talk pages work
Last month we conducted research to understand how to improve the notifications experience for our users. Our goal was to ensure people are accurately receiving important messages from other users and the system, and able to understand and engage with the messages they receive. In last month's update we shared the outcomes of our qualitative research. We now have the outcomes of our ABC test where we evaluated which iconography and placement of said iconography in the app would best improve discoverability of notifications.

By changing the placement of the notifications iconography from the overflow more menu to the top navigation bar we saw an increase in interactions by 121.4%. The activity data was isolated by a seven day average of daily unique users. We further evaluated the impact on our target user groups to ensure our decision making is equitable. Based on this evaluation we saw an increase in interactions by 102.19% for users in Nigeria and India using English Wikipedia, 108.90% for users in Morocco, Egypt, DR Congo, and Mali on French and Arabic Wikipedia, 77.23% for Hindi Wikipedia users, 74.07% for Indonesian Wikipedia users, 147.83% for Japanese Wikipedia users. Based on this information, we made a final decision of ensuring the notifications icon lived in the top bar.

Our next test evaluated if our existing more icon, bell icon or the inbox icon would yield more clicks. Our data indicated the inbox had the highest level of clicks overall and across user groups, the bell icon was the next most favorable icon, followed by more. However, within our target user groups, Indonesian Wikipedia editors and Hindi Wikipedia editors, marginally clicked the more icon over the bell icon. Although the inbox was most favorable, when compared to our qualitative feedback, we learned that users expected to enter an actual inbox when clicking an inbox, and the bell icon was more closely associated with notifications. Additionally, across other platforms, the bell icon is being used to indicate notifications, so for the sake of parity and to not confuse users, our team chose the bell icon.

The next phase of our communication work is to improve the talk page experience in the Android app. While we currently have talk pages, it is important that the experience graduates from functional for experienced users to easy to use by all users, especially those that may need to use them the most. In order to better learn what gaps exist, we are launching two surveys. One survey will be conducted on usertsting.com with new users, so that we may learn what gaps exist for users that may be new to the Android app. You can find that protocol on Phabricator. The other will be for more experienced users that have visited and used talk pages in the Android app before. You may view the survey for experienced users at Wikimedia Apps/Team/Android/Communication/UsertestingOctober2021 and answer questions on talk page.

We also made minor upgrades which included improving how we handle the topmost welcome message on user talk pages, which can be reviewed on Phabricator.

September 2021 - In-app notifications and survey results
The outcomes of the qualitative survey collecting feedback about Notifications can be found on the protocol page.

Through our qualitative research we learned:


 * The top right positioning of the notification icon was most popular
 * The bell icon was most closely associated with notifications. While the inbox tray was a popular choice, it was associated with messages and notifications span beyond human-to-human contact
 * Users were in favor of having a mention tab in the Notifications Home Center
 * Users generally found filtering capabilities within the notifications home center important
 * There was a request for more context for reverts

To compliment the qualitative feedback we've received, the team launched an ABC test to get the final quantitative confirmation of how the discoverability of notifications changes if a bell icon is used in the top right hand corner when compared to the more and inbox tray. The initial details are available in Phabricator via ticket T290995.

As requested by the community and based on the survey feedback the team made notifications more discoverable in the article view.

The final iconography will be decided in October after our ABC test.

In addition, the team released the following minor updates:


 * An ability to to delete individual items in recent searches T276770
 * Enable users to undo a talk page message a few seconds after posting and return to edit mode to make changes T287594
 * Expose the last time a talk page has been edited so that users can easily review the edit history T274836 and T287593

August 2021 - Minor bug fixes
In August, the engineers focused primarily on tech debt and bug fixes raised by users as the rest of the team processed feedback from the community to turn them into features.

26 July 2021 - User testing notifications placement and workflows
The team is requesting feedback about potential changes to notification placement in the Android app and the subsequent workflows. Please visit the user testing protocol on MediaWiki and share your feedback on the talk page.

12 juillet 2021 - Amélioration de la découverte des pages de discussion
Aujourd'hui toutes les notifications et les alertes sont supportées dans l'application Android.

Mais une fois dans l'application, il n'est pas facile de savoir où se trouvent les notifications; FY 2021-2022 nous cherchons à améliorer cette expérience.

Notre mise à jour de juillet - septembre 2021 va améliorer la découverte des notifications dans l'application et étendre les notifications dans l'écran de verrouillage. En décembre 2021, nous allons étendre le centre d'accueil des notifications pour réaliser une interface et une boîte intuitive. Nous allons concevoir et construire de manière cohérente avec les éléments du système Android en tête, de sorte à nous assurer que la fonctionnalité sera à l'aise chez elle sur cette plateforme.

De juillet 2021 à décembre 2021 nous nous focaliserons sur les utilisateurs connectés qui auront fait au moins une modification, nous realiserons néanmoins notre travail préliminaire quelques mois auparavent pour le porter à la connaissance au début de 2022 aux utilisateurs non connectés. Nous envisageons d'explorer les expériences embarquées sur les outils de communication pour les utilisateurs qui ne sont pas connectés. Cela se fera en plus des autres renforcements positifs et des flux de travaux pour les utilisateurs connectés.

10 mai 2021 - Mises à jour des messages de gestion des erreurs
L'équipe va faire quelques mises à jour sur la manière dont les messages d'erreur sont gérés dans l'application, qui seront diffusées en production dans les semaines à venir. Les modifications exactes que nous faisons peuvent être suivies sur les tâches T170726, T276142, et T276139.

Nous reconnaissons qu’il y a plusieurs améliorations à faire, mais nous avons reçu des retours sur ces changements nous indiquant qu’ils sont suffisants pour être publiés, pendant que nous continuons à améliorer la gestion des messages d’erreur et des systèmes de communication dans l’appli Android.

30 mars 2021 - Mises à jour des pages de discussion en langue native et des listes de suivi
L'équipe a collaboré sur les fonctions de relecture des pages de discussion et de la liste de suivi diffusées dernièrement pour évaluer les améliorations possibles. Les modifications suivantes ont été faites dans la version la plus récente :


 * s'assurer que le bouton Répondre ne cache pas la vue de la ligne du message Compose lors d'un rafraîchissement de la page
 * déplacer le positionnement du lien de la page de discussion de l'article, du bas d'un article vers le menu déroulant et ajouter l'accès à la liste de suivi au menu déroulant de l'article
 * mettre davantage en évidence « A propos de cet article » dans le sommaire
 * replier la ligne du sujet des pages de discussion

Les autres élements que nous avons l'intention de modifier comprennent :


 * s'assurer que les réponses en ligne s'affichent en ligne au lieu de se placer en bas de la section.
 * Dependency : API venant d'une équipe du noyau
 * refondre ou reconsidérer les indicateurs de points bleus pour afficher ce qui n'a pas été lu sur les pages de discussion
 * afficher la date de la dernière modification des pages de discussion
 * intégrer la prise en compte des listes de suivi et des pages de discussion

2 février 2021 - Diffusion de la liste de suivi et des pages de discussion
Nous sommes très excités de vous présenter notre dernière version de l'application Android Wikipedia, disponible actuellement sur Google Play Store (ou téléchargeable séparément pour les appareils sans Google). Voici les points forts de cette mise à jour :


 * Watchlists: Your watchlist is now accessible from the main screen when you are logged in. Tap the "More" menu at the bottom and select "Watchlist".  If you have multiple languages selected in the app, the watchlist screen will merge your watchlists from those language wikis. You can also choose which languages to show by tapping the language icon in the toolbar at the top.  Tap any of the items in your watchlist to see a detailed diff screen for the selected change.  And of course, to add any article you're currently reading to your watchlist, tap the top-right menu in the toolbar, and select "Add to watchlist".
 * Talk pages: Article talk pages and User talk pages are now presented natively.  When reading an article, the corresponding talk page is accessible by scrolling to the bottom and selecting "View talk page".  User talk pages can be accessed from various places where user interactions might happen, including your watchlist, various push notifications (e.g. messages left by other users on your talk page), and other users' and article talk pages.

In addition to these major updates, this release has plenty of bug fixes, design refinements, and performance optimizations. Check it out, and as always, we welcome your feedback! We are asking for watchlist feedback on Phab task T273254 and talk page feedback on T273253. You can also leave feedback on this talk page.

Special note: This release is dedicated to the memory of our late colleague and friend Bernd Sitzmann, a brilliant developer and a wonderful person, without whom the app wouldn't be what it is today. He will be missed.

Décembre 2018 - Notifications d'écho sous Android
In 2018, the Android team set out to add Echo Notifications to Android. By the end of the project the following notification types became available:


 * System- Messages from the system
 * Milestone-  Edit counts being reached
 * Thanks- Someone thanks you for an edit
 * Revert- One- of your contributions were reverted
 * Talk Page- Messages from talk pages
 * Login- your login activities
 * Mention- Someone mentions you in page

Additionally, the team implemented poll notifications, which allows the app to use data to check for new notifications in the background. As of April 2021, this feature isn’t turned on by default.

Limitations sur la poussée des notifications
Il existe quelques points bloquants connus pour pouvoir pousser les notifications en temps réel, qui ont limité l'approche de l'implémentation originelle. Comme conséquence de ces limitations il y a un décalage d'environ 10 minutes pour les notifications.