Currently, a user can't access the watchlist out of the app. This should be fixed so users can save and revisit a page they saved on another device.
Please see the mobile apps page for the hackathon for more details in general in case you're interested in working this at the hackathon.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Add watchlist functionality. | apps/android/wikipedia | master | +452 -2 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T91510 Hackathon-able / volunteer-worthy tasks for Mobile Apps | |||
| Resolved | Dbrant | T76953 Add watchlist to app | |||
| Invalid | None | T253129 Android watchlists v1 - Menu item + list | |||
| Resolved | cooltey | T253130 [SPIKE] Android watchlist v2 - Search in list | |||
| Open | Feature | None | T271563 Feature Request: Text selection on change log |
Change 166274 had a related patch set uploaded (by Florianschmidtwelzow):
Add watchlist functionality.
Change 166274 abandoned by Deskana:
Add watchlist functionality.
Reason:
It's going to take a lot of work to get this to the stage where it's really a useful product. Abandoning for now.
The above patch got this to the state where it could fetch the most recent changes from a user's watchlist and display it as a list of pages to the user. The main problem is that the app doesn't have any kind of diff viewing framework, so it would just dump the user onto the page in question.
That's the major bit of outstanding work here; either a diff-viewing framework needs to be made from scratch, or an open source library found that provides that functionality.
There was also some under the hood and technical work remaining to be done. First the patch needs to be unabandoned and rebased. Then we should make the WatchlistFragment implement an onSaveInstanceState method that writes out the state to a bundle. That way, if the activity is paused or stopped by the OS, it could be resumed sensibly from the savedInstanceState bundle without having to actually restart the activity from scratch and double the network requests. This would also increase the user consistency, since the user wouldn't randomly get different results just because they minimised the app and opened it again.
No answer, so I assume no work was done on this task during the hackathon. If this is wrong, please update accordingly.
I am willing to take this up in the upcoming hackathon (provided I get through the scholarship grant :) ).
It'd be great if you could provide me some pointers to how to get started on this, so that I have enough context before the event starts.
I see that a changeset is already here but has been abaondoned. Is it in a ready-to-patch state?
Hey @yashasvi! I've not been involved with the mobile apps for a few years now, so you should probably ask @Charlotte and @Dbrant for their input.
In terms of the code that I wrote three years ago, I highly doubt it's useful any more since the app will have changed a lot in those years. Starting from scratch would probably better. :-)