Community Wishlist Survey 2019/Mobile and apps

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search

Community Wishlist Survey 2019

Mobile and apps
12 proposals, 228 contributors

Go-previous.svg Miscellaneous  •  Multimedia and Commons Go-next.svg

The survey has closed. Thanks for your participation :)
Here are the Community Wishlist Survey 2019 results!


Bring Sitenotice to Mobile view

Edit proposal/discussion

  • Problem: Wikipedia editing is growing up so fast these days due to easy accessibility to mobile. Mostly New editors, readers and information seekers get the mobile view while surfing wikipedia on Mobile devices. We on our wiki organise various new events and edit-a-thons every other month. The only way to get more editor's to edit is by the Sitenotice. Unfortunately wikipedia sites on mobile only show central notice by which we can't target a huge audience.
  • Who would benefit: Almost every mobile user will get the coverage of the notice that is going on in the desktop view. This will limit the bridge between the desktop version and mobile version and editors can get updated information about a wiki.
  • Proposed solution: Enabling a proper sitenotice for mobile. Similar and not marshy like the centralnotice
  • More comments:
  • Phabricator tickets:

Discussion

For the records: phab:T150391 implies that first of all, Sitenotice needs to be made mobile-friendly. --AKlapper (WMF) (talk) 14:53, 31 October 2018 (UTC)

wgMinervaEnableSiteNotice allows you to enable site notices on the mobile MinervaNeue skin and it already exists but is disabled by default. Any project can enable this via a site request. However, whoever enables it, needs to make sure their site notices are both mobile and desktop friendly as site notices can cause performance degradations and user frustration (usually vented on Twitter). I'd recommend installing some community best practices for editors managing the site notice, before doing that, but there's nothing stopping anyone from doing this now without any wikimedia input. Jdlrobson (talk) 23:00, 1 November 2018 (UTC)

Voting

Display interproject links on mobile

Edit proposal/discussion

  • Problem: our readers, who now read mainly Wikipedia with the mobile version, don't have easy access to the interproject links (sister project links?) of an article.
  • Who would benefit: more than half of the readers.
  • Proposed solution: give readers the opportunity to display interproject links such as interlanguage links.
  • More comments: on frwiki, we used the template Autres projets to display interproject links before Mediawiki takes care of them. Today, it still exists principally because the functionality is missing on mobile. Some contributors find that the template pollutes the footer of the articles and would like to delete it, which is not possible without impacting the readers' experience on the mobile version.
  • Phabricator tickets:
  • Proposer: Lofhi (talk) 21:12, 8 November 2018 (UTC)

Discussion

  • I'm fairly certain inter-language links can already be accessed in mobile. I could be wrong. --Izno (talk) 00:34, 9 November 2018 (UTC)
    Izno : interlanguage links yes (enwiki, dewiki, ruwiki, etc.), but not interproject links (Commons, Wiktionary, etc.). Lofhi (talk) 08:03, 9 November 2018 (UTC)
  • @Lofhi: This is unlikely to be in the top ten, but your wish is already being developed as part of overhaul of mobile editing. –Ammarpad (talk) 05:51, 19 November 2018 (UTC)
    Ammarpad : I think the functionality may be too discreet, but it's better than nothing! Thanks for the info. Lofhi (talk) 18:05, 19 November 2018 (UTC)

Voting

Support reverting/undoing accidentally sent thanks

Edit proposal/discussion

  • Problem: On mobile, the risk of accidentally sending thanks by touching the big thank button is very high (“fat finger accident”). As many users reported, this could be very frustrating and can cause awkward moments. Different ideas to solve this are already existing (see the Phabricator ticket).
  • Who would benefit: every mobile user
  • Proposed solution: see the Phabricator ticket
  • More comments:
  • Phabricator tickets: T63737
  • Proposer: Bencemac (talk) 09:16, 11 November 2018 (UTC)

Discussion

A patch exists and just needs a review so if voted this is very doable!! Jdlrobson (talk) 20:41, 15 November 2018 (UTC)

Bencemac what about viewing [1] on mobile (using Timeless skin)? --Gryllida 07:34, 23 November 2018 (UTC)

@Gryllida: Most of us do not use Timeless (and do not want to, I guess). Bencemac (talk) 08:06, 23 November 2018 (UTC)

Voting

Add an undo/revert button to diff view

Edit proposal/discussion

  • Problem: The mobile web diff view features an enormous 'thank' button at the bottom of the screen. Sadly, I find myself reverting people far more often than I thank them. Quickly reverting a dodgy edit is the sort of quick editing that should work well on mobile. Unfortunately, the mobile interface makes this all but impossible without manually rewriting the text or zooming the view after switching to desktop interface.
  • Who would benefit: Editors checking their watchlist or recentfeed on their phones.
  • Proposed solution: Provide an undo button adjacent to the thank button. Undoing an edit would work the same way as on the desktop site - open the editing interface with the offending text removed from the source.
  • More comments: already proposed in 2017

Discussion

Should this be limited to users with "revert" rights for now, to gauge the effects?--Strainu (talk) 21:28, 29 October 2018 (UTC)

I thought everyone with "edit" right can also revert on desktop? --Dvorapa (talk) 21:36, 29 October 2018 (UTC)
  • Endorse: I would have proposed the same. Sheriff | ☎ 911 | 01:46, 4 November 2018 (UTC)
  • Endorse --Patriccck (talk) 09:15, 4 November 2018 (UTC)
  • Endorse, and if possible add a Rollback option as well for users who have it. The Thank function can go if there isn't enough space. Feminist (talk) 04:02, 7 November 2018 (UTC)
  • Endorse, we also do need a button to move page in mobile view. CyberTroopers (talk) 13:54, 18 November 2018 (UTC)
  • I've thought about this for a while and I oppose it. There's another proposal regarding the "fat finger" problem of accidentally thanking other editors, now someone wants to add an additional "fat finger" problem of accidentally undoing or even rolling back my edits. No thanks. You can revert my edit by editing the page to remove the bit you don't like; maybe it's good to slow down and think about what you're doing instead of banging buttons. Jacknstock (talk) 10:56, 20 November 2018 (UTC)
  • Comment Comment I have created a JavaScript hack at en:User:FR30799386/undo which allows a user to do a undo an edit on mobile.FR30799386 (talk) 08:16, 29 November 2018 (UTC)

Voting

Show categories on Commons mobile website

Edit proposal/discussion

No category link here...
No category link here either.
  • Problem: When viewing a Commons image in a mobile browser, I can't see the image's categories. Let's say I want to see images of durians, I take my smartphone and launch a Google/etc search on the term "durian". The fifth result is a picture on Commons, I click it. The picture is OK but I am hoping for better pictures. If there was a "Durians" category link on that page, I could click it and browse all durian pictures on Commons.
  • Who would benefit: Mobile users who are viewing an image and want to see similar images.
  • Proposed solution: Show category links.
  • More comments: Please note that this is about the mobile version of the website. The Commons native Android app already has this feature.
  • Proposer: Syced (talk) 03:52, 31 October 2018 (UTC)

Discussion

Hi Syced. If you click through to Commons from Google (using the "Wikimedia Commons" button), then you are able to click on the "Durians" category, in your example. So do I understand that what you're looking for is a link to the category directly from the Google Images page? Please clarify.—JMatazzoni (WMF) (talk) 15:30, 31 October 2018 (UTC)

JMatazzoni (WMF): Please let me know where on this page (see the 2 screenshots) is the link you are talking about, thanks! Syced (talk) 01:45, 1 November 2018 (UTC)
@Syced and JMatazzoni (WMF): The button for categories is only presented for users that are logged in AND have the Mobile beta setting enabled. I do note that most non-wikimedians have no idea how our category system works btw, so they aren't going to find other durians that way. See also: https://wikimediafoundation.org/2018/10/29/george-oates-conversation/ where it is noted: "She noted how the category system used to organize and tag media files on Commons is confusing and hides—not shows—the richness of content there." —TheDJ (talkcontribs) 15:51, 1 November 2018 (UTC)
Hey, thanks TheDJ. You are right, that Categories link shows only if you are logged in and have the beta activated (I didn't realize I had done that). Also, I'd thought there was a link directly to the category, but in fact I was looking at something else (the image happened to be the main image on the Durians category page, so there was a link directly to the category). The typical experience is that you have to click a "Categories" button and then find the relevant category and click on that. All of which is to say that Syced is totally right. I'd like to see a prominent link to the categories on the main image page as well. —JMatazzoni (WMF) (talk) 17:12, 1 November 2018 (UTC)
As the TheDJ mentions, this feature is currently only available if you have the mobile beta mode turned on. The only reason it hasn't been enabled for everyone yet is that the feature still has a few bugs (see task T24660). Thus fulfilling this wish would basically mean fixing those bugs and then releasing the feature to everyone. Kaldari (talk) 17:15, 1 November 2018 (UTC)
+1 to that... this is actually a very actionable wishlist item, that could be fulfilled with enough votes. Happy to provide details of what's needed there, if necessary. Jdlrobson (talk) 22:16, 1 November 2018 (UTC)
While I agree that categories are confusing and sometimes hide good pictures (for instance the durian picture that fits my needs best might be in "Monochrome photographs of Surabaya durians in 2015"). But still, it is the best navigation system we have, so we should not remove that feature. Let's not assume that non-logged-in people (=me most of the time, especially on mobile) can not fathom the "complexity" of a category page. Maybe the key to making categories more useful for everyone is to make them display the best pictures with that category and its sub-categories, rather than pictures that have not been categorized further (FastCCI could be key to implementing that technical change), but that's a whole other kettle of worms. Syced (talk) 03:37, 2 November 2018 (UTC)

Voting

Save button to save the unfinished content for a new page

Edit proposal/discussion

  • Problem: As the number of editors on Wikipedia mobile continues to grow, there exists a need for a save feature while creating new pages on Wikipedia mobile as creating a new page can take days and one needs to save their content for which they worked hard on.
  • Who would benefit: This would benefit almost every registered user on Wikipedia as this would prevent loss of content by accidental closing of the app/browser on which the editor is logged on. It will also prevent the loss of content due to reloading of pages.
  • Suggested Solution: a save feature should be added to the mobile version of the Wikipedia just like it's added on the desktop version of Wikipedia so that editors on the mobile version can conveniently create new pages whilst being on the phone.
  • Phabricator tickets:
  • Proposer: U1Quattro (talk) 03:08, 5 November 2018 (UTC)

Discussion

mw:Extension:Drafts exists, though I'm not sure if that supports mobile. --AKlapper (WMF) (talk) 12:26, 5 November 2018 (UTC)

It doesn't work for mobile. That is what I'm suggesting. It should work for mobile. U1Quattro (talk) 16:56, 5 November 2018 (UTC)
Will userspace subpages help?--Cohaf (talk) 21:18, 13 November 2018 (UTC)

Voting

Show categories in the Wikipedia app

Edit proposal/discussion

  • Problem: Wikipedia editors spend a significant amount of time categorizing pages so that relevant pages can be quickly found. Not having access to these categories puts mobile app users at a significant disadvantage over desktop users. As more users in the developing world come online, they are missing a critical part of articles, especially if they start editing the encyclopedia. In addition, people are switching to mobile at a rapid pace, so feature parity with desktop sites are critical.
  • Who would benefit: Mobile app users (both readers and editors)
  • Proposed solution: Add a list of categories that article is in at the bottom of the article as a list. Also, create a navigation link to access these categories along with the article's sections.
  • Proposer: Daylen (talk) 04:54, 30 October 2018 (UTC)

Discussion

  • Endorse. Looks like almost everyone agrees to this idea. But do the Wikipedia mobile app technical team require more time to implement this? Chongkian (talk) 03:59, 5 November 2018 (UTC)
  • Endorse. I would like to have categories shown in my mobile since when I bought it. I think categories are very useful for editors and readers, too. --Daniele Pugliesi (talk) 18:35, 5 November 2018 (UTC)
  • Strongly support. This also applies to navigation templates, which showcase the main articles about a specific topic. --Joalbertine (talk) 20:07, 6 November 2018 (UTC)
  • Endorse, and add them to the mobile website as well. Feminist (talk) 03:55, 7 November 2018 (UTC)
  • I'm doubtful that readers (non-editing readers) spend much time looking in categories. I don't think that anyone has ever verified that readers notice the categories or use them. It might be interesting to see if we could get page view data split (logged-in vs logged-out) to determine whether the category system is worthwhile at all (to people who aren't editors like us, of course; I use it for editing purposes). WhatamIdoing (talk) 18:23, 26 November 2018 (UTC)

Voting

Make copy/paste functions easier tablets and phones

Edit proposal/discussion

  • Problem: it’s quite a pain to copy/paste on iPads/tablets and phones. Most of the time, you have to scroll through everything to select and copy them, and it’s quite painful especially if they’re modules. This technique takes longer and sometimes causes the devices to freeze and the browsers to crash. It would be amazing to have a button that would automatically select and copy the content of the templates/modules installed by default.
  • Who would benefit: everyone who uses phones and tablets to contribute
  • Proposed solution: add a button that automatically selects and copies the content of the mentioned pages.
  • More comments: There is a a Mobile Copying and Pasting discussion topic at MediaWiki, created by Whatamidoing (WMF).
  • Phabricator tickets:
  • Proposer: ▸ ‎épine talk 10:44, 4 November 2018 (UTC)

Discussion

@Épine: Could you please explain why you have to copy and paste the content of a page so often on tablets or phones? I'd love to understand better the underlying problem to solve. --AKlapper (WMF) (talk) 00:48, 5 November 2018 (UTC)

@AKlapper (WMF): when moving modules and templates to smaller wikis, it is necessary to copy from the source obviously. I contribute to multiple projects and the issue is site-wide.--▸ ‎épine talk 08:49, 5 November 2018 (UTC)
Obviously this is a problem faced by mobile users, and yes I am typing this using my phone. FYI, I written DYKs using phone. Copying can be a hassle, especially for major editing of articles or even AFD where sometimes multiple articles are nominated with the same reason but not bundled together and the interface really makes it a chore to copy your rationale multiple time. However, I don't think this is a site issue but rather hardware issue, your mobile phone OS does play a role in the ease of copy and paste. My 2 cents.--Cohaf (talk) 19:36, 16 November 2018 (UTC)

I face this problem all the time when I travel and use my phone to edit, as I can't access my laptop. --Мурад 97 (talk) 11:29, 18 November 2018 (UTC)

The main problem I have is with scrolling while editing. Sometimes the whole page scrolls instead of only the edit box, which makes editing frustrating! Sometimes I have to switch to desktop view just to complete an edit. Erzahler (talk) 23:55, 22 November 2018 (UTC)

Voting

Offer different wikitext editors including non-JS editor

Edit proposal/discussion

  • Problem: Currently there are numerous problems I encountered when I try to use mobile browser to edit wiki when I use the default mobile web editor. For instance:
    1. When editing an article and then the browser page get removed from memory due to lack of memory, text typed in javascript-generated editor would not be remembered by the browser, however text typed in traditional text field would be
    2. The current default mobile web editor cannot be used to edit a partially prefilled form on wiki like this community wishlist survey
    3. The "insertable wikimarkup" thing is a bit hard to access on the default mobile web editor.
  • Who would benefit: Everyone who edit on mobile phone
  • Proposed solution: These can be fixed by allowing users to change the mobile editor themselves or by changing the default editor for everyone
  • More comments: The first point in the problem I mentioned is an inherent limitation caused by dynamically generated pages and apparently cannot be fixed by patching the existing editor and thus a change would be needed

Discussion

Did you try the timeless or monobook skin C933103? They are getting more mobile friendly particularly timeless, and may partly address your issues? Gryllida 22:48, 30 October 2018 (UTC)

  • @Gryllida: They still show the same mobile editor with same limitations. (Actually it doesn't seems like the mobile skin vary according to the skin setting?) C933103 (talk) 01:19, 31 October 2018 (UTC)
  • Jdlrobson Deskana, this seems like something your team might have an interest in. Are you guys already working on these issues (in which case we might withdraw the proposal). Or is this something you need help with? Are there any issues you see? —JMatazzoni (WMF) (talk) 18:00, 31 October 2018 (UTC)
  • Also ping @Jdforrester (WMF):, the question Jmatazzoni asked also affects the future roadmaps of VE. --Liuxinyu970226 (talk) 11:36, 11 November 2018 (UTC)

Voting

Make interlanguage links more discoverable on the mobile site

Edit proposal/discussion

  • Problem: The mobile version of the site doesn't have interlanguage links. With mobile, I sometimes enter a Finnish Wikipedia article with Google and notice it's a stub, and I have to switch to the desktop version just to access the English Wikipedia.
  • Who would benefit: Especially people who speak a language that doesn't have a large Wikipedia.
  • Proposed solution: Enable interlanguage links.
  • More comments:
  • Phabricator tickets:
  • Proposer: Pudeo (talk) 14:08, 3 November 2018 (UTC)

Discussion

Interlanguage links are available on the mobile web. Just below the article title is this button, which will bring up the list of interlanguage links. I do think that the menu is not as obvious as it should be. Rchard2scout (talk) 15:19, 3 November 2018 (UTC)

I see. Well, that's not obvious at all (the symbol is cryptic), but glad the feature exists. There seems to be a lot of space next to it, so maybe they should clarify it with "other languages" or something. --Pudeo (talk) 15:23, 3 November 2018 (UTC)
Ping User:jdlrobson, exactly what I told you during our last meetup. Part of this probably has to do with the fact that desktop doesn't use icons like this.... Difficult problem to solve in my opinion. —TheDJ (talkcontribs) 10:45, 5 November 2018 (UTC)
yeh we are completely aware of this problem. If it was up to me I'd add a language link in the footer which when clicked scrolls you to the top and points at the language button. People searching the page would then find it. We used to do something similar when transitioning in the new language button. Jdlrobson (talk) 20:43, 5 November 2018 (UTC)
Side note, we do have some data that compares an older treatment (a button at the bottom of the page) with a new treatment @ phab:T128917#2120680. Maybe there's a wishlist ask here to help with discoverability of these features (I've seen similarly phrased requests for talk and categories which are also in the mobile UI if you know where to find them) Jdlrobson (talk) 21:57, 5 November 2018 (UTC)

Voting

Add a citation option to mobile editing

Edit proposal/discussion

  • Problem: Mobile editors are not able to add citations, they have to use the desktop version of Wikipedia in order add a reference.
  • Who would benefit: Mobile editors
  • Proposed solution: This proposal will add an option to make a citation while editing on the mobile site.
  • More comments:
  • Phabricator tickets:
  • Proposer: ParadiseDesertOasis8888 (talk) 00:52, 4 November 2018 (UTC)

Discussion

  • Endorse. Maybe we can reduce the size of Thank button and add two more buttons Undo and Ref or Citation! Sheriff | ☎ 911 | 01:53, 4 November 2018 (UTC)
  • Really, they can't? That explains a lot. Is this only in VE? There are many people whose only computer is a smartphone, so this seems like this is a systemic bias problem. HLHJ (talk) 08:12, 14 November 2018 (UTC)
  • FYI, If you use visual editing on mobile, then you have access to the full Citation functionality of Visual Editor. That is web only however, not compatible with the apps. —TheDJ (talkcontribs) 14:50, 19 November 2018 (UTC)

Voting

Show navboxes on mobile website and app

Edit proposal/discussion

  • Problem: Navboxes are a common way to link between related topics on articles. These are not shown on the mobile view, limiting the ability of readers to browse related topics.
  • Who would benefit: Readers and editors
  • Proposed solution: Show navboxes on the mobile app and web view. Use side scrolling if there is not enough space, similar to how tables are handled.
  • More comments:
  • Phabricator tickets: T124168
  • Proposer: Feminist (talk) 04:18, 7 November 2018 (UTC)

Discussion

  • Hi Feminist. Thanks for submitting a proposal. Can you give an example too for people who are unfamiliar with what navboxes are? I think the term "navbox" is very English-wikipedia centric. I'd prefer to generalize it so folks from other wikis can recognize the need here and vote for it too. -- NKohli (WMF) (talk) 21:54, 7 November 2018 (UTC)
  • There are a lot of UI design problems with this proposal, and most of them are documented in Phabricator. There is also the download-size problem, also documented there. I don't really think this is a good CommTech task because of the question of navbox size. --Izno (talk) 00:02, 9 November 2018 (UTC)
    • +1 - I'm curious to how this would work? The templates need a lot of work and it's unclear to me if WMF is officially allowed to edit templates and whether that counts as paid editing. Enabling them as is would be detrimental to performance and user experience so doing so will require a lot of community support. Given the high amounts of votes for this has anyone thought about how this would be scoped? Is the request for some kind of consultancy on how those templates can be improved? Hindu Wikipedia did something similar with updating their main page for mobile. Jdlrobson (talk) 21:12, 22 November 2018 (UTC)

Voting

  • Support Support Tom Ja (talk) 20:18, 16 November 2018 (UTC)
  • Support Support Yousefi 1234 (talk) 05:35, 17 November 2018 (UTC)
  • Support Support Liuxinyu970226 (talk) 09:24, 17 November 2018 (UTC)
  • Support Support I think it could be made work even with the knowledge of current technical limits. Right now mobile version significantly lacks navigation options, so experimenting with providing more of them should be good. stjn[ru] 09:32, 17 November 2018 (UTC)
  • Support Support Jo-Jo Eumerus (talk, contributions) 10:20, 17 November 2018 (UTC)
  • Support Support ديفيد عادل وهبة خليل 2 (talk) 10:50, 17 November 2018 (UTC)
  • Support Support ‐‐1997kB (talk) 11:29, 17 November 2018 (UTC)
  • Support Support Kpgjhpjm (talk) 13:44, 17 November 2018 (UTC)
  • Support Support Carlodell (talk) 14:11, 17 November 2018 (UTC)
  • Support Support Sometimes I had to switch my phone in the desktop view so the navbox can be displayed. I hope there'll be a mobile version. CyberTroopers (talk) 14:13, 17 November 2018 (UTC)
  • Support Support Nouill (talk) 15:07, 17 November 2018 (UTC)
  • Support Support Yilku1 (talk) 17:10, 17 November 2018 (UTC)
  • Support Support JogiAsad (talk) 18:09, 17 November 2018 (UTC)
  • Support Support Andree.sk (talk) 19:59, 17 November 2018 (UTC)
  • Support SupportThanks for the fish! talkcontribs 20:29, 17 November 2018 (UTC)
  • Support SupportAmmarpad (talk) 22:10, 17 November 2018 (UTC)
  • Support Support Capankajsmilyo (talk) 00:06, 18 November 2018 (UTC)
  • Support Support Megalibrarygirl (talk) 02:28, 18 November 2018 (UTC)
  • Support Support I've been dreaming of this 日暮卯白 (talk) 03:40, 18 November 2018 (UTC)
  • Support Support Patriccck (talk) 07:44, 18 November 2018 (UTC)
  • Support Support as proposer Feminist (talk) 08:56, 18 November 2018 (UTC)
  • Support Support DerFussi 10:31, 18 November 2018 (UTC)
  • Support Support Jon Harald Søby (talk) 12:58, 18 November 2018 (UTC)
  • Support SupportMeiræ 22:22, 18 November 2018 (UTC)
  • Support Support -- Whats new?(talk) 22:34, 18 November 2018 (UTC)
  • Support Support Yesssss. Lack of navigation boxes and categories is the reason I very often open an article on mobile just to remind myself to check it out later on desktop. Joalbertine (talk) 08:45, 19 November 2018 (UTC)
  • Support Support আফতাবুজ্জামান (talk) 20:43, 19 November 2018 (UTC)
  • Support Support Mr. Fulano! Talk 21:19, 19 November 2018 (UTC)
  • Support Support Perhaps some of the concerns about this feature could be alleviated by imposing a limit on the number of links in a navbox. Any navbox that exceeded the limit would continue to be hidden. This might encourage people to break up some of the awful, sprawling examples - and everyone would benefit from that. Gareth (talk) 12:28, 20 November 2018 (UTC)
  • Support Support Vulphere 12:39, 20 November 2018 (UTC)
  • Support Support Lord van Tasm (talk) 13:45, 20 November 2018 (UTC)
  • Support Support This is long in coming and needed.  Paine Ellsworth  put'r there  17:11, 20 November 2018 (UTC)
  • Support Support --FDo64 (talk) 22:34, 20 November 2018 (UTC)
  • Support Support CAPTAIN RAJU(T) 22:44, 20 November 2018 (UTC)
  • Support Support Novak Watchmen (talk) 01:44, 21 November 2018 (UTC)
  • Support Support --Berdea (talk) 10:41, 21 November 2018 (UTC)
  • Oppose Oppose unless communities are willing to put the effort in to make navboxes significantly more mobile friendly using tools like TemplateStyles, which were recently deployed for this exact purpose. Navboxes were hidden for a reason: they have very poor usability on mobile. In some rare cases even account for up to 50% of the data transmitted to a person's mobile device, significantly increasing their data usage, which is very bad for people in emerging communities that use slow mobile devices on metered data connections. Simply cramming something into the mobile viewport (when it even has poor usability on desktop!) and expecting to deliver value is naive. We should meet in the middle, by putting in the effort to make the navboxes actually mobile friendly, then consider putting them into the mobile views. --Deskana (talk) 12:29, 22 November 2018 (UTC)
  • Support Support Lirazelf (talk) 12:57, 22 November 2018 (UTC)
  • Oppose Oppose just remove mobile frontend altogether and use the mobile-friendly timeless skin. Gryllida 08:20, 23 November 2018 (UTC)
  • Support Support - Please! Lazz R (talk) 18:14, 23 November 2018 (UTC)
  • Support Support Jared-li (talk) 02:15, 24 November 2018 (UTC)
  • Support Support At the very least they should be able to be seen on tablet screens Vctrbarbieri (talk) 02:57, 24 November 2018 (UTC)
  • Support Support HouseGecko (talk) 12:30, 24 November 2018 (UTC)
  • Support Support Gce (talk) 15:03, 24 November 2018 (UTC)
  • Support Support Chepry (talk) 16:43, 24 November 2018 (UTC)
  • Support Support Kaartic correct me, if i'm wrong 17:13, 24 November 2018 (UTC)
  • Support Support Martin2035 (talk) 09:04, 25 November 2018 (UTC)
  • Support Support Ethno & 4D (talk) 09:35, 25 November 2018 (UTC)
  • Support Support Ranjithsiji (talk) 22:59, 25 November 2018 (UTC)
  • Support Support — AfroThundr (u · t · c) 02:24, 26 November 2018 (UTC)
  • Support Support Misaochan (talk) 13:46, 27 November 2018 (UTC)
  • Support Support Grawiton (talk) 20:34, 27 November 2018 (UTC)
  • Oppose Oppose per Deskana. Daniel Case (talk) 18:08, 28 November 2018 (UTC)
  • Support Support Fauvirt (talk) 18:31, 28 November 2018 (UTC)
  • Support Support - tucoxn\talk 21:30, 28 November 2018 (UTC)
  • Support Support Netanel488 (talk) 23:11, 28 November 2018 (UTC)
  • Support Support Ldorfman (talk) 20:23, 29 November 2018 (UTC)
  • Support Support Cymru.lass (talk) 20:34, 29 November 2018 (UTC)