Mobile-l

mobile-l@lists.wikimedia.org

4 participants
6884 discussions

Uber Clone Script - Build Your Taxi App in the USA
by CameronStewartt24＠gmail.com 26 Nov '24

26 Nov '24

TeamForSure offers an easy way to create your taxi app with our Uber Clone Script. It is simple, affordable, and includes features like live tracking, driver management, and secure payments. Perfect for startups or growing taxi businesses, this script helps you launch your app quickly without spending too much. Build a taxi app that is reliable, user-friendly, and fits your business needs. Start now with TeamForSure and grow your taxi service in the USA. Visit More Info: https://www.teamforsure.com/uber-clone

1 0

New mobile app start
by Test 19 Nov '24

19 Nov '24

Hi All I'd like to write an Android app for my wiki. To start with, log me in. Opt in: show notifications from the Echo. Then opt in: show notifications from recent changes (it is tiny wiki, so not too many). Could you please guide me? Some hello world example would be great. I previously asked on wiki and was told that infrastructure for push notifications is missing, but nobody told me how to set it up. This would be my first Android app. I am "gry" on IRC. Thanks!

2 2

Commons app - v5.1 beta release and removal of limited connection mode
by Kaartic Sivaraam 11 Nov '24

11 Nov '24

Hello all, Hope you have been well! We have just released v5.1.0 of the Commons Android app to production. The update is now available on Play store (beta track) [1] and F-droid [2]. You could also build the app directly from our GitHub repository [3]. This release includes the improved upload queue that was specified in the previous release post. This was contributed by Kanahia during Google Summer of Code 2024[4]! He was mentored by Nicolas and Ritika. The new upload queue system ensures smoother, sequential processing and better progress tracking. It also provides more flexibility with managing your whole upload queue by allowing to pause / resume / cancel all ongoing uploads. With this enhancement, we have retired the "Limited Connection Mode". However, the new upload queue's pause provides flexibility similar to the old mode. We would love to hear any thoughts / concerns about this change. Other significant changes: - Fixed an UI issue where the 'Subcategories' and 'Parent Categories' tabs appeared blank in the Category Details screen. Resolved by optimizing view binding handling in the parent fragments. - Added an option in "Nearby" feature enabling users to provide feedback on Wikidata items. Users can report if an item doesn’t exist, is at a different location, or has other issues, with submissions tagged for easy tracking and updates. - Improved the "Nearby" feature by splitting the query into two parts for faster loading and better performance, especially in areas with dense amount of places. This update also resolves issues with pins overlapping place names. - Upgraded AGP and target/compile SDK to 34 and make necessary adjustments to the app such as adding "Partial Access" support. - Fixed an issue where editing depictions removed all other structured data from images. Now, only depictions are updated, preserving other associated data. - Fixed map centering in the image upload flow to use GPS EXIF tag location from pictures and ensured "Show in map app" accurately reflects this location. - Fixed navigation after uploading via Nearby by directing users to the Uploads activity instead of returning to Nearby, preventing confusion about needing to upload again. These are only a small chunk of all the changes that were part of this release. Checkout our release notes [3] for a more detailed set of changes since the last announcement. As always, feel free to reach our to us with your valuable feedback. You could share feedback in our talk page [5] / by writing an e-mail to commons-app-android(a)googlegroups.com / via our issue tracker [6]. [ References ]] [1]: https://play.google.com/store/apps/details?id=fr.free.nrw.commons [2]: https://f-droid.org/en/packages/fr.free.nrw.commons [3]: https://github.com/commons-app/apps-android-commons/releases/tag/v5.1.0 [4]: https://phabricator.wikimedia.org/T360265 [5]: https://commons.wikimedia.org/wiki/Commons_talk:Mobile_app [6]: https://github.com/commons-app/apps-android-commons/issues Best regards, Sivaraam (User:Kaartic)

1 0

Introducing Edit Patrol in the Wikipedia Android App
by Amal Ramadan 29 May '24

29 May '24

Hello all, The Mobile Apps team has recently released a new feature in the Android app to assist rollbackers in patrolling from their mobile device without leaving the Android app. Edit Patrol is a suggested edit that allows users with rollback rights to view the recent changes feed, with access to undo, rollback, thank, and post talk page messages. You can learn more about the feature and its development on our project page <https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Android/Anti_Vandalism#>. Throughout development, we have continued to incorporate feedback from members of the community. We prioritized collaboration with communities that have traditionally had difficulty utilizing existing tools, specifically editors using mobile devices. After initial release, we heard requests to add access to user talk warning templates in the talk page message flow. Users are now able to search and use user talk warning templates as part of the tool. For languages that do not have user warning templates, the team reviewed messages across languages and created 10 example messages <https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Android/Anti_Vandalism/S…> that will be preloaded into the app. The feature is currently available to users with rollback rights based on the feedback we heard during development. However, if specific wikis are interested in making this tool more widely available on their wiki, it can be changed on a per-wiki basis. Please reach out on the discussion page <https://www.mediawiki.org/wiki/Talk:Wikimedia_Apps/Team/Android/Anti_Vandal…> . Please check out this presentation <https://commons.wikimedia.org/wiki/File:Edit_Patrol_Presentation_%26_Demo.p…> with more information, and a demonstration <https://upload.wikimedia.org/wikipedia/commons/f/f8/Edit_Patrol_Demo_-_Upda…> of the feature to learn more. If you have any questions or feedback, we welcome it on the project’s discussion page <https://www.mediawiki.org/wiki/Talk:Wikimedia_Apps/Team/Android/Anti_Vandal…>. Respectfully, *Amal Ramadan* (She\Her) Sr. Community Relations Specialist Wikimedia Foundation <https://wikimediafoundation.org/>

1 0

Re: [Commons-l] Re: Commons app - v5.0 release
by Kaartic Sivaraam 14 May '24

14 May '24

Hi Gnangarra, On 13/05/24 10:45, Gnangarra wrote: > From some who uses the app regularly, has big thumbs, and needs reading > glasses I'll appreciate the voice input feature, now it just has to > recognise my Australian accent 🤣 this should be interesting, and I'll > apologize early on for any slips of the tongue. > Good to hear that you would find the voice input feature helpful. As to the australian accent being recognized, we just piggy back on the speech-to-text services that are available in your device. If you already use any speech-to-text service that recognizes your accent well, the same should work fine for app's voice input feature too. If you notice any discrepancy, feel free to let us know :-) > Thank you and everyone thats working on it. > Thank you for the kind words! -- Sivaraam

1 0

Commons app - v5.0 release
by Kaartic Sivaraam 13 May '24

13 May '24

Hi all, Hope you have been well! We have just released v5.0.1 of the Commons Android app to production. The update is now available on Play store [1] and F-droid [2]. You could also build the app directly from our GitHub repository [3]. If you've faced issues with your profile not working / contribution information not being shown appropriately, sorry about that! We've fixed that in this version :-) We've had yet another revamp of the Maps screens in this version. We replaced Mapbox altogether with the osmdroid library. Key elements like pin visualization and user-centered display are still included in this redesign. We did this to guard against possible misuse of the Mapbox token and, more crucially, to keep the app from becoming dependent on a service that charges for usage but offers a free tier. As a consequence, you may observe the Nearby and other Map screens not being as snappy as they used to. We've noticed this and are actively discussing on ways to improve the same[4]. Feel free to chime in with your thoughts. Talking about improvements to the app, this year Kanahia will be contributing to the app during Google Summer of Code 2024! His project will focus on improving upload queue management [5]. He will be mentored by Nicolas and Ritika. Other significant changes: - Add the ability to export locations of nearby missing pictures in GPX and KML formats. This allows you to browse the locations with desired radius for offline use in your favourite map apps like OsmAnd or Maps.ME - Added a compass arrow in the Nearby banner shown in the "Contributions" screen to guide you towards the nearest item, thus providing the missing directional cues. The arrow dynamically adjusts based on device rotation, aligning with the calculated bearing towards the target location. Further, the distance and direction are updated as you move. - Implemented voice input feature for caption and description fields, enabling you to dictate text directly into these fields. - Improved various flows in the app to redirect you to the login page and display a persistent message if your session becomes invalid due to a password change. - Revamped initial upload screen layout and the description edit screen layout for enhanced user experience and ensuring better symmetry in the design. These are only a small chunk of all the changes that were part of this release. Checkout our release notes [3] for a more detailed set of changes since the last announcement. As always, feel free to reach our to us with your valuable feedback. You could share feedback in our talk page [6] / by writing an e-mail to commons-app-android(a)googlegroups.com / via our issue tracker [7]. [[ References ]] [1]: https://play.google.com/store/apps/details?id=fr.free.nrw.commons (staged rollout has been initiated. It should be available in few days) [2]: https://f-droid.org/en/packages/fr.free.nrw.commons [3]: https://github.com/commons-app/apps-android-commons/releases/tag/v5.0.0 [4]: https://github.com/commons-app/apps-android-commons/issues/5529 [5]: https://phabricator.wikimedia.org/T360265 [6]: https://commons.wikimedia.org/wiki/Commons_talk:Mobile_app [7]: https://github.com/commons-app/apps-android-commons/issues Best regards, Sivaraam (User:Kaartic)

1 0

Commons app - v4.2 release
by Kaartic Sivaraam 07 Nov '23

07 Nov '23

Hi all, Hope you have been well! We have just released v4.2 of the Commons Android app to production. The update is now available on Play store [1] and F-droid [2]. You could also build the app directly from our GitHub repository [3]. An important thing we wanted to communicate. We've changed the Mapbox API key used by the app in this release (v4.2.1) due to some unforeseen circumstances. We also had to revoke the old API key that is being used by the older version of the app (< v4.2.1). You might face issues with accessing maps in those versions of the app such as the Nearby screen appearing blank etc. We request your to kindly upgrade to v4.2.1 in order to continue using the features for which rendering a map is necessary. Other features should work fine. We regret the inconvenience that this may cause. Feel free to open an issue in our issue tracker [4] for any assistance. We'll be glad to help. This release also includes the done by Ritika Pahwa during GSoC 2023. This includes changes done to improve the reliability of the failed, stuck uploads and changes to prevent location metadata loss for uploads done via in the app. In case you've been facing issues with the uploads, do give the latest version a try. It should be better than before. Feel free to reach out to us with any feedback you may have. It would be very helpful. Other significant changes: - Dark mode colour improvements - Uploading via the in-app camera has been fixed and should work normally. - Provide the ability to edit an image to losslessly rotate it while uploading. - Category search now shows exact matches without any discrepancies - We've switched to using MapLibre instead of Mapbox and thereby disabled telemetry sent to Mapbox. We're also actively exploring alternatives to Mapbox so that we could completely move away from it. Check out the related issue [5] for information regarding the same. - Fix some redundant crash issues Checkout our changelog [6] for a more detailed set of changes since the last announcement. [[ References ]] [1]: https://play.google.com/store/apps/details?id=fr.free.nrw.commons [2]: https://f-droid.org/en/packages/fr.free.nrw.commons [3]: https://github.com/commons-app/apps-android-commons/releases/tag/v4.2.1 [4]: https://github.com/commons-app/apps-android-commons/issues [5]: https://github.com/commons-app/apps-android-commons/issues/5352 [6]: https://github.com/commons-app/apps-android-commons/blob/main/CHANGELOG.md Best regards, Sivaraam (User:Kaartic)

1 0

Wikipedia's app newsletter!
by Amal Ramadan 31 Mar '23

31 Mar '23

Hello all, Wikipedia's apps now have a newsletter; subscribe <https://meta.wikimedia.org/wiki/Wikimedia_Apps/Newsletter> for the updated roadmap, and office hours and conferences will be attended! Respectfully, *Amal Ramadan* (She\Her) Sr. Community Relations Specialist Wikimedia Foundation <https://wikimediafoundation.org/>

1 0

Wikimania 2023: Mobile showcase? Submit your ideas!
by bustrias＠gmail.com 25 Mar '23

25 Mar '23

Hi Folks, We encourage each and everyone of you to create a program submission. You can submit an interactive workshop or panel, a lecture, a short lighting talk or a poster for our dedicated poster session. Submissions are catered to both onsite and online (live or pre-recorded) or a hybrid combination. We at the Core Organizing Team would like to see a program submission related to projects related to mobile devices. The theme for this year's Wikimania is Diversity, Collaboration, Future. Topics that strengthen collaboration especially future-thinking topics like Wikimedia products and services on mobile devices are topics we like to see this year. Session submissions for Wikimania 2023 are open until 28 March. Visit the following links for further info: Wiki page: https://wikimania.wikimedia.org/wiki/2023:Program/Submissions Diff post: https://diff.wikimedia.org/2023/02/28/be-part-of-the-wikimania-2023-program/ Program Submission Form: https://pretalx.com/wm2023/cfp Kind regards, Butch Bustria Chair, Program Subcommittee Event lead, ESEAP Wikimania 2023 Core Organizing Team

2 1

Cross Post to mobile-l: Service Decommission Notice: Mobile Content Service - July 2023
by Adam Baso 22 Mar '23

22 Mar '23

---------- Forwarded message --------- From: Adam Baso <abaso(a)wikimedia.org> Date: Wed, Mar 22, 2023 at 4:45 AM Subject: Service Decommission Notice: Mobile Content Service - July 2023 To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> TL;DR: The legacy Mobile Content Service is going away in July 2023. Please switch to Parsoid or another API before then to ensure service continuity. Hello World, I'm writing about a service decommission we hope to complete mid-July 2023. The service to be decommissioned is the legacy Mobile Content Service ("MCS"), which is maintained by the Wikimedia Foundation's Content Transform Team. We will be marking this service as deprecated soon. We hope that with this notice, people will have ample time to update their systems for use of other endpoints such as Parsoid [1] (n.b., MCS uses Parsoid HTML). The MCS endpoints are the ones with the relative URL path pattern /page/mobile-sections* on the Wikipedias. For examples of the URLs see the "Mobile" section on the online Swagger (OpenAPI) specification documentation with matching URLs here: https://en.wikipedia.org/api/rest_v1/#/Mobile == History == The Mobile Content Service ("MCS") is the historical aggregate service that originally provided support for the article reading experience on the Wikipedia for Android native app, as well as some other experiences. We have noticed that there are other users of the service. We are not able to determine all of the users, as it's hard to tell with confidence from the web logs. The Wikimedia Foundation had already transitioned the Wikipedia for Android and iOS apps to the newer Page Content Service ("PCS") several years ago. PCS has some similarities with MCS in terms of its mobility focus, but it also has different request-response signatures in practice. PCS, as with MCS, is intended to primarily satisfy Wikimedia Foundation-maintained user experiences only, and so this is classified with the "unstable" moniker. == Looking ahead == Generally, as noted in the lead, we recommend that folks who use MCS (or PCS, for that matter) switch over to Parsoid for accessing Wikipedia article content programmatically for the most predictable service. The HTML produced by Parsoid has a versioned specification [2] and because Parsoid is accessed regularly by a number of components across the globe tends to have fairly well cached responses. However, please note that Parsoid may be subject to stricter rate limits that can apply under certain traffic patterns. At this point, I do also want to note that in order to keep up with contemporary HTML standards, particularly those favoring accessibility and machine readability enhancements, Parsoid HTML will undergo change as we further converge parsing stacks [3]. Generally, you should expect iteration on the Parsoid HTML spec, and of course as you may have come to appreciate that the shape of HTML in practice can vary nontrivially wiki-by-wiki as practices across wikis vary. You may also want to consider Wikimedia Enterprise API options, which range from no cost to higher volume access paid options. https://meta.wikimedia.org/wiki/Wikimedia_Enterprise#Access == Forking okay, but not recommended == Because MCS acts as a service aggregate and makes multiple backend API calls, caveats can apply for those subresources - possibility of API changes, deprecation, and the like. We do not recommend a plain fork of MCS code because of the subresource fetch behavior. This said, of course you are welcome to fork in a way compatible with MCS's license. == Help spread the word == Although we are aware of the top two remaining consumers of MCS, we also are not sure who else is accessing MCS and anticipate that some downstream tech may break when MCS is turned off. As we are cross-posting this message, we hope most people who have come to rely upon MCS will see this message. Please feel free to forward this message to contacts if you know they are using MCS. == Help == Although we intend to decommission MCS in July 2023, we would like to share resources if you need some help. We plan to hold office hours in case you would like to meet with us to discuss this or other Content Transform Team matters. We will host these events on Google Meet. We will provide notice of these office hours on the wikitech-l mailing list in the coming weeks and months. Additionally, if you would like to discuss your MCS transition plans, please visit the Content Transform Team talk page: https://www.mediawiki.org/wiki/Talk:Content_Transform_Team Finally, some Content Transform Team members will also be at the Wikimedia Hackathon [4] if you would like some in-person support. Thank you. Adam Baso (he/him/his/Adam), on behalf of the Content Transform Team Director of Engineering Wikimedia Foundation [1] https://www.mediawiki.org/wiki/Parsoid [2] https://www.mediawiki.org/wiki/Specs/HTML [3] https://www.mediawiki.org/wiki/Parsoid/Parser_Unification/Updates [4] https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2023

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Mobile-l