chore/12765 - Track large nav button presses

[AdryienH]

There is no requirement to implement the suggestions but please respond to Copilot review comments in some way. Unaddressed comments will prevent the PR from moving to the QA process.

Description of Change

• Added vama_large_nav_btn_click analytic to track <LargeNavButton /> usage

Target Release Date

Link to Issue

closes #12765

Code testing

• Unit tests have been created or updated to cover this change
• End to end (Detox) tests have been added or updated as needed

Pre-QA Artifacts

Include all artifacts or select not applicable and explain below.

• Screenshots or screen recording at factory default settings (before and after, if applicable) in portrait orientation
• Screenshots in landscape orientation
• Screenshots at 2x text size
• Screen recording of interaction using VoiceOver (iOS) and/or TalkBack (Android)
• Visual artifacts not applicable to this PR (explain why below)
  No visual changes were made only added analytics

How to capture these

Screenshots & Video

• Capturing screenshots and videos from Simulator, iOS
• Take screenshots on the Emulator, Android

2x text size

• iOS Dynamic Type: Settings > Accessibility > Display & Text Size > Larger Text. Toggle ON, move slider.
• Android Font Scale: Settings > Accessibility > Display size and text. Adjust Font size and Display size sliders.

VoiceOver / TalkBack (best on actual hardware)

• iOS: Turn on VoiceOver · Screen recording / QuickTime from Mac
• Android: Turn on TalkBack / SCRCPY for desktop capture

Test Context for QA

How does a user get here?

Feature Flags

Risk Assessment:

• Low (UI polish, copy change, isolated component)
• Medium (New feature, non-core path)
• High (Changes to Core Features: Login, Claims, Rx, Secure Messaging, major updates to a backend service, etc.)

What should QA pay extra attention to?

Test Review

Test User(s)

---

Checklist for QA

QA Engineer: Check off the items below as you test

• Shared Test Script executed (post results as a PR comment)
• Feature-specific verification based on QA Test Context above
• Tested on iOS
• Tested on Android

Run a build for this branch

[Copilot]

Pull request overview

This PR adds a new analytics event to capture user presses on the shared <LargeNavButton /> component, supporting consistent usage tracking for large navigation/category tiles across the app.

Changes:

• Added a new analytics event factory: Events.vama_large_nav_btn_click(buttonTitle)
• Updated LargeNavButton to log the new event on press before invoking the provided onPress callback
• Updated internal metrics documentation to include the new event’s parameter mapping

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
VAMobile/src/constants/analytics.ts	Adds the vama_large_nav_btn_click event definition with p1 capturing the button title.
VAMobile/src/components/LargeNavButton.tsx	Logs the new analytics event whenever a LargeNavButton is pressed.
VAMobile/documentation/gettingStarted/Metrics/Event Parameter Reference.md	Documents the new event and its p1 parameter meaning (buttonTitle).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[digitalken]

@AdryienH - What are the large nav buttons that are supposed to be tracked with this? I asked for figma access but it hasn't been granted yet. Thanks.

[AdryienH]

@digitalken They are these tiles on the Health, Benefits, and Payments Tabs. You can hold off on this one though, this PR will likely have to change because of some analytics re-work we're doing.

[digitalken]

@digitalken They are these tiles on the Health, Benefits, and Payments Tabs. You can hold off on this one though, this PR will likely have to change because of some analytics re-work we're doing.

Oh, ok. Thanks @AdryienH . I'll go ahead and pick up the other analytics tag...