3 ms·
I really wish the idea that apps need to open websites in-app would go away. Like it looks neat when you're demoing it for your coworkers but it just increases
by Spivak 7y ago
I really wish the idea that apps need to open websites in-app would go away. Like it looks neat when you're demoing it for your coworkers but it just increases the number of taps since to do anything useful I need to open in in Chrome/Safari anyway.
If the in-app browser was just a window into actual Chrome/Safai (i.e. it's a real tab when you open Chrome/Safari and has your logins bookmarks, etc.) and you could "pull" the window into the foreground as a slick transition to the browser app then it would be fine, but as it's implemented it's mostly just annoying for everything but oauth flows.
- pcr910303 7y agoHmm, that’s strange because I mostly find the ability to open websites in-app very useful: The context of how I was directed to the website exists in the app. I feel that if the site I’d moved to Safari, I eventually forget how I got to this site. I think the problem isn’t in the WebView model - It’s probably that you have to use the browser to do something useful that WebViews can’t.
- dbbk 7y agoThis is essentially an Oauth flow...
- yunyu 7y agoChrome custom tabs have access to your passwords and autocomplete history, for what it's worth
- skavi 7y agoThat’s exactly how chrome custom tabs on Android work. Moving the app custom tab to the browser does not even reload the page.