How to open Deep Links, Notifications and 3D / Siri Shortcuts
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 7.9k
- Forks
- 914
- PR merge metrics
- No merged PRs in 30d
Description
All these features are serving the same purpose — opening a specific app page / RIB. Curious to hear from Uber employees how do they think what's the right way of handling all these shortcuts. I experimented with workflows and faced with a problem that different actions are handled by different RIBs. For example, I have an app state (RIBs tree) which looks like:
Root -> LoggedIn -> Dashboard
Where dashboard might be tab bar or a custom dashboard with multiple tiles on it (think of FB tab bar).
So there are several different deeplinks might exist:
- Post
- Profile
- Notification
- etc
And if I follow actionable items and workflow pattern (from RIBs) I have to implement dashboard actionable item to route to a particular RIB to handle an action. And if I can open a profile or a post right from dashboard, I can't do the same for notifications. I need to attach notifications RIB first and then handle a notification.
Any ideas how to do this in a proper way? Any experience dealing with similar cases?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the RIBs actionable item and workflow patterns referenced in the issue, then compare how deep links, notifications, 3D Touch, and Siri Shortcuts enter the Root → LoggedIn → Dashboard tree. Done would require a decided routing approach that handles the listed destinations consistently and explains how the relevant RIBs should participate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile, mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100