Profile Information

Name: Lawal Abiola
Email: Mshdabiola@gmail.com
Education: University of Ilorin, Kwara state
Github : mshdabiola
LinkedIn : mshdabiola
Location: Lagos, Nigeria
Typical working hours: 8 am - 9 pm (WAT) UTC+1

Synopsis

• The Wikimedia Commons Android app allows users to contribute photos directly from their phones, but the upload experience needs an upgrade. This GSOC project aims to revamp the upload queue management system and modernize the app's overall look and feel.

• Mentors - @RitikaPahwa4444 @Nicolas_Raoul

Have you contacted your mentors already?

Yes

Implementation Strategy

Improve upload queue management

{F44022202}

Database Table for Upload Queue:

• Add a new table specifically designed to cache the upload queue.
• Schema: Employ the schema of the image for this table.

{F44022236}

Upload Screen Design:

• Create a new screen for users to initiate and manage image uploads.
• View: This screen will primarily display a clear and informative view of the upload process.

Image Upload Process:

1. Initiation:
   • When a user selects an image for upload, it's immediately added to the "image database table."
   • A unique identifier (ID) is generated and assigned to the image to ensure tracking and consistency.
   • This ID is then used as a reference for the UniqueWorker, a component responsible for managing the upload task.

2. Progress Management:
   • The UniqueWorker continuously updates the upload progress within dedicated database fields.
   • These updates are reflected on a visually clear progress bar, providing real-time feedback to the user.

3. Cancellation:
   • If the user clicks the "cancel" button, the following actions occur:
     • The image is swiftly removed from the image database table.
     • The image ID is utilized to effectively cancel the upload task within the WorkManager, a system designed to manage background tasks.

4. Error Handling:
   • In the event of an error during the upload process:
     • The table is updated to reflect the error status.
     • A "Retry" button is prominently displayed on the UI, conveniently enabling the user to resume the upload process.

5. Retry Mechanism:
   • Upon clicking the "Retry" button, the UniqueWorker is triggered to restart the upload process from the point of interruption.

6. Successful Upload:
   • If the upload completes successfully:
     • The worker meticulously removes the image from the upload queue table.
     • Relevant image data is seamlessly added to the "contributor table" to facilitate future image display and retrieval.

Nearby: Load pins as the user moves the screen, cache pins

1. Location Caching:
   • Implement a mechanism to store user location data within a dedicated database table. This cached data will optimize future map interactions.

2. Map Interaction and Boundary Detection:
   • When the map becomes visible to the user:
     • Upon zooming or scrolling actions on the map, capture the current bounding box. The bounding box represents the visible area on the map, defined by latitude and longitude coordinates.

3. Cached Data Retrieval:
   • Leverage the captured bounding box to query the location cache database. This query will retrieve any relevant location data stored within the boundaries of the current map view.

4. Data Visualization:
   • Display the retrieved location data as pin markers on the map. These pins will visually represent the cached locations within the user's current view.

Sure!
Here's the markdown table with the description column summarized to 5 sentences:

Previous Contributions to Commons

About Me

Lawal Abiola leveraged his Electrical and Electronic Engineering background from the University of Ilorin to develop a strong passion for coding. For the past 6 years, he has honed his skills in Android development, becoming proficient in utilizing Firebase, Git, UI development, and Retrofit. I am also broadened his experience with Ktor for server-side development, HTML and Javascript for web development, and even design tools like Adobe Illustrator and Adobe XD.

Relevant Skills

• I bring expertise in managing development workflows with Github Actions and Git version control.
• My skillset includes Android development using the Android SDK and designing user interfaces for Android apps.
• I have a grasp of RxJava, Dagger2, and the AndroidX libraries for efficient Android development.
• I'm comfortable working with networking libraries like Retrofit and OkHttp for data communication.
• I prioritize code quality through unit testing practices for Android applications.
• While my primary focus is Android, I also have familiarity with the Kotlin programming language.
• In addition to Android, I possess a working knowledge of Python programming.
• I understand how to interact with RESTful APIs using Python, including those provided by Wikimedia.
• I have a foundational understanding of the Wikimedia API functionalities.

Availability

Are you eligible for Google Summer of Code?

Yes.

Do you have any other plans during the period of GSoC?

No, I do not have any other plans during the contribution period.

How many hours per week can you dedicate to this?

45 hours

Have you been accepted to GSoC before?

No. I am applying in GSoC for the first time.

After GSoC

My commitment to Wikimedia extends beyond GSoC. I'm eager to help with issue resolution, idea generation, and code collaboration to make a positive difference.