wordpress-mobile / wordpress-mobile/WordPress-Android

Zendesk Push Notification Possible Improvements

Open
#7,839 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

[Type] Enhancement Support
Dominant language
Kotlin
Stars
3.2k
Forks
1.4k
Avg merge
1d 11h
Merged PRs (30d)
69

Description

We are currently implementing Push Notifications for Zendesk and we decided to keep it simple for the first iteration as there are some potential issues we'd like to avoid.

The feature has not yet been fully implemented yet, but our expectation is to have the push notification tap to bring the user to the Me tab as iOS currently does at the moment. Here are some possible improvements we can do on that:

  1. Show a badge in the Me tab and Help page meaning that there is a Zendesk reply waiting Zendesk doesn't provide this functionality and iOS uses push notifications for it which is unreliable. We'll not be implementing this.
  2. Instead of landing the user into Me tab, land them into Help page. The issue with that we should be providing the selectedSite to the HelpActivity and we don't know about it (not easily anyway) when it's triggered from a push notification. This one is just not worth it, the better way to do it is just to deep link the ticket without a backstack.
  3. Ticket deep-linking. Although that's a nice idea in theory, when I tried it out, I found that it could be pretty problematic for us. When we open My Tickets or Contact us from Help page, we do a lot of configuration which is required for opening a new ticket. If we were to do ticket deep linking, all those will be bypassed and opening a new ticket can cause some issues for us. I don't expect us to fully implement this, at least not as is, but I am adding a note about my findings just in case. Ticket deep-linking works a little different for their sdk v2 which we have migrated to. We are still looking into this one, so I am keeping the issue open. See last section of #7951 for more details.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the last section of issue #7951 and the existing Zendesk push-notification flow. Review how HelpActivity receives selectedSite and how SDK v2 handles ticket deep links. The issue remains open while the team investigates the approach, so completion criteria are not yet defined.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
mobile-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.