Commons talk:Mobile app

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search

Dropbox bug[edit]

Image previews do not load when uploading photos directly from Dropbox. The photos themselves upload perfectly fine.

Helps needed to avoid dupes and overwrite[edit]

One of my friend started contributing to Commons using mobile uploads. But he faced two issues. 1. It uploads dupes even if the same file exists here. 2. It overwrites existing files if a file with same name already exists. Could you advise how can he avoid these mistakes? Jee 02:47, 5 November 2016 (UTC)

Hi @Jkadavoor: 1. Preventing duplicate uploads is an improvement that we are working on and hope to complete in the near future. Please see this thread for updates. 2. We are currently tracking the overwrite issue here. Unfortunately we still have no idea what is causing it, as it only happens occasionally and only to a few people. Does this happen all the time for your friend? Please post on the GitHub thread with further details and we will try to look into it. Thanks! Misaochan (talk) 05:30, 8 December 2016 (UTC)
Thanks Misaochan; I'll inform him. Jee 06:10, 8 December 2016 (UTC)
It's been a while, but this should finally have been fixed in v2.8.3. Please let us know if further overwrite issues occur, thanks! Misaochan (talk) 07:36, 18 September 2018 (UTC)

Is general browsing of the commons possible on the mobile app?[edit]

It seems that it's not possible to browse/search for pictures and categories on the mobile app. All I get are pictures which I uploaded (~20,000). Why would I want to look at them again on the mobile is beyond me? I already have them on my desktop where viewing is superior. I like browsing and searching categories that relate to my interest: 19th century life.— Ineuw talk 18:46, 7 May 2018 (UTC)

@Ineuw: Well, it was primarily developed for uploading files, not viewing them. But you're lucky: Just today it was announced that User:Ujjwalagrawal17 will start working on implementing browsing features: Commons:Village_pump#Wikimedia Commons app: Allow users to browse Commons from app, phab:T188597. --El Grafo (talk) 07:29, 8 May 2018 (UTC)
@El Grafo:Thanks for the info. Looking forward to using it.— Ineuw talk 08:09, 8 May 2018 (UTC)
@Ineuw: Hi, the browse feature is now available in v2.8, courtesy of our GSoC student Ujjwal! Hope you like it. :) Misaochan (talk) 07:32, 18 September 2018 (UTC)
@Misaochan:Thanks for remembering and letting me know. You are very kind. — Ineuw talk 07:39, 18 September 2018 (UTC)

Other apps[edit]

Have we got a list of apps convenient to Wikiphotographers? Like, are there apps to show a map of unphotographed articles and Wikidata items? Jim.henderson (talk) 12:06, 22 July 2018 (UTC)

Hi Jim.henderson, I'm afraid I can't help you much with other apps, but we do have a map of unphotographed Wikidata items (under the Nearby feature) in the Commons Android app if that helps? Or did you have something else in mind? Misaochan (talk) 07:44, 18 September 2018 (UTC)

Oh! Silly me; I didn't look at that feature. Unfortunately it doesn't show any points that are more than one km from me (I'm typing this from the very dense Midtown Manhattan) so in daytime, even in suburbs, it probably won't be good for planning beyond several minutes of my day on the bicycle. Still, the information will be useful tomorrow when I stop pedaling in Connecticut and pull out the Android phone. As Wikidata becomes more populated the map will become more useful, and I can hope for improvement of the feature in the future. Thanks for the information! Jim.henderson (talk) 01:51, 20 September 2018 (UTC)

Thanks Jim.henderson! Yeah, that aspect of Nearby can definitely be improved. :) We intend to allow users to search in any area of the map that they choose, this should hopefully be implemented by the end of 2018. Misaochan (talk) 15:56, 28 September 2018 (UTC)

Additional app stores[edit]

Any particular reasons as to why this app hasn't been ported to the other popular Android app stores (Amazon Appstore and Samsung Galaxy Apps)? Daylen (talk) 06:05, 18 September 2018 (UTC)

@Daylen: Good question! I created an issue here, will get back to you once the devs have discussed it. :) Misaochan (talk) 07:40, 18 September 2018 (UTC)

How to contribute & some general comments[edit]

Tried the web app last night (UTC -4:00), and found the navigation concept not perfect but I am sure that it will improve over time. The software itself is still very buggy. What type of information does the team require to identify problems? Unfortunately, I can contribute only in a non-technical manner. — Ineuw talk 21:17, 20 September 2018 (UTC)

Hi Ineuw, to clarify, what do you mean by the "web app"? Did you download the Android app (for instance through the Play Store here), or did you go to your mobile phone browser (such as by using this URL)? I am asking this because usually "web app" means a program that runs in the browser, whereas this talk page is for the Android app. ;) But if you did mean the Android app, what bugs did you experience? Thanks! Misaochan (talk) 15:53, 28 September 2018 (UTC)
@Misaochan: My mistake, it was the Android App from the Google App store. As for the bugs, I will repeat what I tried the last time and post the details here.— Ineuw talk 19:32, 28 September 2018 (UTC)

Crash on upload[edit]

On yesterday's bike ride I repeatedly stopped, pulled out my Nexus 6P with Android v6.1.0, checked the Commons app v2.8.3 for nearby pins, went there, clicked the target name to bring up OpenCamera v1.44.1, and snapped a photo. Completed the filename I wanted, and, umm, maybe the category, hit the right-arrow to upload, and got "Unfortunately the Commons app has stopped". Not exactly those words, but yes. And the picture isn't in Gallery, either. Restarted the phone a couple times to repeat in various places a few km away. Still doesn't work. Fortunately the beautiful warm day wasn't completely wasted as I also snapped the target with my big zoom camera. Next time, I'll try using Android's own camera app instead of my preferred OpenCamera, but I'm pessimistic.

So the following day, I tried again, this time afoot in shady places so I could see the screen clearly. No, not category. Here's more detail. I tapped the object pin, the name of the target, the + sign and the camera symbol. Used the camera app to snap the picture. Commons app came up, I added my initials as usual to the default filename, and right-arrow to upload. A box popped up to say the Commons app stopped. I restarted Android (probably not necessary), switched camera apps, and went through the whole thing again. Same result, several times. No picture was put in Photos. Snapped a few photos with both apps and not using the Commons app; got those few photos in Photos.
Far as I can see, the Commons app is preventing the camera app from storing the photo. Commons app tries to upload, but there's nothing, so the app stops. Obviously I don't know enough to be sure of that. Is it working for other users? Jim.henderson (talk) 16:01, 1 October 2018 (UTC)
I use the Commons App to upload pictures taken with my smartphone, with various results. Sure it is fast and easy, but the App is really buggy. I have reported some issues to the devs who are very responsive. Some of the issues have been fixed, some remain. But I always upload pictures long after they were taken, so I don't use the process you describe above. I suggest your report your problem to them. Regards, Yann (talk) 16:32, 1 October 2018 (UTC)
Hi Jim.henderson, could I please get you to update your app to the latest version (if you go to "About" in the app via the navigation drawer, it should say v2.8.4) and try uploading again? We have recently fixed an issue with recurring crashes that were affecting some users, so it would be good to see if it works for you now. Sorry about that! Misaochan (talk) 10:11, 2 October 2018 (UTC)
Done. Actually, before you wrote that, the upgrade appeared on Google Play Store. So, with that version I walked a couple hundred meters again to the same ENWP articled but uninteresting dance school. Same procedure, using first the Google default camera app and then Open Camera. This time, no crash. After asking and accepting the Category, it returned to the map, still showing the purple pin. I went home to check with the real computer. No pictures in Commons with those names; no personal upload record; no new pictures in that Category. No new pictures in Android Photos in the phone. Nice that v2.8.4 doesn't crash in this trial, but it still isn't working. I'll try again soon with a different procedure. Snap photos, then tell Google Photos to upload by Commons app. Jim.henderson (talk) 09:20, 4 October 2018 (UTC)
Jim.henderson, does the app itself demonstrate that the picture completed uploading? If you go to "Home", the main screen should contain a list of all the images you uploaded, including failed uploads (which would say "failed" under the upload). What does yours show? Trying with the different procedure that you mentioned (taking a picture first, and then uploading) would be helpful also, to help us isolate the problem. Lastly, a few people who have not relogged since our last authentication change (a few months ago) have experienced issues with failed uploads and found that logging out and in again solved the issue for them. Thanks for your patience! Misaochan (talk) 16:00, 4 October 2018 (UTC)
My use of the app has also slowed, as I've had trouble uploading images from my phone lately. I'll re-download the app soon and try again. -Another Believer (talk) 15:22, 4 October 2018 (UTC)
Another Believer, please let us know how it goes for you. :) Misaochan (talk) 16:12, 4 October 2018 (UTC)
Having a busy day, but next on my schedule is a bike ride to a restaurant 12 km away and I'll start early so as to snap a few. No, there is no sign of my uploads either in the app or elsewhere. Oops! Last week I forgot my password and recovered the account by E-mail, and I'm pretty sure the Commons app continued oblivious. I was also oblivious, at least for that app. I'll log out and in with the new password.
Done. Now it shows the pictures that failed to upload yesterday. I tried uploading one, and got the word "Queued" between the pic and its name. It's been that way for 27 minutes, so clearly it ain't working. About an hour from now I'll snap another and give it a try. Jim.henderson (talk) 13:14, 5 October 2018 (UTC)
Jim.henderson Ah, I see, thanks! Yes, the "Queued" bug is one that we are currently working on, unfortunately we have yet to be able to figure out how to solve it. :( I will add your comments to the issue that we are using to track it. Could you please (1) Try uploading via Gallery instead of directly from Camera, and (2) Re-check your Android version? I know you mentioned Android 6.1 to us earlier, but the Nexus 6P has been on 8.1 for a while now. Sorry to bother you but this will help us hugely. Thanks! Misaochan (talk) 09:38, 6 October 2018 (UTC)
Quick reply; tomorrow won't be so busy. I indeed tried from Photos, and failed. Alas, I don't remember the details and must repeat. Yes, Android 8.1 is what I've got. Don't recall whether that was a misreading or a typo, but anyway my error. More tomorrow. Jim.henderson (talk) 22:37, 6 October 2018 (UTC)
This afternoon, all went well. Every method I tried, the picture arrived. Start with Commons, bring up Camera to snap it. Worked. Start with Commons, bring up Photos to upload. Worked. Start with Camera, bring up Commons. Worked. Start with Photos, bring up Commons. Worked. Using the Open Camera app, I failed once and didn't have time for more experimenting. OC will be the focus of my next test session. Jim.henderson (talk) 22:39, 8 October 2018 (UTC)
Hey Jim.henderson, happy to hear that! :) We've actually just released v2.8.5 to beta, which is aimed at trying to eliminate the occasional upload failures for some people. If you have the time, could you please register for beta testing and let us know how it works for you? Thanks! Misaochan (talk) 13:03, 11 October 2018 (UTC)

Wish list[edit]

So, the darn thing works now. I walked and biked in Columbus today. Most my pictures were with the big camera and won't arrive quickly. On the Android phone, the Beta app worked, finding a target by the map, making it call Open Camera, uploading. Main difficulty was seeing my screen when Sun was bright; only different hardware would help that.

So, what still bugs me? Biggest nuisance in the map is that it keeps resizing the screen so the pins are all in a little round cluster in the center. Default size should be to make the cluster fill the screen, side to side, and maybe a little more, losing a few off the edges so the high and low parts of the screen are mostly filled. And if I zoom in on something off center, it should stay there instead of drifting to show me the center. I assume that's connected to the idea of showing me, as the word says, what's "nearby".

Much smaller nit, when I tap on a pin, a flag comes up with a name, and a footer shows that name and buttons for actions. Tapping the flag does nothing; must remember to tap the footer. Somewhat more important, if there's no ENWP article when I tap the W symbol, it should pop to say "Ain't got nuffin" or more cultured equivalent instead of pretending not to hear me.

On a grand scale, I was busy hopping back and forth between Google Maps, bike station search map, bike station unlock map, Wikipedia map, and Commons map. Of course the Wiki-empire can do nothing about the first three, but sure would be nice to have all Wikithings consolidated in one map with different symbols for Data, Pedia, Commons cat, Commons pic, and let me turn off the ones I don't want and concentrate on what's important to me at that moment. Like I do by adjusting Google Maps layers with train stations, bike routes and traffic congestion. Then it should let me tap into each page by its symbol to get the info I want. That, I assume, is far out of scope this year, next year, and indefinitely. But if I meet map people tomorrow at WMNA hackathon, that's one thing I'll bitch for, after voicing my gratitude for lovely things already done. Jim.henderson (talk) 23:58, 17 October 2018 (UTC)

Hi Jim.henderson, thanks for the in-depth list of suggestions! We do plan on revamping the map display in the very near future, with a "search this area" UI. This should indirectly fix your problem as well, as the pins displayed in the area would fill the screen and the zoom should not drift.
The flag is a relic of our old system, we are likely getting rid of it in the future and focusing solely on the footer. Do you prefer the flag, or is the confusion just caused by having both of them around?
The WP icon should actually be greyed out if no WP article exists, does it not do that for you?
Cheers! ;) Misaochan (talk) 09:09, 30 October 2018 (UTC)

Since then, I've learned about WikiShootMe. More about that in a later paragraph.

Kill the flag, or make it more active, all the same for me. You're right, the inactive WP icon is grey. However, surrounded by white, it is not pale enough for me to notice the difference easily. Better make a dead link red as done inside WP articles, or with an X through it, or some other really blatant cue.

Last night at dusk I was early for a date, so strolled along Broadway (a target-rich environment) with the Android in my hand. I had the WikiShootMe site open in the browser, turning off the layer for WD places that already had a photo. Couple years ago I used that site but it only worked well at home; not on my phone of the time. Someone kindly reminded me of it after I complained about the Commons App map. WSM's multilayer feature is a great help; pretty much what I asked for previously. I can pocket the phone, or switch among apps, and come back to see the map looking the same, instead of outzoomed to see a vast area with a little cluster of indicators in the middle.

The WSM site also has an upload feature, which is cruder than the Commons App. It doesn't allow changing the filename or adding categories, far as I could see. I decided the best of both worlds was to walk and pick targets with the WSM site, and switch to Commons App to handle the picture work. Naturally it would be less clumsy if these powers were unified, but so far this seems the most efficient way.

The major remaining annoyance has more to do with Wikidata. Often WD has a link to the ENWP article, even though the Commons app does not. Sometimes that article has a picture, but WD does not, hence both the WSM page and the Commons app fail to show that the object has been photographed. I haven't tried to figure whether that's only a matter of inadequate data about these objects, or some deeper problem in connecting the various Wiki-items that try to cover them.

As it happens, the majority of unphotographed WD sites in this neighborhood are theaters that haven't existed for decades. That wastes a certain amount of my time, but it could only be repaired by noting the demolition in WD and giving the mobile mapper an option of ignoring the demolished ones. I shan't get my hopes up for that. Jim.henderson (talk) 14:41, 30 October 2018 (UTC)

Jim.henderson, I understand the frustration re: zooming. I will let you know when we have completed our revamp of the map UI. ;) Best, Misaochan (talk) 07:47, 7 November 2018 (UTC)
A lot of interesting insight in these posts, thanks! About demolished buildings we have this issue waiting for a generous developer: https://github.com/commons-app/apps-android-commons/issues/618 . About items that have a picture on Wikipedia but not Wikidata: Before my trips I use this tool to fix the problem: https://meta.wikimedia.org/wiki/WDFIST#Tip:_Items_around_you Syced (talk) 09:48, 7 November 2018 (UTC)
Hi Jim.henderson, just a brief update: we have found out a way to solve the zoom issue, and the fix should be ready with our v2.9 release next week. I will let you know when the release is in beta. :) Misaochan (talk) 09:45, 22 November 2018 (UTC)
Jim.henderson, v2.9 was just released for beta testing. Hope the new default zoom level works better for you. :) Misaochan (talk) 16:57, 27 November 2018 (UTC)

Very good. Minutes before you entered that, I turned off the computer, put my meal on the fire, turned on the phone, and found and downloaded the new version. Then ate quickly and spent busy hours running errands. Chores done, I opened the app. Oops! The map isn't under the menu button; it's up front. Good. Yes, the map opens nicely, with the screen showing almost all the pins. Exactly right; if it showed all the sites in a given radius, it would also show blank spaces. Another good one, when I zoom in or out, it stays where I put it. Of course, the map is still only for nearby objects, which wasn't very informative since I was already back home, but a choice of viewed location will be a new feature one day, not the fix of an old bug.

One annoyance; the map took a long time to load through my slow DSL. Like, a quarter minute. I don't recall such slowness with the old version, but it could be my elderly memory fading. Anyway, it's good to see you're working on the app. Jim.henderson (talk) 01:36, 28 November 2018 (UTC)

Jim.henderson, great to hear that. ;) Re: searching other locations, we are actually actively working on it now (see discussion here) - the feature should be rolling out with v2.10 in a month or so. :) Re: map loading, we haven't changed the query itself recently, so it is unlikely to have gotten slower, but we should certainly look into ways to make it faster in the future.
We have also just submitted a PG proposal with our plans for 2019, would love to hear your thoughts on it as a regular user of our app.
Thanks,
Misaochan (talk) 14:19, 29 November 2018 (UTC)

Incorrect dates reported as of 2.8.6?[edit]

Consider File:Ratatat light show at Pomona Fox Theater April 15 2015.jpg. I uploaded it with Commons App for Android 2.8.6; note that in the original upload, the 'according to EXIF' source date was the upload date, not the date actually specified in the EXIF, as shown in the 'Metadata' section on the file page. This also happened in 2.8.5 (see File:Dasyprocta leporina at Buffalo Zoo.jpg), but not 2.7.2 (see File:San Jose Fire Department crane truck, rear corner view.jpg); I don't have examples of uploads made with versions in between. This seems like a pretty big potential annoyance (though the true EXIF dates are still discoverable; nothing's really lost). Is there anywhere else I should be reporting this? grendel|khan 06:27, 21 November 2018 (UTC)

Hi Grendelkhan, same for example here File:Calgary Folk Festival.jpg. Could you please report this as a bug on https://github.com/commons-app/apps-android-commons/issues. --Arnd (talk) 07:16, 21 November 2018 (UTC)
Ah, it's already been reported; it's issue 1854 on the tracker, and should be fixed in 2.9. (Though maybe there should be a bot run to correct all of the wrong metadata?) This has been known since August, which is a bit disappointing; I'm not sure when 2.9 is supposed to come out. grendel|khan 14:35, 21 November 2018 (UTC)
Hi guys, sorry about that. 2.9 is slated for release to beta early next week. We are still working on solving a few other niggling issues with that release, and we didn't want to rush it and release with those bugs. Time has been very tight for us recently, as we are only a small community team of part-time devs, and we are also running hard into other deadlines at the same time.
Thanks for your understanding. I will ping you as soon as 2.9 is out. :) Misaochan (talk) 09:43, 22 November 2018 (UTC)
I could run my bot to change the misleading date if you like. But what i need to know for it is which files must be considered. --Arnd (talk) 10:12, 22 November 2018 (UTC)
Thanks Arnd. As far as I am aware based on user reports, this would affect files uploaded in version 2.8 (so 2.8.0, 2.8.1, etc). Misaochan (talk) 10:36, 22 November 2018 (UTC)
Thanks Misaochan. I would prepare and test such a bot run the next time. But i will start later after the new release is out. Do you have any idea how long it approximately takes until most users updated their apps? --Arnd (talk) 10:52, 22 November 2018 (UTC)
Hmm, we would usually leave a major release in beta for a couple of weeks, and then promote to production if there are no serious issues with the beta testing. After that, most non-beta-testing users take another couple of weeks to update their apps usually (although some never do... I still see uploads from users using v1.x of the app, lol. Such is Android development....). I guess it might be best to start the bot at the end of Dec? I can ping you once we have promoted to production, and the bot can be run 2 weeks after that probably. Misaochan (talk) 12:48, 22 November 2018 (UTC)
Ok Misaochan. I think i will need to update the files based on this search. I will check if the Exif date fits to what is used in the Exif date template. If not, i will update it. But what to do if there is no Exif date available? What does the app in this case? --Arnd (talk) 13:37, 22 November 2018 (UTC)
Thanks, the search looks good to me. I will need to double-check this, but I believe we use the upload date if there is no date in Exif. Misaochan (talk) 14:53, 22 November 2018 (UTC)
Hi Grendelkhan and Arnd, we just released v2.9 for beta testing. Could you please give it a test and see if the date is fixed for you? Thanks. Misaochan (talk) 16:58, 27 November 2018 (UTC)
Looks good to me! (See File:UP 1096 crossing Hamilton Avenue in Campbell.jpg.) Thanks for looking into this. Could the app use a more thorough test suite, do you think? I understand that this is a lot of work for a small dev team--thank you for the quick response, and for taking care of this. grendel|khan 17:37, 3 December 2018 (UTC)
Thanks Grendelkhan, happy to hear it works for you now. :) We do actually have plans to implement a more thorough test suite next year! We've submitted a proposal for it here, would greatly appreciate your feedback. Misaochan (talk) 11:36, 4 December 2018 (UTC)

Commons Android app PG proposal[edit]

Hi folks,

We're applying for a Project Grant to fund the development of v3.0 of the Commons Android app. At the moment, we're approaching completion of our 2nd Individual Engagement Grant, having implemented several major new features, e.g. a revamped map of "nearby places that need photos" with direct uploads and Wikidata integration, user talk notifications, browsing of other Commons pictures with focus on featured images, and 2FA logins. We currently have 4000+ active installs, and 15,000+ distinct images uploaded via our app have been used in Wikimedia articles. In the last 6 months alone, 21,241 files were uploaded via our app, and only 1738 (8.2%) of those files required deletion. We are also proud to report that we have a vibrant, diverse community of volunteers on our GitHub repository, and that we have increased our global user coverage since our first grant.

It has been a rocky road this year, however. One of the major issues we faced was that a large portion of our codebase is based on sparsely-documented legacy code from the very first incarnation of the app 5 years ago (a long time in the Android development world), leading to unpredictable behavior and bugs. We eventually found ourselves in a position where new features built on top of legacy code were causing other features to not work correctly, and even fixes to those problems sometimes had side effects that caused other problems. (My sincerest apologies to users for the inconveniences that they were caused!)

In view of that, our Project Grant proposal focuses on these areas:

  • Increasing app stability and code quality: We plan to overhaul our legacy backend to adhere to modern best practices, reduce complexity and dependencies in our codebase, and introduce test-driven development for the first time.
  • Targeted acquisition of photos for places that need them: The "Nearby places that need photos" feature has come a long way, but there is still plenty of room for improvement. We plan to introduce new quality-of-life features (e.g. by implementing filters and bookmarks) and fix a few outstanding bugs to make it more user-friendly and convenient to use. We will also complete the final link in the chain of collecting photos for Wikipedia articles that lack them by prompting users to add their recently-uploaded photo to the relevant Wikipedia article.
  • Increasing user acquisition in the Global South: We plan to implement a "limited connectivity" mode, allow pausing and resuming of uploads, and put more time and effort into outreach and socializing the app, especially to underrepresented communities.
  • We also wish to continue to assist the Commons community to reduce vandalism and improve usability of images uploaded. This will be done by implementing selfie detection, and a "to-do" system that reminds users if an image lacks a description/categories.

Your feedback is important to us! Please do take a look, and feel free to let us know what you think on the Discussion page, and/or endorse the proposal if you see fit. If you would like to be part of the project, new volunteers and additions to our diverse team are always welcome - please visit our GitHub repository and say "Hi". :)

Finally, we want to thank everyone who has cheered us on and supported us throughout the years. As a community-maintained app, we wouldn't be here without you.

Misaochan (talk) 18:00, 28 November 2018 (UTC)

Allow multiple files to be uploaded[edit]

Right now I don't commonly use the Wikimedia Commons app from Google Play because I could only use it to upload 1 (one) image at a time, this is despite the advantages that this app has over the browser (though a ton of disadvantages such as an inability to edit and/or categories existing files). The Wikimedia Commons app should allow its users to upload the same amount of files as the MediaWiki Upload Wizard allows or 50 (fifty). --Donald Trung 『徵國單』 (No Fake News 💬) (WikiProject Numismatics 💴) (Articles 📚) 17:50, 29 November 2018 (UTC)

v2.9 beta allows multiple uploads. You can sign up for beta testing here (though bear in mind that beta versions tend to have more bugs than production). It should be out in production in a few weeks' time. Categorizing existing files is one of the improvements proposed in the PG proposal. ;) Misaochan (talk) 17:57, 29 November 2018 (UTC)

What is this sentence talking about?[edit]

"Please note that the selfie-pocalypse frequently mentioned in association with mobile uploads was solely caused by the mobile web interface (now deprecated)." Deprecated? Y'all mean this interface? Because that's the standard upload form that I use and only recently (earlier this year) did the MediaWiki Upload Wizard support the mobile web interface. So which mobile web interface is this sentence talking about? --Donald Trung 『徵國單』 (No Fake News 💬) (WikiProject Numismatics 💴) (Articles 📚) 17:54, 29 November 2018 (UTC)

AFAIK it was referring to the Mobile Media Uploads interface (also see this). We should probably make this clearer, Syced? Misaochan (talk) 18:03, 29 November 2018 (UTC)
@Donald Trung, Misaochan: mw:Wikimedia mobile engineering/Mobile QA/Commons uploads has some relevant info. They said: "We want to encourage users to contribute pictures to Wikipedia pages missing images. We do this by showing a big upload button in those pages." I believe this was a major cause of the influx of the inexperienced uploads in 2013. (I didn't experience it first-hand, so that's only my understanding from existing documents and comments I saw, though.) --whym (talk) 14:58, 1 December 2018 (UTC)

Imply "|Permission" in Summary[edit]

Misaochan, try to put one more line, since i often use :

|Permission=

Right-pointing hand in green octagon.svg You can use this picture according to license. For use outside of Wikipedia I would appreciate it if you let me know by sending e-mail to petarmslo@gmail.com Nuvola apps email.png Thank you in advance.

It look like this. --Mile (talk) 12:42, 18 January 2019 (UTC)

Apps option[edit]

I noticed that wiki its not offering the 2 options that are usually available for downloading apps on ur mobile device (app store for iphone and google play for android) Only showed google play and "F-droid" which its the first time in my life seen such a thing... besides my previous knowledge I heard about windows play or whatever Microsoft store offered. I will appreciate accurate facts and feedback on this topic please. Sincerely Vinicio Viquez aka Gaymalegender on wiki Gaymalegender (talk) 16:11, 2 April 2019 (UTC)

@Gaymalegender: The app is only available for android, not for iOS/iphone. F-droid is an alternative for people with android devices who want to install apps without creating a Google account. Hope that helps? --El Grafo (talk) 13:12, 3 April 2019 (UTC)

Apple App?[edit]

Is something like this app also available or planned for Apple devices like iPhones? --Neitram (talk) 14:58, 25 April 2019 (UTC)

There was an iOS port available, but currently there nobody maintaining/developing it. The source code is available at github, so if you are interested in picking it up: go for it ;-P --El Grafo (talk) 08:05, 26 April 2019 (UTC)
Thanks! I wonder why the WMF with all their money is not paying some developer to develop and maintain this app? --Neitram (talk) 06:54, 30 April 2019 (UTC)
Because if they would, people would be complaining about how they are wasting donor money on closed eco systems for a toy or some weird shit argument like that. —TheDJ (talkcontribs) 08:19, 30 July 2019 (UTC)
Hello Neitram, this is actually quite a popular request, so much so that I've been considering applying for a Project Grant in the next round for the development of an iOS app (this is also how the Android app is currently funded, by the way, we are not officially "WMF staff"). The main issue as far as I can tell is that the existing iOS port is very old and does not comply to modern iOS development practices (for one thing, it's in Objective-C...). So it would probably be better to create one from scratch rather than trying to reuse legacy code. I have no iOS dev experience unfortunately, but we could search for collaborators that do. If we do apply for funding for the iOS app, would you like me to ping you when the proposal is up? Misaochan (talk) 12:10, 9 June 2019 (UTC)
@Misaochan: Thanks for your reply. Sure, please ping me when the proposal is up. --Neitram (talk) 06:28, 14 June 2019 (UTC)

Thank you for improvements[edit]

I have been uploading images since 2013 using the Android Commons app and the Commons mobile app. To say that there have been frustrations is an understatement. Many crashes, many unexplained failures to upload, many uninstall/reinstall efforts and many cases of giving up trying to upload a useful photo. Despite this, I have managed to upload quite a few decent photos over the years, interspersed with months of not really bothering to try. But in recent weeks, I have had universally good results with the latest version. No crashes, rapid uploads and the app is suggesting actually relevant categories and it is easier to search for other categories. In my opinion, the current version is vastly better than all previous versions, and I sure hope that nobody screws it up. Thanks. Cullen328 (talk) 00:40, 14 May 2019 (UTC)

Thank you for your feedback, Cullen328, glad to see that the recent version works for you! We will try our best not to screw things up. ;) Misaochan (talk) 12:05, 9 June 2019 (UTC)
Gah, I had my hopes up after reading your message, but my attempts to add images still fail. I used to love using this app, but I've mostly given up at this point, unfortunately. -Another Believer (talk) 14:08, 14 May 2019 (UTC)
Another Believer, sorry to hear that. We're aware that there are still a few people experiencing issues with the latest version. The reason this is taking so long to fix is described in greater detail here, but the short version of it is that we are building on legacy code that is causing a lot of unexpected, difficult-to-debug issues. We have been playing patchwork with this for some time (which has fixed a lot of issues, albeit not all), but at the end of the day the inevitable solution is to overhaul the codebase to a more modern version, with better software development practices and stricter code quality measures. This does take a lot of time, and will also involve some teething issues, but it is the best long-term solution for everyone involved. We are halfway through the overhaul now, would you like me to ping you when we are done? Misaochan (talk) 12:05, 9 June 2019 (UTC)
@Misaochan: Yes, please! -Another Believer (talk) 15:16, 9 June 2019 (UTC)
@Another Believer: Will do. Apologies for the inconvenience in the meantime. Misaochan (talk) 15:38, 9 June 2019 (UTC)
@Misaochan:, please let me know when you are done as well. Cullen328 (talk) 17:13, 9 June 2019 (UTC)
@Cullen328: Sure thing! :) Misaochan (talk) 07:51, 10 June 2019 (UTC)
Hi Another Believer and Cullen328, just an update: We have just released the first of two planned releases in our code overhaul project (v2.11), which should now be available to download from the Play Store for all beta testers. This may not completely fix the failed uploads issue, but I just wanted to let you know so that you are kept up to date. If you experience any issues with v2.11, please do let us know so that we can fix it ASAP (the good news is that the further we get with the overhaul, the easier debugging and fixing issues gets for us). I'll ping you again when v2.12 is out, which should contain the completely revamped authentication flow that would address the failed uploads. Best, Misaochan (talk) 14:22, 29 July 2019 (UTC)
@Misaochan: Thanks for the update. I just tried to upload a photo from my phone using my wifi at home, but the upload failed. :( I'll try again after the next update. -Another Believer (talk) 18:59, 30 July 2019 (UTC)