Skip to content

Added the Skip Button to ReaderDiscoverViewController - #25921

Merged
jkmassel merged 4 commits into
wordpress-mobile:trunkfrom
Vivek09Chahal:Skip-Button-UI-Introduce
Aug 21, 2026
Merged

Added the Skip Button to ReaderDiscoverViewController#25921
jkmassel merged 4 commits into
wordpress-mobile:trunkfrom
Vivek09Chahal:Skip-Button-UI-Introduce

Conversation

@Vivek09Chahal

@Vivek09Chahal Vivek09Chahal commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Description

Open Issue: #25911
Before on the first Time opening of the discover page in the reader tab, forces user to choose a tag, without choosing tag it didn't allowing the user to move forward.

Added a Skip button below on the page.

2026-08-20_23-13-25

Testing instructions

  1. Sign out and reset the app, or clear its state, so the tag-selection screen appears on first Discover visit
  2. Go to Reader → Discover — the "Select a tag" screen appears
  3. Without selecting any tag, tap Skip (below the primary button)
  4. Confirm you're taken into Discover with no tag pre-selected, and no tags are saved as followed
  5. Repeat, this time selecting one or more tags and tapping the primary button, to confirm the existing flow still works
  6. Verify Skip button appearance/placement in both light and dark mode, and with larger Dynamic Type
  7. Verify VoiceOver reads "Skip" and it's reachable/actionable

Copilot AI lite review requested due to automatic review settings August 21, 2026 05:52

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@Vivek09Chahal Vivek09Chahal changed the title Added the Skip Button to the ReaderDiscoverViewController Added the Skip Button to ReaderDiscoverViewController Aug 21, 2026

@jkmassel jkmassel left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks for the contribution! I've opened #25924 with a few additional housekeeping things :)

@jkmassel
jkmassel added this pull request to the merge queue Aug 21, 2026
Merged via the queue into wordpress-mobile:trunk with commit 1cec770 Aug 21, 2026
23 checks passed
jkmassel added a commit that referenced this pull request Aug 24, 2026
Follow-up to #25921 addressing review findings:

- Track a `select_interests_skipped` event; skip was the one
  interest-selection outcome with no analytics, so the funnel could not
  distinguish it from an abandonment.
- Disable the button on first tap to debounce, matching the primary
  button; a fast double-tap could otherwise re-run the Discover flow's
  dismiss and forced stream sync.
- Call `readerDiscoverFlowDelegate?.didCompleteReaderDiscoverFlow()` on
  skip so a flow that both shows Skip and sets the delegate completes.
  Inert today — the only Skip flow (Discover) leaves the delegate nil.
pull Bot pushed a commit to kliu/WordPress-iOS that referenced this pull request Aug 25, 2026
…ols (wordpress-mobile#25924)

* Reader: Harden the interest-selection Skip button

Follow-up to wordpress-mobile#25921 addressing review findings:

- Track a `select_interests_skipped` event; skip was the one
  interest-selection outcome with no analytics, so the funnel could not
  distinguish it from an abandonment.
- Disable the button on first tap to debounce, matching the primary
  button; a fast double-tap could otherwise re-run the Discover flow's
  dismiss and forced stream sync.
- Call `readerDiscoverFlowDelegate?.didCompleteReaderDiscoverFlow()` on
  skip so a flow that both shows Skip and sets the delegate completes.
  Inert today — the only Skip flow (Discover) leaves the delegate nil.

* Reader: Add debug menu controls to re-show the interests screen

The select-interests screen is a one-time onboarding prompt gated by
`readerDidSelectInterestsKey` and an `isFollowingInterests` check, which
makes it hard to see again during development. Adds two internal-only
Developer menu actions:

- Show Reader Interests Screen — presents the `.discover` screen
  directly, bypassing both gates so it can be inspected on any account.
- Reset Reader Interests Prompt — clears `readerDidSelectInterestsKey`
  so the real auto-prompt can fire again on the next Discover visit.

* Reader: Make the reset-interests debug confirmation legible in dark mode

The debug menu's shared `showSuccessNotice()` posts a bare "✅" emoji,
which is illegible against the notice's inverted (light-in-dark-mode)
background. Post a text confirmation for the Reset Reader Interests
Prompt action instead.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants