Redesign app updater with global status management and UI enhancements

[Himanth-reddy]

This pull request introduces a comprehensive in-app update system for the application, including a user interface for update notifications and actions, and the necessary state management to support it. The update badge is now displayed in both the top bar and sidebar when an update is available, and a modal dialog guides users through the update process. The changes are grouped below by theme.

User Interface Enhancements for Updates:

• Added an update badge indicator to both the AppTopBar and Sidebar components, visually alerting users when an update is available. The badge appears as a red dot on the settings gear icon in the top bar and the settings icon in the sidebar. (AppTopBar.kt, Sidebar.kt) [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]

• Introduced a new AppUpdateModal composable, which displays a modal dialog guiding users through the app update process, including states for checking, downloading, installing, failures, and update notes. The modal provides contextual action buttons and progress indicators. (AppUpdateModal.kt, HomeScreen.kt) [1] [2]

State Management and ViewModel Integration:

• Extended HomeUiState to include update-related properties: updateStatus, showAppUpdateDialog, and hasUpdateBadge, enabling the UI to react to update events and display the appropriate indicators and dialogs. (HomeViewModel.kt)

• Updated the HomeViewModel to inject and use new update-related repositories and managers (AppUpdateRepository, ApkDownloader, UpdatePreferences, UpdateStatusManager), laying the groundwork for managing the update process and user preferences. (HomeViewModel.kt)

These changes collectively provide users with a seamless and interactive in-app update experience, ensuring they are notified of new updates and can easily take action within the app.

[ProdigyV21]

Thanks, this is a good direction and the merge build passes for both Play and Sideload.

I would like a few cleanups before merging:

1. PackageInstaller failure retry can become a no-op
   ApkInstallReceiver sets UpdateStatus.Failure(userMessage) without attaching the AppUpdate. The modal then shows a Retry action, but downloadAppUpdate() only retries a Failure when Failure.update is non-null, so after an install failure/cancel the Retry button may do nothing. Please keep enough update context for retry, or make the failure action re-check for updates first.

2. “Ignore” is now session-only
   ignoreAppUpdate() now uses sessionIgnoredTag instead of persisting the ignored release via UpdatePreferences. That means the same ignored update can appear again after app restart. If this is intentional, maybe label it “Later”/“Dismiss” instead of “Ignore”. If “Ignore” should mean ignore this release, please keep writing the tag to UpdatePreferences.

3. git diff --check fails
   There is trailing whitespace in HomeViewModel.kt and SettingsViewModel.kt. Not a runtime issue, but it should be cleaned up before merge.

[Himanth-reddy]

Implemented the review cleanups.

Changes:

UpdateStatusManager now remembers the last AppUpdate context and attaches it to context-free Failure statuses, so PackageInstaller failure/cancel retry can download again.
Ignore persists the release tag again via UpdatePreferences in both Home and Settings.
Home update badge/dialog suppression now checks the persisted ignored tag after restart.
Trimmed trailing whitespace in the touched files.
Verified:

git diff --check passes.
./gradlew :app:assemblePlayDebug :app:assembleSideloadDebug passes. Existing deprecation/always-true warnings remain, but no build errors.