I wish Apple would open up its system so the user can select her own default programs. Oh my, daydreaming.
Making Chrome better on iOS
51–60 of 68 posts
Re: Making Chrome better on iOS
#52Cydia has a tweak to change your default browser. Sorted. iOS Chrome has greater issues. Tab management is all whizz bang but very unintuitive. I have used it for about a day and can it fathom how to email a link to the current page to someone. Emailing a link to the current page is not a standard use case for desktop but it is typical on mobile. Further: it's hard to see where to arrest the loading of a page, the pr…
In order to email the current page, or stop a page from loading, hit the menu button to the right of the omnibar. Email will be the 5th text row down. Note that I do not think it is a side effect of desktop to mobile, but instead their attempt to maximise the content area.
[deleted]
Re: Making Chrome better on iOS
#53Just a heads up: the page doesn't scroll on android, so its impossible to read the whole article.
Re: Making Chrome better on iOS
#54"If a user has Chrome installed, chances are they wish that it would be their default browser."
Horrible assumption. I am all for Apple stealing Android's intents. Assuming that because the user has an app installed they want it to be the default is wrong.
I think the better approach would be each app could ask the user once if they want Google Chrome to be their default browser and then store which one they should open. Sure it is more code but it will be a better user experience than forcing them to uninstall Google Chrome if they don't want it.
Re: Making Chrome better on iOS
#55Please Apple. I will downvote every person who whines about "stealing" if you just hurry up and steal Android's Intents.
The lack of "Intents" on iOS is deliberate IMHO. Apple's products are in the default roles for all the common intents and implementing support for switching intents across the OS would result in less people using Apple's first-party apps. Being the browser is a very valuable position, and not one I expect Apple would invest dev resources to give up.
Re: Making Chrome better on iOS
#56Please Apple. I will downvote every person who whines about "stealing" if you just hurry up and steal Android's Intents.
Yup it's a major missing element on iOS and many iOS supporters just don't understand how great it really is...
I haven't used iOS, but as an Android user I can definitely see why they haven't implemented it yet. It's a powerful feature, but at least on Android, it's also a usability disaster.
Basically, the way it works on Android is that whenever an intent is passed for which there is no default, the user gets a dialog. The dialog will contain the applications that the user has installed for handling that intent. When there are 4+ items (eg, PDF) this can be confusing.
Then when they pick one (hopefully the one they really wanted) they check the box to make it default. So far this is confusing for some people, but they generally muddle through somewhat happily.
But there are issues... which protocols does the browser accept? Oh, http, https, and possible one or two more. So later they tap an https url and have to go through the same process again.
The next day, one of their four web browsers auto-updates from the Play store. This clears the defaults, and they have to go through the whole process again.
Seriously, the underlying concept seems solid, but the implementation is severely lacking. I hope that they (or someone) does this right in the future. I'm not entirely sure what a solid solution would look like, but I certainly don't expect Apple to copy the Android approach. It's completely incompatible with a number of their UX goals for the platform, IMO.
Re: Making Chrome better on iOS
#57Please Apple. I will downvote every person who whines about "stealing" if you just hurry up and steal Android's Intents.
The lack of "Intents" on iOS is deliberate IMHO. Apple's products are in the default roles for all the common intents and implementing support for switching intents across the OS would result in less people using Apple's first-party apps. Being the browser is a very valuable position, and not one I expect Apple would invest dev resources to give up.
So you're OK with that?
Re: Making Chrome better on iOS
#58While this is an interesting idea, it is pretty useless in practice, IMO. Email is by far the app I (and I assume most others) am going to be clicking the most links from, and I'm gonna go out on a limb and say that Apple won't be changing their links to go to chrome. If you use something like the gmail app, they (if they don't already) should probably be doing something like this.
or sparrow
Re: Making Chrome better on iOS
#59First step to making it better might be fixing the awful scrolling. Chrome on iOS is slick but it stutters like hell when scrolling large vertical pages. Safari has no problem.
Re: Making Chrome better on iOS
#60"If a user has Chrome installed, chances are they wish that it would be their default browser." Horrible assumption. I am all for Apple stealing Android's intents. Assuming that because the user has an app installed they want it to be the default is wrong. I think the better approach would be each app could ask the user once if they want Google Chrome to be their default browser and then store which one they should o…
What's stopping the app creator from asking the user (in a settings" page) which browser s/he wants to open web pages in? Default will be Safari, unless changed explicitly