Community Wishlist Survey 2016/Categories/Mobile and apps

Mobile and apps
10 proposals, 87 contributors, 168 support votes

Improved app for browsing Commons

  • Problem: The Commons app is just for upload. You don't see the picture of the day, recent Featured Pictures (FP), ongoing photo challenges, contests, winners of the previous contests.
  • Who would benefit: Wikimedia Commons could increase its penetration. This could bring more daily users of the app, and increase the visibility of the Commons volunteers work, and maybe more volunteers.
  • Proposed solution: Create an app that shows off the content of Wikimedia Commons, with an easy uploader.
Instead of the app showing our own pictures at home, it could show FPs on a subject that the user selects, or recent pictures uploaded by a volunteer that we like. does a good job at this; we could do something similar in the app.
We could have a tab to explore and find available pictures. Having selected images with the possibility to see the original size, allowing readers to see details. In addition to that, it could have a detailed description, in our case could be a WP article and data from Wikidata. For inspiration, Google Arts & Culture and Second Canvas do a very interesting job in the content area.
  • Phabricator tickets:

Community discussion

  • Rather than forcing everyone to install "Second Cavas" to understand what you mean, would you mind explaining what it does that you like and that the Android upload app does not do yet? Thanks a lot! :-) Syced (talk) 08:27, 15 November 2016 (UTC)
    • @R.T.Argenton: This proposal currently feels a bit vague. Which exact technical improvement(s) are you looking for? Also, have you tried c:Commons:Mobile app? If yes, does it fulfil your needs? If not, what specifically are you missing in that app? --AKlapper (WMF) (talk) 12:36, 15 November 2016 (UTC)
The actual app it's just for upload. And that's it, we don't see the picture of the day, I can't see recent Feature Pictures (FP), ongoing photo challenges, contests, winners of the previous,...
The 500px app is very similar to their website we could do something similar in the app. Instead the app show our on pictures at home, it could show FPs on a determinate subject (that the user select), or recent pictures of a volunteer that we like, we could have a tab to explore and find pictures available... In another tab have something more content oriented, just as the mentioned Google Arts & Culture and Second Canvas (serious, just enter, you don't need to download it.)
Having selected images with the possibility to see the original size, allowing readers to see details, in addition to that it could have a detailed description, in our case could be a WP article and data from Wikidata...
This could bring more daily users of the app, and increase the visibility of the Commons volunteers work, and maybe more volunteers.
Got it? Rodrigo Tetsuo Argenton m 00:28, 17 November 2016 (UTC)
@R.T.Argenton: I used your additional info to revise the proposal, it's just below in the collapsed box. I took out the reference to the easy uploader, because everything else you wrote is about the browsing/discovery experience. What do you think? -- DannyH (WMF) (talk) 23:13, 18 November 2016 (UTC)

Thanks Danny, its pretty much it, however I do not want to separate them. That's way I mentioned "with a easy uploader", not easier*, it's okay as a uploader, but we could include this content mentioned, to have a more attractive, compelling app. Got it? Rodrigo Tetsuo Argenton m 04:57, 19 November 2016 (UTC)

R.T.Argenton: Got it! I put the easy uploader back in. This is a great proposal, thanks! -- DannyH (WMF) (talk) 23:09, 19 November 2016 (UTC)

Hi R.T.Argenton - just a heads-up, I've moved your proposal to this Mobile and apps page. -- DannyH (WMF) (talk) 01:56, 23 November 2016 (UTC)

Danny did you mix the discussions, don't you? I removed the duplicate part that bellows to the other discussion, feel free to revert. Rodrigo Tetsuo Argenton m 17:24, 24 November 2016 (UTC)
R.T. Argenton: oh, I did mix those. Thank you! -- DannyH (WMF) (talk) 21:13, 24 November 2016 (UTC)

Voting – Improved app for browsing Commons

  1.   Support add browse function--Shizhao (talk) 03:00, 28 November 2016 (UTC)
  2.   Support SamanthaNguyen (talk) 00:23, 30 November 2016 (UTC)
  3.   Support, it should show great images to the user such as contest-winners and nominees and featured pictures (with their associated description and potentially article, switching image by a simple swipe) while also allowing search and the display of categories etc. The app could be openable from the Wikipedia app. --Fixuture (talk) 20:58, 30 November 2016 (UTC)
  4.   Neutral I don't think it can be big size for app and can be low. Murbaut (talk) 13:19, 1 December 2016 (UTC)
  5.   Support Sandiooses (talk) 17:41, 2 December 2016 (UTC)
  6.   Support --Juandedeboca (talk) 15:06, 5 December 2016 (UTC)
  7.   SupportHmxhmx 16:22, 5 December 2016 (UTC)
  8.   Support - Ciridae (talk) 09:32, 8 December 2016 (UTC)
  9.   SupportNickK (talk) 10:20, 12 December 2016 (UTC)

Real-Time Recent Changes App for Android/iOS

  • Problem: Reviewing changes on Android is clunky and bandwidth intensive. Requires desktop version of site on mobile and multiple key punches before actual work can begin. No facility of offline reveiewing.
  • Who would benefit: Reviewers using Mobiles
  • Proposed solution: Dedicated Android based stand-alone app for Reviewing activity on wikipedia, (RTRC App for Android/iOS)
  • More comments: presently one has to load Android browser, open wikipedia, login, click on side bar, choose settings.... before starting the work. its too cumbersome on mobile. Low bandwidth in countries like India (where I'm from) add to the woes. Bandwidth issue becomes worse while travelling. I would like if I can check a few pages if I have 10-20 minutes spare time, on my mobile... like while I'm travelling, and have a few minutes in hand. I would like to be kept logged in with pre-set mostly used configurations, offline support for storing 20-50 unreviewed changes, batch processing, reviewable while offline-updated as soon as I get good signal/start internet again, etc.
  • Phabricator tickets:

Community discussion

  • @Anamdas: Unfortunately, currently no underlying problem to solve is described in this proposal. Also, what does "RTRC" stand for? Also, does your Android browser not allow storing cookies and keep you logged in? I am also wondering why you have to click on the side bar and choose settings every time - why would you have to change the settings within you Wikipedia every time and which settings are those exactly? I am asking to better understand the underlying problems you are facing... --AKlapper (WMF) (talk) 19:41, 14 November 2016 (UTC)
I think it means "Real time recent changes". -- NKohli (WMF) (talk) 05:23, 15 November 2016 (UTC)
Hi, AKlapper (WMF), Sorry for late reply. Thanks, NKohli (WMF) for your help. Yes, I'm talking about Real Time Recent Changes tool for reviewers. The underlying problem is that : as a reviewer, I strongly feel the need of an Android based stand-alone app for Reviewing activity on wikipedia. Regards. --Anamdas (talk) 09:28, 16 November 2016 (UTC)
It might be fair to say that "Problem = reviewing changes on Android is clunky and bandwidth intensive." Rich Farmbrough 20:35 17 November 2016 (GMT).
Thanks, Rich. Changed as advised.--Anamdas (talk) 09:33, 18 November 2016 (UTC)

Hi Anamdas - just a heads-up, I've moved your proposal to this Mobile and apps page. -- DannyH (WMF) (talk) 01:48, 23 November 2016 (UTC)

Voting – Real-Time Recent Changes App for Android

  1.   Support: as a proposer.--Anamdas (talk) 08:50, 2 December 2016 (UTC)
  2.   Support I hold Wikipedia trainings in Accra, Ghana. It's getting more mobile every day. Most own a mobile device but not a laptop. And many complain of not knowing what to edit. Recent changes app will be great for keeping up with the prospective articles that may be needing their contributions. Even if not a separate app, it can be added to the Wikipedia app itself. Sandiooses (talk) 17:36, 2 December 2016 (UTC)
  3.   Support and iOS, please :) --Framawiki (talk) 20:42, 2 December 2016 (UTC)
  4.   Support Anything that enables more reviews of recent changes is good. Also, check out "Hide trusted users" checkbox option on watchlists and related/recent changes (RC) pages as another way to make RC patrol more manageable. Stevie is the man! TalkWork 19:13, 4 December 2016 (UTC)
  5.   SupportHmxhmx 16:22, 5 December 2016 (UTC)
  6.   Support--Ranjithsiji (talk) 11:14, 6 December 2016 (UTC)
  7.   Support --Nikola (talk) 13:40, 9 December 2016 (UTC)
  8.   Support--Nizil Shah (talk) 06:22, 10 December 2016 (UTC)

Stereo viewer for the Wikipedia app

  • Problem: We have lots of stereo imagery, but it is hard to view. Commons includes many stereo images; see Commons:Category:Stereo images. Many are in old collections going back to the nineteenth century, others are modern. Some people can "free fuse" them to enjoy the 3-D effect with no extra equipment, but for most the only option I am aware of is to print the images out and put them a stereo viewer.
  • Who would benefit: Users who could enjoy our stereo collection if it were easy to view. Having such a viewer could stimulate new stereo content creation for Commons as well.
  • Proposed solution: Stereo view adapters for smartphones and tablets are becoming widely available, sometimes simply made of cardboard. I would like to see a option in the Wikipedia apps (or if necessary a new standalone app) that would display a stereo image in a way that is compatible with those adapters. Ideally it should have options for viewing both a single commons file with two images and a pair of commons files that constitute a stereo view. Perhaps an adjustment slider might be provided to get spacing and alignment right. The software showed be able to navigate through a sequence of slides, perhaps from a Commons page or a list as well and also from a Commons category.
  • Phabricator tickets:

Community discussion

Hi ArnoldReinhold - just a heads-up, I've moved your proposal to this Mobile and apps page. -- DannyH (WMF) (talk) 01:57, 23 November 2016 (UTC)

  • Would using WebVR make more sense? Building and maintaining separate stereo/photosphere viewers for each major platform/HMD (Windows: Rift, Vive. Android: GearVR, Daydream. iOS: Cardboard) doesn't seem sustainable. Related: Improve 360 panorama support. Dispenser (talk) 02:17, 24 November 2016 (UTC)

Voting – Stereo viewer for the Wikipedia app

  1.   Support Ainali (talk) 14:23, 30 November 2016 (UTC)

Support the creation of more attractive pages on mobile

  • Problem: Making attractive and non buggy pages on Wikimedia projects that are mobile friendly is very very hard and extremely time consuming. People working on these pages have less time to work on content if there are spending a large amount of time changing code and trying to fix bugs. In short the barrier to entry to creating good looking pages is far too high.
Default wiki pages don't offer solutions that fit current design trends, and hence are not engaging for audiences outside the movement. Further, sometimes a more complex structure is needed for better navigation, in those cases where there is too much information.
This problem is a number of technical, documentation and ease of use issues.
Examples of attractive pages that are modern and attractive but are buggy and took a very long time to create
  • Who would benefit: Everyone who would like to make Wikimedia pages more attractive.
  • Proposed solution: There are a number of parts of the solution including:
  • Phabricator tickets:

Community discussion

@John Cummings: As proposals should be as specific as possible, I'm wondering if you could elaborate on the problem (what are examples for "buggy pages" that are not mobile friendly?) and the potential solutions (what makes pages "attractive"? what are current "ease of use" issues? what are examples for "better documentatrion" that you would like to see?) to help anybody get a shared understanding of what is requested in this proposal and define the scope and potential specific actions to improve the situation. Thanks in advance! --AKlapper (WMF) (talk) 12:23, 9 November 2016 (UTC)

Thanks AKlapper (WMF), I've added some examples. I'm not really sure how I can illustrate how hard these are to create, to make the Simple Reuse guide took me at least a week of messing about with code. John Cummings (talk) 16:44, 9 November 2016 (UTC)
  • The buggy pages are a result of the fact that programming HTML is hard, yet we have given those tools to people who shouldn't be building websites. The solution is to give people more layout options in the form of classes etc that they can use or template styles, instead of having to program in a limited form of HTML and CSS. There are some phabricator tickets on things related to this, but they are a bit stuck in over ambition, or underestimation of reality. Bootstrap-like classes for wikieditors for layouting, and semantic classes for content identification. —TheDJ (talkcontribs) 11:38, 11 November 2016 (UTC)
  • FWIW, I find all the linked pages very unattractive and anti-engaging. Nemo 08:27, 15 November 2016 (UTC)
  • Hi Nemo, are there particular aspects you take issue with? Do you have any suggestions to improve the pages? "unattractive and anti-engaging" doesn't give many pointers to work with. Richard Nevell (WMUK) (talk) 13:47, 17 November 2016 (UTC)
  • Nemo, could you give some examples of Wiki pages that you think are attractive and engaging? Then we could use those as possible examples to work from.StuartPrior (talk) 14:50, 17 November 2016 (UTC)
Nemo_bis, please can you expand on your comment, just saying the pages are unattractive and anti-engaging without expanding on it is not very helpful and is probably pretty demotivating for the people who worked on them, especially since the whole point of this proposal is that these sorts of pages take a lot of time and effort to make. --John Cummings (talk) 14:56, 18 November 2016 (UTC)
  • yes, need a toolkit, wizard, pre-formated template, design for page creation, which can be refreshed by designers, to professionalize the look and feel and engagement of projects and events. Slowking4 (talk) 14:57, 16 November 2016 (UTC)

Hi John Cummings - just a heads-up, I've moved your proposal to this Mobile and apps page. -- DannyH (WMF) (talk) 01:58, 23 November 2016 (UTC)

FYI, there are gadgets MobileView and Mobile-sidebar (commons:Category:Mobile-sidebar mediawiki gadget) which might help. --Atlasowa (talk) 14:24, 5 December 2016 (UTC)

Voting – Support the creation of more attractive pages on mobile

  1.   Support Libcub (talk) 02:29, 2 December 2016 (UTC)
  2.   Support --Ranjithsiji (talk) 11:13, 6 December 2016 (UTC)
  3.   Support --CreativeC38 (talk) 21:06, 6 December 2016 (UTC)
  4.   Support Tyseria (talk) 13:54, 7 December 2016 (UTC)
  5.   Support SamanthaNguyen (talk) 23:58, 12 December 2016 (UTC)

Uploading from a mobile phone

  • Problem: Uploading from a mobile phone is too hard!
  • Who would benefit: People who have a mobile phone and want to contribute through photos to Wikimedia Commons, people who want to make videos or sound recordings, organizers of numerous activities and tools to make demand-based-contributions easier (i.e. by pointing out locations that still require a photo). Activities like Wiki Loves Monuments/Earth/Art/Africa would become likely more successful if implemented well.
  • Proposed solution: Set up anc easier way to contribute realtime produced photos, videos and sound recordings to Wikimedia Commons. This could be an app, or an improved upload interface on the (mobile) website. Part of the solution has to be in making the social process easier. This tool/app/method should be possible to integrate with other tools, and allow 'delayed uploading': marking a photo for upload when there's a better/cheaper internet connection. Focus should be on (real time) self-produced materials.
  • Phabricator tickets:

Community discussion

If uploading from a mobile phone is too hard, specific information and steps are welcome why it is hard, to better understand the underlying problems and potential solutions. Also, have you tried c:Commons:Mobile app already? --AKlapper (WMF) (talk) 22:00, 7 November 2016 (UTC)

I tried the app just now (was not aware there was one again, thanks for the pointer), previously I mostly remembered whatever you're sent to when you try uploading when you're working from Wikipedia (i.e. through a monument list). The integration with other tools (Wikipedia, maps etc) is important for image uploaders to be triggered to share something.
But apart from that, the workflow didn't feel natural. When you start, it is hard to understand what was going on. At some point I think I was seeing new images being uploaded? And without being asked for a license, whether I took the photo myself or anything, or to confirm anything, the image was suddenly uploaded (even before the category selection, which was apparently added in a later edit) - which I only noticed because it was the top image on the 'recently uploaded' flow. Quite a confusing experience. The design looks nice though, and the uploading itself was quite smooth. But I would never use this for contributing photos myself, because it doesn't connect the photo upload with parts of my phone that I would actively use anyway. Effeietsanders (talk) 23:33, 7 November 2016 (UTC)
Thanks for the feedback Effeietsanders! I agree that we could do with some UI changes. The license can be selected in Settings, but we need to update that and make the selection more explicit, perhaps in the upload screen. Yeah, image uploading starts as soon as you select the picture, with categories being added later. I think the original developers thought that would save time, but it can be changed if many users prefer otherwise. How do you feel we could better connect the photo upload with parts of your phone you would actively use? Misaochan (talk) 00:59, 15 November 2016 (UTC)
I use this app a lot, and it is integrated nicely in Android as it can receive a 'share-intent', that is, from your usual photo app you can "share to -> Wikimedia Commons" which takes you directly to title and description. The feature on remembering the last used categories in a top list makes it easy to upload many images from the same event or object at once. Ainali (talk) 15:39, 30 November 2016 (UTC)

my impression for WLM upload was find talk page and then start upload to integrate monument number. could it possible to integrate article missing image with location to tag photo? Slowking4 (talk) 02:27, 8 November 2016 (UTC)

Also we have to remember that uploading from mobile has been bounced back HARD by the Commons community in the past. Basically in order to tackle this issue, you first need to deliver a significant improvement in the ability to review (either fully automatic or with human assistance) new uploads, so that an increase of uploads can be handled by the existing amount of labour force available within the Commons community. The one cannot be separated from the other. —TheDJ (talkcontribs) 15:10, 8 November 2016 (UTC)
Yes, uploading from mobile used to be quite easy, circa 2014, but too many people were uploading copyrighted images or selfies, so the Commons community asked the mobile team to turn off the feature, which they did. See Commons:Mobile access/Mobile upload needing check#Background and the post-mortem on the mobile-l mailing list for the full background. Kaldari (talk) 22:50, 9 November 2016 (UTC)
From what I know, the Android app is back and working now. It was recently overhauled as part of a GSoC project. The iOS app is still unavailable. -- NKohli (WMF) (talk) 20:01, 14 November 2016 (UTC)
  • Unfortunately, i have to oppose this proposal per commons:Commons:Mobile_access/Mobile_upload_needing_check#Background --Steinsplitter (talk) 15:03, 10 November 2016 (UTC)
  • This would be a waste of resources since we will likely end up with designing a filter to block those uploads... This is a been there, done that kind of situation. It didn't work in the past and no argument why it should work now has been provided. Natuur12 (talk) 14:33, 11 November 2016 (UTC)
    Wouldn't it make sense to figure out fields where it would make sense? For example, for Wiki Loves Monuments-related campaigns, where there are clear identifiers available with geographic restrictions, people are asked to identify the photo, and that can more easily be checked. 'm especially thinking about ways that workflows are improved for photographers, and clearly defined requests can be made to photograph objects (which can be checked again). But I agree there has to be a more thought out plan before starting to code (and the commons community is crucial in that). IHowever, at some point, we will have to fix mobile uploading. Effeietsanders (talk) 10:56, 15 November 2016 (UTC)
  • @AKlapper (WMF): the mobile app would be fine IF it worked. But it keeps crashing. It's far from being a better alternative... The AAndroid version keeps crashing upon opening, without even loading in. If it happens to work after mulétiple reinstalling, it's cumbersome to use, especially the categories (doesn't add the selected categories after upload). Teemeah (talk) 17:35, 13 November 2016 (UTC)
    • @Teemeah: I see. Could you link to the bug report about the crashes that you are experiencing? --AKlapper (WMF) (talk) 18:44, 14 November 2016 (UTC)
      • @Teemeah: I glanced through the recent crash reports and was unsure which one is yours. Could you please submit a fresh crash report and let me know when you have done so, with either the email address used to send it or the time of submission to identify it? Also, we are aware that some users are experiencing issues with categories not being saved, but the issue is spotty and not everyone experiences it. We are currently trying to debug that, so input would be appreciated here. In the future if there is a major issue like that, please do let us know on GitHub or the forums. We are only a team of volunteers (and one part-time grantee), but we generally try to do our best to resolve issues that users have, when we are made aware of them. Misaochan (talk) 01:19, 15 November 2016 (UTC)
@Misaochan: I deleted the app after it crashed on me a dozen times a few days ago. I could upload some photos a couple of months ago with the app (minus adding the categories, because it was never working for me), but now it just simply crashed again and again (Android 6.0, EMUI 4.0.1 on PLK-L01, if that helps). Teemeah (talk) 08:38, 15 November 2016 (UTC)
@Teemeah: Unfortunately we need to be able to see the stack trace in order to find out which line of code is causing the crash, as well as the app version etc associated with it. If you do try the app again in the future, please select 'send crash report' after it crashes, and if possible follow up with a thread in GitHub or the forums letting us know that the crash is constant for you (occasional crashes are not as worrisome as constant ones that render the app unusable). Thanks! Misaochan (talk) 09:36, 15 November 2016 (UTC)

There is currently a community-maintained Android app (download here). There is none for iOS as far as I know, sorry.

Re: the copyright/selfie-pocalypse issue, I have heard this mentioned several times, and all of the issues (including those linked here) appear to be about the mobile web interface. The current active mobile app available is a native Android app. The two are inherently very different and have different workflows. Mobile websites are just accessed via browser whereas native apps need to be downloaded by the user, and native apps allow development of features that would not be possible with mobile websites.

These are the stats for the current Android app's uploads vs deletes. It isn't perfect, but it's a far cry from the graph linked for mobile web uploads. We also have a few improvements planned to try and further reduce those - see GitHub issues #95 and #97. Misaochan (talk) 00:50, 15 November 2016 (UTC)

@Misaochan: I downloaded the app again and same issue. Every time I open the app it crashes immediately. I made sure now the crsh report is sent from my email address teemeah.wikiposta[at]gmail(dot)com, so you can check it. Just sent it like a minute ago. Teemeah (talk) 11:07, 17 November 2016 (UTC)
@Teemeah: Thanks, I found your crash report. We will look into it and get back to you as soon as we can manage. Misaochan (talk) 11:12, 17 November 2016 (UTC)
  • Custom uploading interfaces must be avoided. There is no reason for Special:Upload or Special:UploadWizard to not work well in mobile. In fact, per commons:Commons:Village_pump/Archive/2016/08#UploadWizard soon available on the mobile site too, it now does: are you sure this proposal is still current? Nemo 08:15, 15 November 2016 (UTC)
    • you realize that people are going to vicunauploader and pattypan? and i had to go to the old version of special:upload, i.e. lots of interfaces for the veterans. just where is the upload tool integration? Slowking4 (talk) 16:02, 15 November 2016 (UTC)
    • "Custom uploading interfaces must be avoided" is only your personal opinion, and the page you link to is a discussion page where you link again to your own messages. Definitely not a policy. Joining web development forces is probably a good idea, but in the Android world a native app is vastly superior to a web-based uploader. Try taking a picture on Android: the "Share to Commons" button let you share it with one touch whereas using a webapp takes at least three touches (best cases, minimum number of touches to reach the step where you enter the image's title). Syced (talk) 06:37, 16 November 2016 (UTC)

Let me make a quick suggestion: existence of Commons:Mobile app should be advertised on Wikipedia sites like fundraising, through banners, etc. People need to know about it. I know fundrising banners are controversial, but in this case, this is not about asking for money, but to join in and become volunteers. --Piotrus (talk) 08:27, 15 November 2016 (UTC)

Great idea! Syced (talk) 06:37, 16 November 2016 (UTC)
I think we need this app. It will make easy to upload more useful images and can work in many ways. For issue of vandalism, we can restrict upload to people with account and confirmed/extended confirmed user flag on wiki.--Nizil Shah (talk) 12:01, 16 November 2016 (UTC)
That would be great. :) I think the correct link is c:Commons:Mobile_app though - the link above brings me to a nonexisting page. Misaochan (talk) 11:21, 17 November 2016 (UTC)
I am in favor of this idea. Uploading via mobile phones could be of great use during photo contests for instance. We organized photo hunts during Wiki Loves Africa, and we noticed that many volunteers were taking pictures using their phones. If the uploading process was easy, those pictures could have been uploaded to commons in no time. African Hope (talk) 15:54, 17 November 2016 (UTC)

This is a great idea.If wikimedia develop app about wikicommons( I think making wikipedia,wikitionary,wikicommons and so on into one app is best choose.),it should include upload photos,voices,change information ,etc. The volunteer can use mobile phone everywhere to share their contributions.--晾衣杆 (talk) 14:32, 18 November 2016 (UTC)

I use the iOS version of the Commons app a lot and I generally find it much easier to use than the Commons desktop upload tool. Providing me with a list of my most recent categories is especially helpful. My biggest complaint is that it is too hard to find images deep in my photo library. The thumbnails are too small, even if enlarged using the iOS accessibility tool. A simple improvement would be to allow entry of a date, with only images on or after that date displayed. Default would be today's date. Then I could find an image I want to upload with other tools, get its date and have the app display it up front. There is also a weird bug that makes the upload button inoperable after a couple of uses. I work around this by killing the app with a swipe up. On opening the app again, it shows the image I wanted to upload as "queued" and lets me upload it from the main screen. I'm using the latest iOS 10.1.1.--ArnoldReinhold (talk) 15:49, 21 November 2016 (UTC)

Hi Effeietsanders - just a heads-up, I've moved your proposal to this Mobile and apps page. -- DannyH (WMF) (talk) 01:55, 23 November 2016 (UTC)

Voting – Uploading from a mobile phone

  1.   Support I usually just give up, nobody needs my uploads anyway. --Oop (talk) 23:11, 29 November 2016 (UTC)
  2.   Support It is a pain to email photos to myself so I can upload them on the desktop version Daylen (talk) 20:28, 1 December 2016 (UTC)
  3.   Support Talmoryair (talk) 13:15, 2 December 2016 (UTC)
  4.   Support Unlike reading on mobile, which can be done even without the app, uploading is something that should receive a disproportionate amount of attention on mobile (IMO) because most people take pictures on mobile nowadays, and no one should be expected to use the regular site on mobile for uploading (if it even works). —Ynhockey (talk) 11:44, 7 December 2016 (UTC)
  5.   Support Agreed. The Commons app really needs some updates in this regard. Ciridae (talk) 09:39, 8 December 2016 (UTC)
  6.   Support - Restricted to authenticated, confirmed users. DPdH (talk) 22:05, 9 December 2016 (UTC)
  7.   Support --OrsolyaVirág (talk) 11:44, 10 December 2016 (UTC)
  8.   Support, uploading photos from a mobile phone should be really easy. In addition, chances are high that these photos will be one works, as people are way more likely to have own photos on mobile rather than store a collection of copyvios on their mobile — NickK (talk) 10:25, 12 December 2016 (UTC)
  9.   Support--Mikheil Talk 21:12, 12 December 2016 (UTC)
  10.   Support SamanthaNguyen (talk) 23:58, 12 December 2016 (UTC)

Video support on iOS devices

  • Problem: Videos can not be played on iOS devices.
  • Who would benefit: Users of these devices would be the prime beneficiaries. Secondary the entire community would benefit since more people would be compelled to create free videos. In Sweden (unfortunately) Ipads are common in schools and flipped classroom is quite common, but since the videos cannot be played on their devices they don't bother to upload it to Commons even though they can agree on releasing it under a free license.
  • Proposed solution: ?
  • Proposer: Ainali (talk) 18:17, 14 November 2016 (UTC)

Community discussion

  • i think User:Brion Vibber (WMF) is working on it, but more elevation of video issues is a good thing. we could expand it to more video editing tools (expanded popcorn), after we can actually watch them. Slowking4 (talk) 16:40, 15 November 2016 (UTC)
  • Video is currently unstaffed and fully reliant on volunteers (being brion ad me actually). The progress is thus accordingly. I'd welcome any dedicated resource for it. —TheDJ (talkcontribs) 00:12, 16 November 2016 (UTC)
  • Playing Video in iOS devices would be great. Uploading video (often vertical) from iOS devices would also be great. --Jarekt (talk) 04:27, 17 November 2016 (UTC)

Hi Ainali, just a heads-up -- I moved this proposal to the Mobile & apps page. -- DannyH (WMF) (talk) 21:50, 23 November 2016 (UTC)

  • Ogg Theora video is playing on iOS 10 Safari with the Vector skin, in software by JavaScript (also Devices with WebM/VP9 hardware) and without playback controls.
    Neither Theora or WebM are working in the app nor the mobile skin. iOS VLC is rendering the video corrupt (file renders in OPlayer desynced at 50% speed). Dispenser (talk) 00:04, 24 November 2016 (UTC)

Voting – Video support on iOS devices

  1.   Support --Telaneo (User talk page) 21:54, 29 November 2016 (UTC)
  2.   Oppose This sounds a lot like the idea that was already rejected for going against the Foundation's principles. Connor Behan (talk) 19:09, 1 December 2016 (UTC)
  3.   Support --Morten Haan (talk) 23:14, 2 December 2016 (UTC)
  4.   Support --Juandedeboca (talk) 15:11, 5 December 2016 (UTC)
  5.   Oppose --WinTakeAll (talk) 22:18, 5 December 2016 (UTC)
  6.   Support - Doesn't seem fair to leave out readers due to device compatibility. DPdH (talk) 22:07, 9 December 2016 (UTC)
  7.   Oppose --Cvf-ps (talk) 21:27, 10 December 2016 (UTC)
  8.   Comment. @Connor Behan, WinTakeAll, and Cvf-ps:, if your oppose is to MPEG 4/H.264 that's a separate issue, but solutions to this can be 1) adding WebM decoder to the iOS App and/or 2) Making OGV.js work better on mobile. Dispenser (talk) 00:18, 11 December 2016 (UTC)
  9.   Neutral. This is worthwhile, but looks like this does not really depend on us, but more on webm support in iOS. It would be great if iOS would support free file formats, but this may be too hard for Community Tech — NickK (talk) 10:28, 12 December 2016 (UTC)

Add categories to the app

  • Problem: Categories are an integral part of Wikipedia. Users can use them to find articles they'd like to find or simply related articles (among other things such as better understanding the topic of an article). For some reason however the app doesn't show the categories. The only workaround is to tap the edit button on the bottom-most section to display the categories in wiki-syntax (they still can't be browsed though and this is no solution).
  • Who would benefit: Everyone using the app
  • Proposed solution: Below (or above?) the "Read more" row display the article's categories which can be clicked.
  • More comments: This suggestion is for the app and the mobile version of the site.
  • Phabricator tickets:

Community discussion

  • Absolutely, those who do not have access to categories are at a real disadvantage. @Fixuture: (just pinging you to see if the feature works for you here - I did not get a ping from you when you sent one before) Ottawahitech (talk) 23:56, 23 November 2016 (UTC)please ping me

̽* Good idea - That'll be very useful.--Anamdas (talk) 12:19, 24 November 2016 (UTC)

  • This is the main reason I don't use the app. Libcub (talk) 02:31, 2 December 2016 (UTC)

Voting – Add categories to the app

  1.   Support--Shizhao (talk) 03:01, 28 November 2016 (UTC)
  2.   Support —The preceding unsigned comment was added by Murbaut (talk)
  3.   Support --Strainu (talk) 10:33, 28 November 2016 (UTC)
  4.   Support Sadads (talk) 15:33, 28 November 2016 (UTC)
  5.   Support Nocowardsoulismine (talk) 18:42, 28 November 2016 (UTC)
  6.   Support JAn Dudík (talk) 21:58, 28 November 2016 (UTC)
  7.   Support One of the reason why I hate the mobile version. --Oop (talk) 23:12, 29 November 2016 (UTC)
  8.   Support --Una giornata uggiosa '94 · So, what do you want to talk about? 00:57, 1 December 2016 (UTC)
  9.   SupportMurbaut (talk) 13:45, 1 December 2016 (UTC)
  10.   Support --Grabado (talk) 18:38, 1 December 2016 (UTC)
  11.   Support Ermahgerd9 (talk) 19:00, 1 December 2016 (UTC)
  12.   Support --AmaryllisGardener talk 19:08, 1 December 2016 (UTC)
  13.   Support Afnecors (talk) 19:33, 1 December 2016 (UTC)
  14.   Support --Vachovec1 (talk) 20:03, 1 December 2016 (UTC)
  15.   Support Daylen (talk) 20:28, 1 December 2016 (UTC)
  16.   Support«« Man77 »» [de] 22:03, 1 December 2016 (UTC)
  17.   Support Libcub (talk) 02:31, 2 December 2016 (UTC)
  18.   SupportTheDJ (talkcontribs) 10:03, 2 December 2016 (UTC)
  19.   SupportJc86035 (talk) 11:15, 2 December 2016 (UTC)
  20.   Support Sandiooses (talk) 17:40, 2 December 2016 (UTC)
  21.   Support Jianhui67 talkcontribs 10:03, 3 December 2016 (UTC)
  22.   Support Without categories wikipedia is pretty useless for me as an editor, and also as reader. Ottawahitech (talk) 15:21, 3 December 2016 (UTC)please ping me
  23.   Support Demostene119 (talk) 17:47, 3 December 2016 (UTC)
  24.   Support MGChecker (talk) 13:04, 4 December 2016 (UTC)
  25. Strong   Support I don't want all the categorization work I've done to go to waste for mobile users. They should be able to navigate through them as well as desktop users. Stevie is the man! TalkWork 19:23, 4 December 2016 (UTC)
  26.   Support Yes. Please! More isn't always better; in this case it most certainly is an improvement. CmdrDan (talk) 19:48, 4 December 2016 (UTC)
  27.   Support - Add categories to the mobile Wikpedia! --Atlasowa (talk) 09:55, 5 December 2016 (UTC)
  28.   Support --β16 - (talk) 11:06, 5 December 2016 (UTC)
  29.   SupportHmxhmx 16:22, 5 December 2016 (UTC)
  30.   Support Lbertolotti (talk) 00:41, 6 December 2016 (UTC)
  31.   Support --Wikipal (talk) 11:52, 6 December 2016 (UTC)
  32.   Support --Yapparina (talk) 12:34, 6 December 2016 (UTC)
  33.   Support --CreativeC38 (talk) 21:07, 6 December 2016 (UTC)
  34.   Support Tyseria (talk) 13:53, 7 December 2016 (UTC)
  35.   Oppose — Categories are bogus and a rest from the early 2000's, when Wikipedia was created. They are not useful 15 years later and should be replaced as soon as we can with proper search and query functionality with Wikidata. Categories serve negligible purpose for desktop users, and even less for mobile viewers (who are nearly entirely readers). To keep clutter like categories out of the mobile app is a conscious decision. CFCF 💌 📧 20:56, 7 December 2016 (UTC)
    I have found them very useful ever since they came on the scene, but everyone is entitled to their opinion. At any rate, I would not oppose making this a user option. Stevie is the man! TalkWork 20:23, 8 December 2016 (UTC)
  36.   Support Ayack (talk) 11:55, 9 December 2016 (UTC)
  37.   Support - DPdH (talk) 22:08, 9 December 2016 (UTC)
  38.   Support--Nizil Shah (talk) 06:20, 10 December 2016 (UTC)
  39.   Support --OrsolyaVirág (talk) 11:44, 10 December 2016 (UTC)
  40.   Support --Cvf-ps (talk) 21:27, 10 December 2016 (UTC)
  41.   Support --Goonsquad LCpl Mulvaney (talk) 03:56, 11 December 2016 (UTC)
  42.   Support -- Mobile readers and editors should not miss out on useful stuff like categories! PamD (talk) 09:38, 11 December 2016 (UTC)
  43.   Support Essential.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  17:20, 11 December 2016 (UTC)
  44.   Support, yes please, I don't understand why categories cannot be seen on mobile as they are potentially very useful — NickK (talk) 10:29, 12 December 2016 (UTC)
  45.   Support --KuboF (talk) 21:30, 12 December 2016 (UTC)

Add navboxes to mobile/app version

  • Problem: Today, navigational boxes (placed at the bottom of a lot of articles) aren't showing in the mobile/app version of Wikipedia. These navboxes create easy links to related articles. Today (in many languages), the mobile/app version of Wikipedia is used around half of the time, which makes for a lot of viewers.
  • Who would benefit: Every reader or contributor who would like to have a better overview of important articles on a subject. On the desktop, long "See also" lists are a poor layout solution and normally solved by exchanging them with navboxes. But if half of the readership cannot see them…
  • Proposed solution: Solve the problems mentioned in this bug. They are visible through Wikiwand (at least the app for iOS), so this should be possible to make happen. Talks of "too much html" have been mentioned in another bug discussion.
  • More comments: Vertical sidebar-style navboxes are visible in the mobile/app version, but they compete with the infoboxes for the space and are therefore less practical (at least on the desktop).

Community discussion

Hi Paracel63 - just a heads-up, I've moved your proposal to this Mobile and apps page. -- DannyH (WMF) (talk) 01:58, 23 November 2016 (UTC)

Voting – Add navboxes to mobile/app version

  1.   Support Oh, yes, please - the behavior of some pages is totally different on mobile than on desktop due to this limitation.--Strainu (talk) 10:34, 28 November 2016 (UTC)
  2.   Support - Gareth (talk) 07:04, 29 November 2016 (UTC)
  3.   Support --Fixuture (talk) 22:21, 29 November 2016 (UTC)
  4.   Support --Una giornata uggiosa '94 · So, what do you want to talk about? 00:57, 1 December 2016 (UTC)
  5.   Support I never understand why they are desactivated... (There aren't one... really). And navbox contains majors informations, in some case ... For me it's very more important than categories. --Nouill (talk) 13:29, 1 December 2016 (UTC)
  6.   Support Daylen (talk) 20:28, 1 December 2016 (UTC)
  7.   Support Libcub (talk) 02:33, 2 December 2016 (UTC)
  8.   Support Sandiooses (talk) 17:40, 2 December 2016 (UTC)
  9.   Support MGChecker (talk) 13:05, 4 December 2016 (UTC)
  10.   Support It's a shame that mobile users can't navigate like desktop users can. Stevie is the man! TalkWork 19:01, 4 December 2016 (UTC)
  11.   Support Yes. Please! More isn't always better; in this case it certainly is an improvement. CmdrDan (talk) 19:43, 4 December 2016 (UTC)
  12.   SupportHmxhmx 16:22, 5 December 2016 (UTC)
  13.   Support --Wikipal (talk) 11:53, 6 December 2016 (UTC)
  14.   Support Tyseria (talk) 13:54, 7 December 2016 (UTC)
  15.   Support: This would great. But make it so in all languages. --M11rtinb (talk) 16:23, 7 December 2016 (UTC)
  16.   Support: Great idea! BoskiBelmondo (talk) 19:15, 7 December 2016 (UTC)
  17.   Oppose CFCF 💌 📧 20:57, 7 December 2016 (UTC)
  18.   Support Navboxes in some form are certainly required. Ciridae (talk) 09:39, 8 December 2016 (UTC)
  19.   Support --Nikola (talk) 18:41, 9 December 2016 (UTC)
  20.   Support Ale And Quail (talk) 03:52, 11 December 2016 (UTC)
  21.   Support -- Mobile readers and editors should not miss out on useful stuff like navboxes! PamD (talk) 09:39, 11 December 2016 (UTC)
  22.   Support Giorgos ab1234 (talk) 13:06, 11 December 2016 (UTC)
  23.   Support Easy navigation is especially important on mobile.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  17:21, 11 December 2016 (UTC)
  24.   Support, I can't understand why those are not available either — NickK (talk) 10:30, 12 December 2016 (UTC)
  25.   Support --KuboF (talk) 21:34, 12 December 2016 (UTC)

Add other project links in mobile apps

  • Problem: When reading an article on the ios Wikipedia app, you can't access the Commons related category. So you only see the pictures on the article and have no way to consult the one on Commons. This issue is also true for Wikidata and all the other Wikimedia projects.
  • Who would benefit: All the persons who consult Wikipedia on their smartphone.
  • Proposed solution: Add links to other project in mobile app.
  • Phabricator tickets:
  • Proposer: Ayack (talk) 20:05, 19 November 2016 (UTC)

Community discussion

  • I support your comment, and also want to include Wiktionary in this list. Noé (talk) 15:09, 21 November 2016 (UTC)

Hi Ayack - just a heads-up, I've moved your proposal to this Mobile and apps page. -- DannyH (WMF) (talk) 01:58, 23 November 2016 (UTC)

Voting – Add other project links in mobile apps

  1.   Support JAn Dudík (talk) 21:58, 28 November 2016 (UTC)
  2.   SupportJeblad 01:50, 29 November 2016 (UTC)
  3.   Support --Telaneo (User talk page) 21:55, 29 November 2016 (UTC)
  4.   Support --Oop (talk) 23:12, 29 November 2016 (UTC)
  5.   Oppose Wikipedia app just wikipedia--Shizhao (talk) 02:48, 30 November 2016 (UTC)
  6.   Support SamanthaNguyen (talk) 01:13, 1 December 2016 (UTC)
  7.   Support --Juandedeboca (talk) 17:54, 1 December 2016 (UTC)
  8.   Neutral I don't think is can be big app size Murbaut (talk) 13:15, 1 December 2016 (UTC)
  9.   Support Libcub (talk) 02:36, 2 December 2016 (UTC)
  10.   Oppose App bloat is a serious problem on smartphones. Have separate apps for separate projects. Stevie is the man! TalkWork 18:59, 4 December 2016 (UTC)
  11.   Support. - Mailer Diablo (talk) 07:02, 7 December 2016 (UTC)
  12.   Support Tyseria (talk) 13:54, 7 December 2016 (UTC)
  13.   Support Ayack (talk) 11:55, 9 December 2016 (UTC)
  14.   Support--Nizil Shah (talk) 06:21, 10 December 2016 (UTC)
  15.   Support - Important feature. DPdH (talk) 06:32, 10 December 2016 (UTC)
  16.   Support, perhaps next to Other languages feature? — NickK (talk) 10:30, 12 December 2016 (UTC)
  17.   Support Template with links to sister proĵects shows bit badly on mobile devices. Maybe there should be at least links (from Wikidata), and not necessarily the possibility to read inside the app. --KuboF (talk) 21:42, 12 December 2016 (UTC)

Add talk page links to the app

  • Problem: This is an essential feature that's long overdue and simply needs to be added to the app and the mobile site ASAP. Currently using the mobile site is just annoying fiddling around - it's not making things easier when you got to switch to the desktop version every minute or so.
  • Who would benefit: Everyone using the app.
  • Proposed solution: It shouldn't take more than a few minutes to fix it either: just add a new entry to the bottom, bottom right or upper right panel with a link to the respective page's talk page which opens the talk page within the app.

Hi Fixuture - just a heads-up, I've moved two of your proposals to this Mobile and apps page. -- DannyH (WMF) (talk) 01:57, 23 November 2016 (UTC)

  • @DannyH (WMF): Yes, I've noticed. Thank your for notifying me and creating that page! --Fixuture (talk) 19:56, 23 November 2016 (UTC)

Community discussion

I just supported adding categories to mobile, but forgot that there are other important featues such as talk which are also not available on mobile view. If we add all of them in we will end up with the desktop view.

Come to think of it there are even more fundamental problems effecting the usability of mobile devices for wiki-editors that are there whether one uses desktop/mobile views. For example, and please forgive me if my experience differs from yours, I find the special characters in common use on wiki, such as ~~~~, to be a real pain to type on the mobile devices I have seen. Ottawahitech (talk) 15:37, 3 December 2016 (UTC)please ping me

Voting – Add talk page links to the app

  1.   Support I sometimes use the Wikipedia app to comment on discussions when I don't want to or can't wait for the desktop version of the site to load on my phone, and I would use it a lot more if it was possible to easily access the talkpage and a "new section" button from within the app. Gestrid (talk) 00:47, 28 November 2016 (UTC)
  2.   Support--Shizhao (talk) 02:58, 28 November 2016 (UTC)
  3.   Support JAn Dudík (talk) 21:59, 28 November 2016 (UTC)
  4.   Support Anthonyhcole (talk) 09:27, 29 November 2016 (UTC)
  5.   Support --Telaneo (User talk page) 21:55, 29 November 2016 (UTC)
  6.   Support also bring back links to desktop version as they disappeared lately. --Jarekt (talk) 04:11, 30 November 2016 (UTC)
  7.   Support --Una giornata uggiosa '94 · So, what do you want to talk about? 00:58, 1 December 2016 (UTC)
  8.   Support I hope great Murbaut (talk) 13:17, 1 December 2016 (UTC)
  9.   Support --Juandedeboca (talk) 18:04, 1 December 2016 (UTC)
  10.   Support--Jdmirandar (talk) 18:58, 1 December 2016 (UTC)
  11.   Support Ermahgerd9 (talk) 19:01, 1 December 2016 (UTC)
  12.   Support --Vachovec1 (talk) 20:02, 1 December 2016 (UTC)
  13.   Support Daylen (talk) 20:28, 1 December 2016 (UTC)
  14.   Support I would also support some general "feedback" button. Mobiles are mainstream we can benefit much from. Matěj Suchánek (talk) 21:20, 1 December 2016 (UTC)
  15.   Support --Gestumblindi (talk) 21:47, 1 December 2016 (UTC)
  16. strong kind of   Support«« Man77 »» [de] 22:02, 1 December 2016 (UTC)
  17.   Support big time --JB82 (talk) 01:13, 2 December 2016 (UTC)
  18.   Support NMaia (talk) 01:44, 2 December 2016 (UTC)
  19.   Support Libcub (talk) 02:28, 2 December 2016 (UTC)
  20.   SupportJc86035 (talk) 11:15, 2 December 2016 (UTC)
  21.   Support – Necessary! Sandiooses (talk) 17:39, 2 December 2016 (UTC)
  22.   Support Yes talk pages are important and one of the drawbacks of the app. One should not / cannot edit without talk pages. Doc James (talk · contribs · email) 04:12, 3 December 2016 (UTC)
  23.   Support --Continua Evoluzione (talk) 15:01, 3 December 2016 (UTC)
  24.   Support Stevie is the man! TalkWork 18:50, 4 December 2016 (UTC)
  25.   Support --β16 - (talk) 11:03, 5 December 2016 (UTC)
  26.   SupportHmxhmx 16:22, 5 December 2016 (UTC)
  27.   Support --Ranjithsiji (talk) 11:13, 6 December 2016 (UTC)
  28.   Support --Wikipal (talk) 11:53, 6 December 2016 (UTC)
  29.   Support Tyseria (talk) 13:54, 7 December 2016 (UTC)
  30.   Support - Talk pages are seriously required and would be a great help to editors. Ciridae (talk) 09:31, 8 December 2016 (UTC)
  31.   Support --Spencer (talk) 14:31, 9 December 2016 (UTC)
  32.   Support --Nizil Shah (talk) 06:22, 10 December 2016 (UTC)
  33.   Support --OrsolyaVirág (talk) 11:45, 10 December 2016 (UTC)
  34.   Support --China Crisis (talk) 13:47, 10 December 2016 (UTC)
  35.   Support --Cvf-ps (talk) 21:29, 10 December 2016 (UTC)
  36.   Support --NaBUru38 (talk)
  37.   Support Ale And Quail (talk) 03:54, 11 December 2016 (UTC)
  38.   Support -- Mobile readers and editors should not miss out on useful stuff like easy access to talk pages! When discussing Wikipedia with sceptical users I recommend them to check the talk page of an article.PamD (talk) 09:42, 11 December 2016 (UTC)
  39.   Support Essential.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  17:19, 11 December 2016 (UTC)
  40.   Support, I have not used the app but I know that talk pages are already available on the mobile version, thus this should be doable — NickK (talk) 10:32, 12 December 2016 (UTC)
  41.   Support --KuboF (talk) 21:45, 12 December 2016 (UTC)