Contributors/Mobile Web Editing Research/Wikimania 2025 Session

Session Abstract:

Despite mobile accounting for 60% of Wikipedia traffic, only 12% of successful edits come from mobile devices, creating significant barriers for contributors—especially those without access to desktop computers. The Product & Technology Advisory Council (PTAC) recently released a recommendation emphasizing the urgent need to improve mobile editing experiences to broaden participation and inclusivity within the Wikimedia movement. This interactive roundtable explored the challenges and opportunities of mobile editing, examining usability barriers, technical limitations, and the unique advantages of mobile contributions. Participants engaged in a collaborative discussion to share experiences, identify key pain points, and brainstorm solutions to make Wikipedia a truly mobile-friendly and accessible platform for all.

Wikimania Session Recap on Wikipedia’s Mobile Editing Experience: A Friction Point or a New Frontier?

Background

This document summarizes the 40 minute roundtable during Wikimania on mobile web editing. Participants were polled using the mentimeter platform and encouraged to share their thoughts aloud. The interactive roundtable explored the challenges and opportunities of mobile editing, examining usability barriers, technical limitations, and the unique advantages of mobile contributions. Participants engaged in discussion to share experiences, identify key pain points, and brainstorm solutions to make Wikipedia a truly mobile-friendly and accessible platform for all.

Discussion Summary

Why do you think mobile editing completion is much lower than desktop? Small screens, clunky interfaces, accidental entry, and shorter, more distracted mobile sessions make it harder to complete edits
Why do mobile users abandon edits they’ve started? Confusing UI, frequent distractions, and poor mobile workflows (like switching tabs or losing progress) lead users to give up mid-edit.
What works well on mobile web? Editing on the go is convenient for small fixes, and mobile accessibility—especially in low-connectivity environments—is a major advantage.
If Wikimedia were mobile-first from the start, how would editing look? Tools would be simplified, modular, and interactive—centered on mobile-native input (e.g. voice, video, geo-tagging) with AI and playful UIs.

What bold step should we take to double mobile participation? Improve the mobile editing experience, offer smarter onboarding and suggestions, and scale access through campaigns and cross-wiki improvements.

Session Recap

Most of the group is generally familiar with Mobile Web editing with a minority of participants claiming that they tried to edit on mobile but gave up and some never tried editing on mobile web.

In response to the open-ended question “Why do you think the edit completion rate is so low on mobile web when compared to desktop? (Type your answers below).”

Respondents indicated:

Editing on mobile is physically difficult: Small screens, limited typing space, and difficulty placing the cursor make editing frustrating.
The editing interface is not user-friendly or intuitive: The mobile UI and editor tools are hard to learn, navigate, or access.
Many users enter the editor unintentionally or just to explore: Accidental clicks and casual curiosity reduce completion rates.
Mobile usage tends to be shorter and less focused: Users spend less time per session, lowering the likelihood of completing edits.

Question on editing difficulty: In your opinion, which editing action is hardest to do on mobile?

In response to the open-ended question “Recent enwiki analysis found that mobile users were significantly more likely to abandon an edit they've started? Why do you think this is the case?”

Respondents indicated:

The editing experience is frustrating or confusing: Users may get stuck, open the wrong section, or struggle with a tiresome UI.
Mobile use is prone to distraction and interruption: Short attention spans, external distractions, and multitasking reduce edit completion.
Mobile workflows don’t support sustained editing: It’s hard to switch between tabs for research, and users may lose their place or need to stop suddenly.
UI elements like the publish button are less prominent: A less visible or less motivating call to action may contribute to abandonment.

What is your opinion on the statement: "Not everything is a downside. Mobile web editing offers flexibility and some people prefer it." About 54% of respondents agreed with the statement, while 23% disagreed.

In response to the open-ended question “What’s one thing that works well on mobile web? Or, what are some advantages of mobile web editing?”

Respondents indicated:

Mobility and convenience: Users can edit on the go, from anywhere, without needing a desktop—especially useful when mobile is their only device.
Good for small, quick edits: Mobile is well-suited for typo fixes and light corrections that don’t require complex workflows.
Accessible even in constrained environments: Users noted success editing with poor internet connections and using features like VisualEditor forms or the Commons app.
Mobile is the primary platform for many users: As more users come online primarily via mobile, its accessibility makes it a key entry point for participation.

In response to the open-ended question “If Wikimedia were starting today in a mobile-first world, how do you think our editing tools would look different?”

Respondents indicated:

Simplified, intuitive UI/UX: A mobile-first Wikimedia would likely feature a more playful, beginner-friendly, and interactive interface—with editing by sentence or word, instant feedback, and minimal exposure to wikitext.
Enhanced input and media features: Voice editing, video integration, geo-tagging, and image uploads would be more deeply embedded—mirroring how people create and consume content on mobile.
Smaller, modular editing workflows: Instead of editing entire sections, tools might favor short-form, sentence-level contributions and lightweight, auto-filled forms to streamline edits.
AI and automation: A mobile-first system might rely more on AI to assist users with suggestions, auto-population, and guided contributions.
Design shaped by mobile-native norms: The project structure—including Commons and Wikidata—would be redesigned with mobile contributors in mind, possibly at the cost of some privacy or open-source principles.

In response to the open-ended question “If we wanted to double mobile editing outcomes and participation in 3 years, what bold step should we take?”

Respondents indicated:

1. Improve Mobile Editing UX & Parity with Desktop

Optimize the visual editor and ensure it matches desktop functionality
Create a more intuitive, responsive, and native-feeling UI
Make mobile editing easier and more natural than desktop

2. Expand Onboarding, Tutorials, and Motivation

Introduce short tutorials and smart, structured edit suggestions
Break editing into smaller, selectable tasks for ease on mobile
Prompt users with location-based or interest-based edit opportunities

3. Broaden Access and Ecosystem Integration

Push for mobile-friendly design across all wikis (Commons, Wikidata, etc.)
Preinstall editing tools/apps on devices or streamline login (e.g. via Google)
Use community campaigns, testimonials, and live editing sessions to build momentum