Migrate watch history to Jetpack Compose

[Isira-Seneviratne]

What is it?

• Bugfix (user facing)
• Feature (user facing)
• Codebase improvement (dev facing)
• Meta improvement to the project (dev facing)

Description of the changes in your PR

• Rewrite the watch history UI using Jetpack Compose. As part of this change, the ItemList composable was refactored to use separate data classes, in order to further decouple it from the information provided by the extractor and make it more easily reusable.
• Clean up unused methods in StreamHistoryDAO.
• Reimplement the watch history retrieval from the Room database using AndroidX Paging for improved efficiency, as it supports pagination.
• Add stream card and grid composables.
• Update several relevant dependencies, including the Compose BOM version.
• Use loading indicator for placeholder items in ItemList.

Before/After Screenshots/Screen Record

Before	After

Screen_recording_20250311_110112.mp4

Fixes the following issue(s)

• Fixes #

APK testing

The APK can be found by going to the "Checks" tab below the title. On the left pane, click on "CI", scroll down to "artifacts" and click "app" to download the zip file which contains the debug APK of this PR. You can find more info and a video demonstration on this wiki page.

Due diligence

• I read the contribution guidelines.

[asandikci]

There should be a confirmation screen after "clear history" button clicked I guess

[TobiGr]

Is it possible to put get the background, pop up, and play all actions in a single row? The buttons and sort by drop down use a lot of vertical space.
What is the reasoning to make the sort by box not to grow to the full width of its parent container in portrait mode?

[Isira-Seneviratne]

Is it possible to put get the background, pop up, and play all actions in a single row? The buttons and sort by drop down use a lot of vertical space. What is the reasoning to make the sort by box not to grow to the full width of its parent container in portrait mode?

A scrollable row could be used to keep the buttons in the same row (at the moment, a FlowRow is used to adjust the buttons if the screen width is too narrow). The sort box could also be included in the same row if needed.

[Isira-Seneviratne]

@TobiGr I revised the UI again to use a segmented button instead of a dropdown.

[TobiGr]

thanks. I am wondering whether the checkmark is the right icon to use here. Did you try to use the sort icon?

[Isira-Seneviratne]

No, but I added the Sort By label for clarity.

[Stypox]

I would put the Clear button in the three-dot menu, it's rarely used and especially should not be pressed on by accident.

[Isira-Seneviratne]

I would put the Clear button in the three-dot menu, it's rarely used and especially should not be pressed on by accident.

It opens a confirmation dialog first.

[Stypox]

I know, but I still think it would be better in the 3-dot menu (also because it would use up less space). Consider that if somebody doesn't want history they would just disable it, they wouldn't keep using the clear button.

[Isira-Seneviratne]

Good point. I made the change.

[sonarqubecloud]

Quality Gate passed

Issues
9 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[ShareASmile]

No, but I added the Sort By label for clarity.

Would you please restore earlier default behavior of "sort by" to "date", it defaults to "views" in this PR.

Also noticed a minor bug: last selected option isn't saved, it switches to sort by "views" even after manually changing it to sort by "date" after reopening the app.