I've been conducting tests on various iOS apps to identify those that disrupt website downloads when using in-app browsers. During my testing of Gmail, I observed that clicking on Safari within the app actually leads to what seems to be SFSafariViewController. However, the downloading experience within this view is notably cumbersome. To save an image, users must first select 'More...' then scroll to find and select 'Save image'. This behavior is unexpected when users anticipate accessing the full Safari browser. What are the reasons behind the differing UI/UX of SFSafariViewController and Safari?

I've noticed on Android devices the use of deep linking, which also permits the inclusion of a backup URL that opens in the user's default browser. This feature has been incredibly useful for me in exiting in-app browsers, as many of them break sites by not allowing for downloads. I'm reaching out to request guidance on creating a reliable link for web developers, ensuring users can seamlessly redirect to the full-featured view of our websites.