Skip to content

Migrate wear events to Event Horizon#5109

Open
MiSikora wants to merge 1 commit intomehow/task/event-horizon-miscfrom
mehow/task/event-horizon-wearos
Open

Migrate wear events to Event Horizon#5109
MiSikora wants to merge 1 commit intomehow/task/event-horizon-miscfrom
mehow/task/event-horizon-wearos

Conversation

@MiSikora
Copy link
Contributor

Description

This migrates Wear OS related events to Event Horizon.

Relates to PCDROID-419

Testing Instructions

I would mostly focus on the code review and smoke test some of these events as the migration process is rather a mechanical one.

  • wear_main_list_shown
  • wear_main_list_now_playing_tapped
  • wear_main_list_podcasts_tapped
  • wear_main_list_downloads_tapped
  • wear_main_list_filters_tapped
  • wear_main_list_files_tapped
  • wear_main_list_starred_tapped
  • wear_main_list_settings_tapped
  • wear_require_plus_shown
  • wear_signin_shown
  • wear_signin_google_tapped
  • wear_signin_phone_tapped
  • wear_signin_email_tapped

Screenshots or Screencast

N/A

Checklist

  • If this is a user-facing change, I have added an entry in CHANGELOG.md
  • Ensure the linter passes (./gradlew spotlessApply to automatically apply formatting/linting)
  • I have considered whether it makes sense to add tests for my changes
  • All strings that need to be localized are in modules/services/localization/src/main/res/values/strings.xml
  • Any jetpack compose components I added or changed are covered by compose previews
  • I have updated (or requested that someone edit) the spreadsheet to reflect any new or changed analytics.

I have tested any UI changes...

  • with different themes
  • with a landscape orientation
  • with the device set to have a large display and font size
  • for accessibility with TalkBack

@MiSikora MiSikora added this to the 8.8 milestone Mar 11, 2026
@MiSikora MiSikora requested a review from a team as a code owner March 11, 2026 11:43
@MiSikora MiSikora requested review from Copilot and geekygecko and removed request for a team March 11, 2026 11:43
@MiSikora MiSikora added [Area] Analytics Analytics related issues do not merge [Type] Enhancement Improve an existing feature. labels Mar 11, 2026
@dangermattic
Copy link
Collaborator

1 Error
🚫 This PR is tagged with do not merge label(s).

Generated by 🚫 Danger

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Migrates Wear OS analytics from the legacy AnalyticsTracker/AnalyticsEvent system to Event Horizon, aligning wear tracking with the newer analytics pipeline (PCDROID-419).

Changes:

  • Replace AnalyticsTracker.track(AnalyticsEvent.*) calls with EventHorizon.track(*Event) in Wear view models.
  • Update Wear unit tests to assert tracked Event Horizon events via TestEventSink.
  • Add the analytics testing module as a Wear test dependency.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
wear/src/test/kotlin/au/com/shiftyjelly/pocketcasts/wear/ui/WatchListScreenViewModelTest.kt Switches analytics assertions to Event Horizon events using TestEventSink.
wear/src/main/kotlin/au/com/shiftyjelly/pocketcasts/wear/ui/authentication/RequirePlusViewModel.kt Migrates “require plus shown” tracking to Event Horizon.
wear/src/main/kotlin/au/com/shiftyjelly/pocketcasts/wear/ui/authentication/LoginViewModel.kt Migrates Wear sign-in shown/tapped events to Event Horizon.
wear/src/main/kotlin/au/com/shiftyjelly/pocketcasts/wear/ui/WatchListScreenViewModel.kt Migrates main list shown/tapped events to Event Horizon.
wear/build.gradle.kts Adds modules.services.analytics.testing for Wear unit tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Area] Analytics Analytics related issues do not merge [Type] Enhancement Improve an existing feature.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants