Grants:Project/Commons app/Commons app Android and iOS

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


statusunder review
Commons app Android and iOS
summaryDevelop and release Commons iOS app and improve Commons Android app, to increase and broaden participation in Commons.
targetWikimedia Commons (primarily); geolocated Wikidata items and Wikipedia articles lacking images
amount96,400 USD
contact• josephinelim86(_AT_)gmail.com• nicolas.raoul@gmail.com
volunteerMaskaravivekDomdomeggKaartic
organization• Commons app (group)
this project needs...
volunteer
join
endorse
created on10:05, 10 February 2020 (UTC)


Project idea[edit]

What is the problem you're trying to solve?[edit]

What problem are you trying to solve by doing this project? This problem should be small enough that you expect it to be completely or mostly resolved by the end of this project. Remember to review the tutorial for tips on how to answer this question.

The Wikimedia Commons Android app, an open-source project maintained by grantees and volunteers since 2015, allows users to easily upload photos to Commons from their Android mobile device. As of today (11 Feb 2020), we have 6,131 active installs, a total of 23,599 distinct images (17.14% of all images) uploaded via our app have been used in Wikimedia articles, and 1,398 places that need photos have had photos added to them via the app. At the moment, we are halfway through a Project Grant for stabilizing and improving the Android app, which we expect to complete by June 2020.

The most common request (by far!) that we have received from Wikimedians, both online and at in-person events, has been for an iOS app. This makes a lot of sense - while Android does have a bigger market share worldwide[1], there is still a very large number of iOS users, with more than 1.5 billion active devices as of Jan 2020[2]. Due to this, most apps that intend to reach a significant mobile user base (e.g. Wikipedia app, Kiwix) will target both Android and iOS. The lack of a Commons iOS app prevents a large chunk of current (and potential) Commons contributors from having the convenience of uploading from their mobile device.

Active installs for Android app over the last year
Map of p18 edits made

What is your solution to this problem?[edit]

For the problem you identified in the previous section, briefly describe your how you would like to address this problem. We recognize that there are many ways to solve a problem. We’d like to understand why you chose this particular solution, and why you think it is worth pursuing. Remember to review the tutorial for tips on how to answer this question.

We plan to develop and release a Commons iOS app that will allow iOS users to upload photos to Commons directly from their mobile device. The iOS app will also include most of the popular and commonly-used features from our Android app - category suggestions based on coordinates and title, a map of nearby places that need photos (with the option to upload a photo to one of them), in-app user talk notifications, upload statistics/achievements, and basic structured data integration.

We also intend to continue supporting our Android users by further polishing and stabilizing the Android app, as well as developing a couple of new features for it based on user requests and findings from a study re: increasing and broadening participation in Commons. In the final phase of the grant, we plan to start publicity initiatives to increase awareness of Commons in the general public and to let people know that anyone with a mobile device can now contribute easily to Commons.

Project goals[edit]

What are your goals for this project? Your goals should describe the top two or three benefits that will come out of your project. These should be benefits to the Wikimedia projects or Wikimedia communities. They should not be benefits to you individually. Remember to review the tutorial for tips on how to answer this question.

  • Wikimedia Commons iOS app available for download on the Apple App Store, with stable upload functionality, popular features from the Android app, and adhering to modern iOS code standards and design principles.
  • Continuing to increase the number of Commons contributors and useful images uploaded to Commons, including for places that lack them, by improving and publicizing both the iOS and Android app.

Project impact[edit]

How will you know if you have met your goals?[edit]

For each of your goals, we’d like you to answer the following questions:

  1. During your project, what will you do to achieve this goal? (These are your outputs.)
  2. Once your project is over, how will it continue to positively impact the Wikimedia community or projects? (These are your outcomes.)

For each of your answers, think about how you will capture this information. Will you capture it with a survey? With a story? Will you measure it with a number? Remember, if you plan to measure a number, you will need to set a numeric target in your proposal (i.e. 45 people, 10 articles, 100 scanned documents). Remember to review the tutorial for tips on how to answer this question.

For the iOS app:

  • iOS app implemented in Swift, code available in open source repository.
  • Deliverables available for download on Apple App Store.
  • 50% code coverage (the percentage of code which is covered by automated tests). This metric is a predictor of app stability in future releases, as failing tests provide early warning of issues with new code. It will be measured after completion of the grant via Codecov reports.
  • Crash rate of <0.5%. This metric is an indicator of app stability, and will be measured via data obtained from the Apple developer account 2 weeks after the final version is released to production.
  • >500 installations on devices that were active in last 30 days. This metric will be obtained from the Apple developer account at the end of the grant, roughly 6 months after estimated release of the first minimum viable product. (Note: This number is significantly smaller than our Android number, as we have found that the first installs are the hardest to get. For instance, the Android app took more than 6 months after it was released by the community to get its first 200 active installs. However, as we have more connections and resources for publicity this time around, we are setting our targets higher than that - my estimate would be 500-1000 installs, with 500 being the more conservative end of the range.)

For the Android app:

  • All tasks completed, final deliverable available for download on Google Play and F-Droid.
  • 50% code coverage. This will be measured after completion of the grant via Codecov reports. (Projected code coverage by June based on current PG goals: 25%)
  • Crash rate of <0.5%. This will be measured via data obtained from the Google Play developer console 2 weeks after the final version is released to production. (Projected crash rate by June based on current PG goals: <1.0%)
  • Open bug issues on GitHub reduced by 50% from the start of the grant.
  • >10,000 active installs. This metric will be obtained from the Google Play developer console at the end of the grant. (Currently: 6131)

Do you have any goals around participation or content?[edit]

Are any of your goals related to increasing participation within the Wikimedia movement, or increasing/improving the content on Wikimedia projects? If so, we ask that you look through these three metrics, and include any that are relevant to your project. Please set a numeric target against the metrics, if applicable.

These goals include uploads from both the Android and iOS apps, which will be tallied at the end of the grant.

  • >3000 new contributors who were introduced to Commons via the app. This metric refers to the number of app users whose first upload to Commons was via the app, during the grant period, and is measured by a query similar to this. (Number from previous IEG grant: 1728)
  • A total of >40,000 distinct images uploaded via the app are used in Wikimedia articles. This metric defines not just the number, but also the usability of images uploaded via mobile app, and will be measured via a GLAMorous query. (Currently: 23599)
  • >80,000 new images uploaded to Commons via the app throughout the grant duration, while maintaining a deletion rate of <10%. Both of these numbers will be measured via analysis of data from the Commons app stats tool at the end of the grant. (Number of images uploaded to Commons using our app from Nov 2017 to Aug 2019: 57,446)
  • A total of >2500 places that need photos will have photos added to them via the app. This will be measured at the end of the grant by querying the number of unique P18 edits made in Wikidata by our app (an edit is made automatically to the corresponding Wikidata entity whenever anyone uploads an image via the Nearby feature). (Total number of unique P18 edits as of 11 Feb 2020: 1398)

Project plan[edit]

Activities[edit]

Tell us how you'll carry out your project. What will you and other organizers spend your time doing? What will you have done at the end of your project? How will you follow-up with people that are involved with your project?

What will you and other organizers spend your time doing?[edit]

For both the iOS and Android apps, we will be spending our time on:

  • Design and development of the planned features
  • Testing - both manual testing and writing of unit tests
  • Publishing releases on Apple App Store (iOS) and Google Play Store/F-Droid (Android)
  • Communicating with users on a regular basis to obtain feedback and bug reports
  • Fixing any issues with releases
  • Supporting and fostering volunteer code contributors
  • Outreach and socializing project

iOS app[edit]

Considerations[edit]
  • Native vs cross-platform. After discussion with Joshua Minor from the WMF iOS team, we concluded that creating a native iOS app (with Swift) would be a better use of resources than creating a cross-platform app. We had initially created a (very basic) prototype of the app using the Flutter (cross-platform) stack, which we then sent to the team for discussion. Our findings were that: (1) from the user experience and design perspective, the Flutter stack and available built-in components will be a limiting factor, preventing it from fitting with the Wikipedia app or Apple's user interface guidelines. (2) The quality of the cross-platform app, in terms of responsiveness, would be inferior to that of a native iOS app. (3) There were concerns about stability and future maintenance, as cross-platform frameworks are all third party and may undergo changes or be abandoned in the next few years. Therefore, we are going with native.
  • Starting anew instead of using legacy app. We are aware that there is an existing open-source repository for the Commons iOS app - however, (aside from readme.md pull requests submitted by Nicolas Raoul from our team) it was last updated in 2016 and is written in Objective-C. Based on our experience with developing the Android app, building on legacy code is likely to cost far more development time than it saves, especially if many new features are planned, and also Apple has moved away from Objective-C; Swift is the current recommended language for iOS development. Additionally, the Android app has changed a lot from the legacy app, and most of the "staple" features that our current users have come to expect (e.g. category suggestions, the entire Nearby feature, etc), do not actually exist in the legacy app.
  • Design. Our aim is to provide a user experience for our iOS users that is as close as possible to that of our Android users, while taking into consideration iOS design principles. For this purpose, we will consult with Carolyn Li-Madeo (our advisor from the WMF iOS team) throughout our design and development process.
  • Code. The app will be developed in Swift based on the best practices described in Apple's developer documentation, and all of the code for the app will be publicly available on GitHub under the open source Apache License 2.0.
  • Choice of features to implement. For this proposal, we have selected the most commonly-used and popular features from the Android app to implement in the iOS app, in order to make the best use of resources. Just like the Android app, the codebase for the iOS app will be fully open-source and community maintained, so volunteers can submit pull requests for any additional features that they are interested in implementing, and if they fit our project and code quality requirements we will accept them.
Phase 1 - Minimum viable product with upload functionality and ability to view own uploads[edit]
First step of upload process in Android app

Deliverables:

  • v1.0 of app released to Apple App Store. The first app release will focus on our core functionality: uploading. Users should be able to have the same experience for uploading photos on iOS as they have on Android (category suggestions, multilingual descriptions, etc), and the resulting file created on Commons should contain the same information as files that are uploaded with Android. Debugging facilities are also implemented to enable us to fix any issues that users may experience. A tutorial, warnings, checks, and tooltips are all included to avert any potential selfie-pocalypses from the start.
  • Minor publicity phase after v1.0 release: Write article for Wikimedia blog about the new iOS Commons app (if editor allows), announcements on mailing lists, Village Pump, social media, etc. This will help us get our first beta testers and start the user feedback loop.

Detailed breakdown of tasks:

Authentication:

  • Login page (with signup option)
  • Logout option in-app

Tutorial prior to login:

  • Reused from Android app, displayed on fresh install

Main screen:

  • User can view their previous contributions and currently-uploading file (if any)
  • Floating action button for uploads
  • Gallery
  • Camera
  • Share from stock gallery

Upload process:

  • Same steps as Android (v2.12.2) and same options at each step - users can fill in title, multilingual descriptions, select categories, and select license
  • Tooltips at each step to guide new users
  • Handle multiple uploads
  • After user submits upload, they can view loading progress bar in Contributions and be notified by a snackbar on completion

Category suggestions:

  • If no text entered in search field, display: Recent categories, GPS categories, Title-based categories
  • If text entered in search field, search API for that text

Checks:

  • Prevent overwrite of filename, add numbered suffix to end of filename if already exists
  • If file with same hash already exists, prevent user from uploading
  • Warning if user submits upload with no categories selected

Send appropriate data to Commons when creating file:

  • EXIF data
  • Uploader
  • Date picture taken
  • Categories
  • Tag for “Uploaded by Mobile/iOS [version]”

Media details view:

  • Users can tap on their previous contributions and view media details, e.g. title, description, license, coordinates, categories, upload date

Debugging facilities:

  • Feedback option
  • Send logs option

Phase 2 - Add "nearby places that need photos", 2FA logins, and notifications[edit]
Nearby feature in Android app

Deliverable: v1.1 of app released to Apple App Store. This version will contain our most popular feature - a map of places that need photos. Users will be able to upload photos directly for places on this map, with the associated category suggestions and Wikidata p18 edits, similar to the Android app. Other conveniences like 2FA logins and viewing user talk notifications in-app are also added.

Detailed breakdown of tasks:

Nearby places that need photos:

  • Same as Android (v2.11) without filters
  • Map and list of places that need photos
  • Ability to "search this area" when user moves the map
  • Selecting a pin opens up bottom sheet
  • FAB for gallery and camera uploads

Direct uploads from Nearby:

  • Title and description pre-filled
  • Categories suggested from Wikidata
  • Adds image to p18 of Wikidata item

2FA logins working

Notifications:

  • View user talk notifications in-app
  • Tapping notification brings user to talk page with that notification

About page added:

  • App version
  • Link to repository, website, social media pages, etc
  • Disclaimer

Settings page added

Main screen setup completed:

  • Contributions tab and Nearby tab in Home page
  • User talk notifications visible via bell icon
  • Navigation Component added for Home, About, Tutorial, Feedback, Settings and Logout
  • Username displayed in navigation component
Phase 3 - Add Achievements and basic Structured Data integration[edit]
Achievements feature in Android app

Deliverable: v1.2 of app released to Apple App Store. This version will contain basic Structured Data integration, allowing users to add multilingual captions and "depicts" statements for their uploads. Users can also view their upload statistics in Achievements.

Detailed breakdown of tasks:

Structured Data integration:

  • Option to add multilingual captions after selecting file to upload
  • In next step, users can search for and add "depicts" statements
  • Tooltips to explain all of the above to new users

Achievements:

  • Level - calculated based on images uploaded, deletion %, and images used in articles
  • Statistics - all the above stats, plus images uploaded via Nearby, featured images, and thanks received
  • "Share" option for users to share a screenshot of their Achievements with friends

Android app[edit]

We intend to continue supporting the Android app by polishing it, further reducing bugs and crashes, and increasing code coverage. We also have a new feature for power users, and a couple of new features aimed at encouraging a diverse range of people to upload (usable) photos to Commons.

New feature for power users[edit]
  • More powerful pin filtering of "nearby places that need photos" map via allowing users to modify SPARQL query (#3410). There is a limit to the number and type of user-interface filters that we can offer in the Nearby map - if we offer too many, it will be difficult for newer users to adjust or to find what they need. On the other hand, power users may have specific requirements that are not covered by the filters we already offer. This feature was requested by power users who would like more control over customization of their Nearby map, and are familiar with SPARQL.
New features to increase diversity and encourage more people to upload (usable) photos to Commons[edit]

For this goal, we draw from findings in the study “Sharing small pieces of the world: Increasing and broadening participation in Wikimedia Commons" by A. Menking et al. (Full disclosure: I (Josephine) was emailed by the authors early in the study, but only to provide technical details - I had no influence in the design of their study or the results obtained). The authors ran a survey about a hypothetical mobile game for uploading to Commons called "Scavenger Hunt". Some of their notable findings were:

"Considering our quantitative and qualitative data in tandem, we suggest a game-based approach to facilitating contributions in Commons may provide a novel means of increasing participation as well as broadening the demographics of those contributors. Wikipedia [37] has reported 53% of contributors are less than 30 years old and only 16% identify as women. Similarly, Viégas [29] reported the respondents to her survey about the demographics of Commons contributors were on average aged 33.6 and were 100% male (N=29). Conversely, 77% of our participants were under 31 years old, 50.5% self-identified as women, and fully 74% of respondents indicated they would be interested in contributing to a system like Commons after being exposed to Scavenger Hunt."

"First, the two most common codes identified in our data across all respondents were the “desire for social and/or community interactions” and the “desire to make impact and/or contribute” (e.g., be useful). Characteristics common among observations coded thusly included the desire to be a part of either a local or a virtual community, to have a tangible connection between one’s own efforts and another’s needs, and to be responsible—either solely or in part—for the making of something meaningful."

While creating a whole new mobile game would be beyond the scope of this grant, these findings have inspired us to head further in the "light gamification" direction with the existing Android app.

  • Show Commons pictures on map of "nearby places that need photos" (#28). We currently already retrieve all geolocated Wikidata items and display them on the Nearby map - users can choose to toggle items that already have p18 images on or off, but even if toggled on they are only displayed as pins, and in order to view the actual image, the user must investigate further. With this feature, users who choose to toggle it on can view these items as small thumbnails instead of just pins. This feature will be disabled if the user chooses to enable "limited connection mode" (a feature that we are implementing very soon as part of our current grant), so as not to waste bandwidth. After a user makes a direct upload through Nearby, they will then be able to see their own photo as one of these thumbnails, in the spot that they uploaded to.
  • Allow users to view other users' profiles (achievements) (#3389). We already have an Achievements page in the app, where the user can view their own upload statistics (pictures uploaded, deletion %, images used in articles, etc). We now plan to allow users to view other people's achievement/profile pages, for instance when they are browsing pictures in Explore and tap on an author's name, or when they tap a name in the Leaderboard feature (that is planned for this year's GSoC/Outreachy). They would also be able to view a gallery of that user's uploads (perhaps through a WebView). This could later be further gamified with profile badges, or other forms of profile enhancements.

Community engagement[edit]

How will you let others in your community know about your project? Why are you targeting a specific audience? How will you engage the community you’re aiming to serve at various points during your project? Community input and participation helps make projects successful.

Throughout the grant, we will continue our usual user feedback cycle, and will engage with users and volunteer contributors on an ongoing basis through these media:

  • GitHub - Our source code is publicly available on GitHub, and anyone is welcomed to fork and contribute to our repository - the Android repo currently has 556 stars and 768 forks. Also, most of our new features/improvements and details of their implementation are discussed publicly on GitHub.
  • Mailing lists and village pump - After major releases, I will usually post on the wikitech-l, mobile-l, and commons-l mailing lists, as well as on the Commons village pump.
  • On-wiki discussion page - We engage regularly with users who have questions or problems with the app in our on-wiki discussion page.
  • Google groups forum - We have a "feedback" option in-app that sends an email to our Google group forum, this is the most convenient options for new and casual users to contact us.
  • Social media - We have a Facebook page which is regularly updated.
  • Hangouts - Volunteers receive news about beta releases and help with getting started in our Hangouts group, an invite can be requested here.
  • Blog - Screenshots and details of major releases are posted here.
  • Mentorship - We mentored GSoC/Outreachy students for 2018 and 2019, and plans are ongoing to mentor another student this year. Our 2018 and 2019 students have remained fairly active in the community, with two of them mentoring GCI this year.
  • In-person meetups to foster our volunteer developer community - our app was represented in every Wikimedia hackathon since 2017, where we often mentor newcomers to these events.

Additionally, at the end of the grant, we plan to undertake several outreach and publicity measures. Along with gamification improvements (mentioned under Android: New Features), these tasks are aimed at increasing public interest and awareness of the app.

  • Organize a “Nearby places that need photos” walk (#3388). An event like this might sound more fun and attractive to new contributors than an official "workshop" on contributing to Commons. It would be an outdoor exercise where a leader would guide participants on a walk through the city, point out interesting landmarks, and show them how to take photos of places on Nearby and upload them. With the iOS app released, we would not need to limit the participants to Android users, anyone with a mobile device would be able to participate. We will not need additional resources for this other than time, as it can be advertised online, there is no need to pay for a venue, and a grantee (or volunteers if anyone wants to) can hold it locally. (Note: This will be held at the end of the grant, so definitely after the September 15 2020 cutoff.)
  • Organize a competition for Nearby contributions (#2428). We plan to experiment with organizing a virtual competition for Nearby contributions, and iterate/improve on it in the future if successful. For instance, the winner could be the person who has the most valid (non-reverted) p18 edits from the Commons app on a particular week. Rewards would be non-financial - perhaps barnstars or other types of profile enhancements and a mention in our website/blog.
  • Write blog posts for the Wikimedia blog, if approved by the blog team.
  • Contact blogs and tech-related online magazines to ask if they would be interested in writing about the app. We tried this once a long time ago, in my very first IEG in 2017, and failed - the authors/editors were not interested. The main reason, as I noted in my final report, was that the effort was premature - we were barely known in the Wikimedia community at that time, so it made a lot more sense to focus our effort on promoting awareness of the app within the communities instead of trying to engage the general public. We have focused more on community efforts ever since. But now the community is (for the most part) aware of us, the app looks a lot better and has a lot of new features, and we will soon have both iOS and Android apps. I believe it is time for us to try again.

Budget[edit]

How you will use the funds you are requesting? List bullet points for each expense. (You can create a table later if needed.) Don’t forget to include a total amount, and update this amount in the Probox at the top of your page too!

The total amount requested is 96,400 USD for 12 months, to pay grantee and contractor salaries.

Grantee Role Job description Commitment Person-weeks Rates Cost
Josephine
  • Project & product manager (iOS & Android)
  • Android developer
  • Responsible for the entire project, product quality, and meeting grant reporting requirements
  • Managing app releases, communicating with users, integrating user feedback into products
  • Organizing & coordinating development of products and publicity initiatives
  • Android development
30 hrs/week 46 weeks 30 USD/hr 41,400 USD
Neslihan
  • Android developer
  • Android repository maintainer
  • Android development
  • Managing Android code repository - testing and reviewing pull requests, organizing issues, supporting volunteer contributors
20 hrs/week 50 weeks 20 USD/hr 20,000 USD
Ashish
  • iOS developer
  • iOS repository maintainer
  • iOS development
  • Managing iOS code repository - testing and reviewing pull requests, organizing issues, supporting volunteer contributors
20 hrs/week 50 weeks 20 USD/hr 20,000 USD
(Contractor)[1]
  • iOS developer
  • iOS development
15 hrs/week 50 weeks 20 USD/hr 15,000 USD
Total 96,400 USD

[1] The contractor position will be advertised if/when the grant is approved. We have connections with a substantial community of developers via our participation in open-source initiatives, so we are reasonably confident that we will be able to find a suitable person.

Get involved[edit]

Participants[edit]

Please use this section to tell us more about who is working on this project. For each member of the team, please describe any project-related skills, experience, or other background you have that might help contribute to making this idea a success.

Grantees[edit]

  • Josephine Lim - project lead (User: Misaochan, GitHub: misaochan). I have been the project lead/maintainer of the Commons app since September 2016, and have worked on the app as an Android developer since October 2015 (when it had 20 active users!).
  • Neslihan Turan (User: Flanoz, GitHub: neslihanturan). Neslihan has been with our team as an Android developer and repository maintainer since 2017. She has participated in several hackathons representing our app, and was a GSoC mentor for our app.
  • Ashish Kumar (User: Ashishkumar468, GitHub: ashishkumar468). Ashish has been with our team as an Android developer since 2018, and was a GSoC mentor for our app last year. He has also developed other mobile applications, and was one of the developers who made the cross-platform prototype of the app.

Advisors[edit]

Community[edit]
  • Nicolas Raoul (User: Syced, GitHub: nicolas-raoul). Nicolas has been a Wikimedia contributor since 2005 and was the previous project maintainer of the Commons app.
  • Vojtěch Dostál (User: Vojtěch_Dostál). Vojtěch is a member of the board of Wikimedia Czech Republic, a Wikidata enthusiast, and an avid user of the Commons app.
  • Stéphane Coillet-Matillon (User: The other Kiwix guy). Stéphane is the CEO of Kiwix and a regular user of the Commons app.
WMF[edit]
  • Dmitry Brant (User: DBrant_(WMF) , GitHub: dbrant). Dmitry is a software engineer on the Wikipedia Android app team and a collaborator of the Commons app.
  • Carolyn Li-Madeo (User: CMadeo (WMF)). Carolyn is the senior UX designer of the Wikipedia iOS app.

Volunteers[edit]

Sign up here if you like :)

  • Volunteer Android developer and repository maintainer Domdomegg (talk) 20:12, 18 February 2020 (UTC)
  • Volunteer I have been part of the Wikimedia Commons app team for the past 3 years. Would love to continue contributing to the project as a volunteer. Maskaravivek (talk) 09:30, 25 February 2020 (UTC)
  • Volunteer I would love to help the app in all the ways I am capable of. Some ways that come to the top of my head:
  1. Noting and reporting any bugs
  2. Providing feedback about design ideas, changes
  3. etc.
-- Kaartic correct me, if i'm wrong 19:05, 26 February 2020 (UTC)

Community notification[edit]

You are responsible for notifying relevant communities of your proposal, so that they can help you! Depending on your project, notification may be most appropriate on a Village Pump, talk page, mailing list, etc.--> Please paste links below to where relevant communities have been notified of your proposal, and to any other relevant community discussions. Need notification tips?

Endorsements[edit]

Do you think this project should be selected for a Project Grant? Please add your name and rationale for endorsing this project below! (Other constructive feedback is welcome on the discussion page).

  • As always, this is an excellent proposal by Josephine and her team and should be selected for funding. A growing number of app users is the best evidence of their success. "When will you make it for iOS" is really the most frequent question the team is getting. Vojtěch Dostál (talk) 19:18, 18 February 2020 (UTC)
  • Would love to see the Commons mobile apps improve! Domdomegg (talk) 20:11, 18 February 2020 (UTC)
  • It should be noted that besides working on grant tasks, Josephine and her team have always also taken responsibility for fixing legacy bugs, adapting the app to server-side changes, and helped WMF with mentoring (Google Code-in, Google Summer of Code, Outreachy), welcomed new volunteers, answered questions on the forum and Google Play, for free. Syced (talk) 06:45, 19 February 2020 (UTC)
  • Will be nice to see Commons Apps come to iOS RhinosF1 (talk) 14:46, 19 February 2020 (UTC)
  • I am excited to see this proposal! As an iPhone user, I would use a Commons app every day to take photo of buildings, nature, and landmarks. Right now, I take photos on my phone, email them to myself, download them to my desktop, and upload them to Commons. With an app, I think this process would be so much faster, that I would upload many more photos. -- Cloud atlas (talk) 15:20, 19 February 2020 (UTC)
  • I highly endorse this project. I am an iPhone user myself and as a long-time Wikipedian have missed an app like this for years. Neitram (talk) 15:39, 19 February 2020 (UTC)
  • I am starving to wait for iOS app coming. In Japan, there are a lot of Wikipedia Town events, which consists of photowalk and editathon. iOS commons app is useful for participants to upload photos to be included in subject article(s) of editathon part. And the market share of iPhone among smartphones is significant (nearly 60%) in Japan. That's why I am awaiting iOS app to come. --Takot (talk) 15:42, 19 February 2020 (UTC)
  • iOS app! I highly endorse this! iPhone users are wikipedians too. --Frettie (talk) 19:17, 19 February 2020 (UTC)
  • Would be perfect! The best camera is the one you have with you. And the iPhone can nearly keep up with my canon in some situations... Indeedous (talk) 20:59, 19 February 2020 (UTC)
  • Support Support This is a very welcome proposal! The absence of a commons app for iOS has really been a big hindrance to contribution. I'm glad it's finally on the table :).--Jamie Tubers (talk) 16:11, 23 February 2020 (UTC)
  • So excited to see this proposal! After seeing how the Android version of the Commons app has significantly added value to the Wikimedia Commons project, I can only imagine what the iOS version will bring. Also, having worked with/observed all the three grant writers more closely as they have mentored several times in the Wikimedia outreach programs and Hackathons, I am positive that they will bring this project to fruition. SSethi (WMF) (talk) 01:21, 25 February 2020 (UTC)
  • Excited for the iOS app. Maskaravivek (talk) 09:31, 25 February 2020 (UTC)
  • It is a great app supporting documentation of the world around us using Wikidata. Czeva (talk) 16:51, 26 February 2020 (UTC)
  • Symbol strong support vote.svg Strong support I totally support this proposal. I strongly believe the iOS would be a great thing to achieve during this proposal period. Personally, I'm a huge admirer of the quality of the images taken using the iPhone's camera and I could only imagine how the introduction of the iOS app would help the users to easily upload their wonderful images to Wikimedia Commons, the free media repository. I would love to see the impact that the iOS app is going to have.
Also, I would love to see all the features planned for the iOS app implemented within the grant period. I hope that should be possible given a person who has the appropriate iOS development experience. Kaartic correct me, if i'm wrong 17:52, 26 February 2020 (UTC)
  • I have had a great experience using the Commons Android app and would be thrilled to see a similar iOS app. I take most of photos using my cellphone's camera and the ability up upload directly from my phone to Wikimedia Commons has resulted in me contributing more. The development team is incredibly hardworking, welcoming, and fosters a good community. Mds08011 (talk) 22:49, 27 February 2020 (UTC)
  • An iOS app is very exciting, and will reach a whole new audience. As an Android user myself, I'm also glad to see the commitment to further support and development of the Android app. The plans for the grant look very well thought out, and with clear metrics for success. the wub "?!" 23:24, 29 February 2020 (UTC)
  • Support Support, this open source project is run well, by trusted Wikimedians. Not a user of the app myself but porting it sounds pretty sensible. − Pintoch (talk) 13:25, 5 March 2020 (UTC)
  • Support Support Anthere (talk)
  • Support Support --Anonymous Apple Addict (talk to AAA) 13:04, 13 March 2020 (UTC)
  • This will greatly improve workflow for Commons contributors using iOS devices, and should lead to more content and new contributors. Lack of this app has restricted our outreach activities related to photo shoots Pru.mitchell (talk) 00:58, 15 March 2020 (UTC)

References[edit]