Hey everyone, i am building a native mobile app and i want to create this type of workflow :
When a user receives a notification and clicks on it, it gets him exactly to the page concerned.
like when someone comments your facebook post, you click on the notification and gets you to the exact post and opens your comment section.
Yeah, this is doable, you just need to handle deep linking properly.
When you send the push notification, include some data with it (like the page name and the thing’s ID — for example, a post ID or comment ID). Then set up deep links in your app so that when the user taps the notification, the app reads that data and navigates straight to the correct page and state.
So instead of just “opening the app”, the notification says something like: open /post/123?comment=456. The app catches that link, loads the post page, and scrolls or opens the comment section automatically.
That’s basically how apps like Facebook do it. If you want, tell me what you’re using (Bubble + BDK, FlutterFlow, native iOS/Android, etc.) and I’ll explain it in the exact way for your setup.
Can you be more specific? I was left with the fact that Bubble Native Mobile still didn’t support deep linkink..
Yeah, fair point — Bubble Native Mobile doesn’t support true deep linking the same way web does, so you can’t rely on universal links like /post/123 yet.
The way people handle this right now is by passing data inside the push notification payload, not via a URL. When the user taps the notification, Bubble gives you access to that payload in the “app opened from notification” event. From there, you manually route the user to the right page and load the correct data using the IDs you sent.
So instead of deep linking, it’s more like “controlled navigation after open.” You include something like post_id or comment_id in the notification, then on app open you check: if post_id exists → go to post page → load that post → open comments. It’s not automatic deep linking, but functionally it achieves the same result.
That’s the current workaround until Bubble adds real deep link support.
