Wikidata talk:Usability and usefulness/Item editing experience/Mobile editing of statements

Long values? Never heard

I'm not sure how to comment on the prototype, as it is English-centric and doesn't even try to use long values. Everything works fine if you using "start time" or "reference URL". At the same time, we can already see that "determination method…" (20 characters) is cut as it is too long for a table, and "located in the administrative territorial …" is too long for a selection list. In many languages, we have hundreds of properties that start with "идентификатор"/"identyfikator"/"identificador" (13 characters + space), so we have only 6 characters to distinguish between them.
The same issue with "edit". Try to use Ukrainian with "редагувати" or Greek with "επεξεργασία" and you will immediately see that there is simply no room for this text. —putnik 19:06, 12 June 2025 (UTC)

Thank you Putnik, this is really helpful and important feedback. You're absolutely right that terms like "редагувати" or "επεξεργασία" can quickly run into space constraints, and that many property labels are much longer in other languages or start with similar prefixes. At this stage, the prototype is intentionally simplified to test the core layout and interaction patterns. But as we move forward, we’ll definitely be looking at how the design handles longer values, multilingual labels, and RTL scripts to ensure it's usable and inclusive for everyone. Mohammed Abdulai (WMDE) (talk) 10:02, 16 June 2025 (UTC)

Dates

Can you explain why you don't use a date picker for date values? Discostu (talk) 20:34, 13 June 2025 (UTC)

Thanks for the question @Discostu! We’re intentionally replicating how dates are entered on desktop to ensure consistency across devices. A date picker might seem more convenient at first, but it can limit flexibility for example historical dates, uncertain values and non Gregorian calendars. The current input method supports a wider range of formats and use cases, which is important for Wikidata’s diverse data needs. Mohammed Abdulai (WMDE) (talk) 13:07, 16 June 2025 (UTC)

Interface Language

I didn't see how to change the default interface language from English to a language of choice by a user.

And also I love to know the options hidden under the Hamburger icon in the top left

And is there any way possible of interacting with the prototype directly? B722N (talk) 03:25, 14 June 2025 (UTC)

Hi @B722N, Thank you for your feedback and good catch. Changing the interface language and the options in the hamburger menu will continue to work the same way as they do currently. This prototype focuses specifically on testing improvements to how statements are displayed and edited.

The prototype isn’t interactive at this stage. It’s just a visual demonstration to test and gather feedback on the new layout for viewing and editing Item statements. - Mohammed Abdulai (WMDE) (talk) 11:22, 24 June 2025 (UTC)

Thank you for the feedback̊̊@Mohammed Abdulai (WMDE) B722N (talk) 11:26, 24 June 2025 (UTC)

Simple Mode & Advanced Mode

I wonder if the user interface could be made simpler. Or perhaps we could introduce two modes of operation: Simple Mode (limited features for basic tasks) and Advanced Mode (full-featured, with all the complex buttons displayed). For the Simple Mode, I’ve made a prototype here : https://wdlite.toolforge.org/?item=Q180 Niryhpr (talk) 09:20, 16 June 2025 (UTC)

Thanks so much for that idea. Yes we’ve been exploring similar concepts, including collapsed or simplified versions of the interface to reduce visual complexity. Your prototype is really helpful in showing how a Simple Mode could work. We'll take a closer look and consider how best to incorporate that kind of flexibility. Mohammed Abdulai (WMDE) (talk) 13:23, 16 June 2025 (UTC)