By Stephen Schenck | May 8, 2013 3:43 PM
It is no fun trying to horn-in on Apple’s turf when it comes to iOS, and no matter how much of a better browser you think you can make, the platform is going to keep steering users back to Safari. What’s a dev to do? If you’re Google, trying to raise Chrome’s image on iOS, you reach out to other developers, giving them some interesting ways to let their users interact with web pages.
What this new system lets developers do is have their apps send users over to Chrome to check out a web page. The system call directs them to Chrome in specific, bypassing Safari in the process. Devs might want to take this route over using an in-app browser window if users are expected to be interacting with larger content.
The neat part is how this lets them get back. When an app sends them to Chrome in the first place, it can create a button users can tap to jump right back in to the originating app. Besides being convenient, this helps developers avoid their users getting distracted and wandering off into the depths of the internet, keeping them focused on the app and coming back for more.