Skip the "Do you want to open ?" Modal

Question

Created 2w

Replies 1

Boosts 0

Participants 2

We have an Angular web application which gets installed as a webclip on client iPads. The web application has buttons that will take the user directly to our native iOS application. We also would like a way for our webclip application when opened to perform some data lookups and if certain conditions are met, then take the user directly to our native iOS app.

We're using vanilla JS window.open. This works well when the user manually taps button. However, this does not work when the webclip application tries to open the native iOS app without user interaction. In that case the window.open does nothing. The window.open target URL is the exact same in both cases.

We tried using URL Schemes instead of Universal Links but with this the iPad displays a modal asking "Do you want to open <app name>?". For our use case, this is unacceptable. Is there any way for us to skip this prompt? We'd like there to be no additional action needed from the user to be able to get from webclip to native iOS app beyond simply opening the webclip.

Boost

Answer 1

DTS Engineer OP

Apple

2w

Thank you for sharing your post. To ensure seamless navigation from your Angular web application to your native iOS app via a webclip without user interaction or prompts, Universal Links may be a suitable solution. However, it’s important to note that Apple imposes restrictions on automatic launches of native apps from web content for security reasons.

Regarding your mention of using URL Schemes instead of Universal Links, I would like to understand the reasons behind your decision to discontinue using Universal Links?

Universal Links
- Universal Links are designed to open your app directly if it's installed, or fall back to a website if not. This is the most seamless user experience available without dealing with URL schemes and prompts.
- Ensure your app's entitlements and Apple Developer account are set up correctly to handle Universal Links.
- If the conditions you mentioned can be checked via deep link parameters, include these in your Universal Link setup.
Custom URL Schemes:
- If Universal Links aren't feasible or introduce unwanted UX, you might reconsider custom URL schemes, although as you've noted, they prompt the user.
- Consider enhancing the user experience by ensuring your app's info.plist correctly declares the custom URL scheme and handling any prompts programmatically within the app to provide a smoother transition.

If you'd like us to consider adding the necessary functionality, please file an enhancement request using Feedback Assistant. Once you file the request, please post the FB number here.

If you're not familiar with how to file enhancement requests, take a look at Bug Reporting: How and Why?

While these approaches each have trade-offs, Universal Links remain the most Apple-sanctioned method for securely and seamlessly transitioning between web and native app contexts on iOS.

Albert Pascual   Worldwide Developer Relations.

0