To help people from clicking on Load more a bunch as they're going down the list, let's use infinite scroll, and load more cases as the user is scrolling down.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T116957 Plagiarism detection tools for text (tracking) | |||
| Resolved | • TBolliger | T120435 Improve the plagiarism detection bot | |||
| Resolved | • TBolliger | T131583 Epic: Make a tool labs interface for Plagiabot aka Eranbot | |||
| Declined | None | T137986 Use infinite scroll on Copy Patrol |
Event Timeline
Comment Actions
Do we still want to do this? We've cut our load time in half, but doubling the number of records is going to slow it down that much more.
I think adding an infinite scroll would be a better option. Coupled with the filters, users should have a seamless experience of going through the list. For a dedicated reviewer, it will take some time to get through the first 50, and by the time they're reviewing items within the 40s, the next chunk of 50 items will have already loaded and be rendered into view.
If they just want to get to the end of the backlog, we should consider an option to reverse the order.
Comment Actions
As I remember, in one of our earlier meetings we discussed infinite scrolling but decided against it. I don't remember all of the points raised but one of them was that it'll hog bandwidth without people's explicit acknowledgement. This might seem like nothing on good internet connections but on 30Kbps, it might be a problem.
Comment Actions
A block of 50 records is about 22KB in size, which is quite small. Users of the tool are going to need to open up the Wikipedia interface and revert the edit, etc, so I doubt data usage is much of a concern. Internet speed isn't much of an issue because the data will download in the background
Comment Actions
Yeah, I thought we decided to use a "Load more" button instead of infinite scrolling, although I don't remember exactly why.
Comment Actions
My concern is that infinite scroll doesn't actually seem worthy of all the development time and effort it needs. Especially now when we don't know how much usage this tool is going to get. It's easy to get carried away adding niceties to the tool to improve user experience, but it's important to know if that is actually what is really wanted by the users. When people start using the tool, they will come up with ideas that we probably didn't think of at the moment. Just my 2 cents.
Comment Actions
No problem here with side-stepping this. I just figured it was a better solution over showing a 100 records. I was also thinking infinite scroll would prevent us from showing a footer, should we ever want to add one.