Community Wishlist Survey 2019/Archive/Add option to set the mobile skin and desktop skin

Add option to set the mobile skin and desktop skin

  • Problem: The current default mobile skin which is forced onto all users is not extremely featured for the editor community(understatement). With the advent of responsive skins like Timeless and Monobook (the mobile version), it seems unfair that the mobile editor community will be stranded with a skin that was primarily meant for readers.
  • Who would benefit: All users who edit Wikipedia on mobile interface
  • Proposed solution: Allow users to set separate mobile and desktop skins. Thus, I could be able to select monobook's mobile version/Timeless for mobile and Vector/Monobook/Modern on desktop.
  • More comments: This is an alternative proposal to Replace the mobile frontend with the timeless skin which advocates a complete change over to Timeless. I personally prefer if the choice of the skin was left to the editor's own liking. The Wikimedia Foundation will always be free to serve up the reader's skin (MiniveraNeue) to most anon users.

Discussion

Hi FR30799386: we've got a product team working on this right now; check out the Advanced mobile contributions project. They're bringing lots of editor controls to the mobile site -- here's a current mock-up:

 

So I'm going to archive this proposal, because the work is already in progress. Thanks for participating in the survey! -- DannyH (WMF) (talk) 19:00, 15 November 2018 (UTC)[reply]

DannyH (WMF), I am already aware of the current work being done to improve the mobile skin and I support it. However, this proposal is not about improving the mobile skin ! It is about adding the ability for editors to switch skins while the mobile Frontend is deployed. Among other things, it will add the ability to use the citoid extension on the mobile interface, something that the current MiniveraNeue work does not have on its agenda. I hope I was able to clear your misconceptions. If you have any other questions you are free to ask them to me here. Regards.FR30799386 (talk) 10:26, 16 November 2018 (UTC)[reply]
" Among other things, it will add the ability to use the citoid extension on the mobile interface, something that the current MiniveraNeue work does not have on its agenda." - Sadly I'm not sure this is true. The issue with many things on mobile is not related to the skin MinervaNeue, but related to the JavaScript used on these pages. I'd recommend you have a play with the Vector mobile skin by appending useskin=vector to the end of mobile URIs (example) to see what I mean. Personally, this is why I would have supported this preference (even if it was a hidden one via the API) as it will help share knowledge of this problem (and help find solutions!) as right now there's a lot of misinformation about how our mobile site is configured/works and how that's separate from skin. Jdlrobson (talk) 16:07, 29 November 2018 (UTC)[reply]