Agreed! This is just spectacular. I'm going to geek out and show my wife when she gets home from the late shift. I just finished showing off my iPhone to some friends tonight, and this makes it even more useful than before! I can really see myself using this in the future, and I'd just started to sour on the Google App.Works really well.
Here's my problem... I think I can SEE why they don't want to have the Google app come up in a web browser. --It's not supposed to duplicate Safari. The mini-webkit window is supposed to be there to give you quick access to results and stuff, but they're stopping show of giving you a full-on Safari experience. --For instance, if you went into Gmail, and a link in Gmail transferred you to another website. --When does Google know to leave the Gmail app? Maybe you don't want to be in the Gmail app for a particular link... how do you escape the Google App when you're using web apps that may or may not stay inside a Google domain? For instance, at one point I saw Google forward me to a raw IP address before the site was redirected.I'd really like better integration with Google Apps though. For example, a native view for news instead of launching the page in the browser. If it had native interfaces for the apps, it would instantly be a must-have application.
I could see it being hard for Google to detect WHEN to stay inside the web app, and when to launch Safari if it doesn't decide immediate. --Google doesn't want to modify its websites simply to cater to such conditions across its suite of sites. Things just need to WORK. --To that end, the Google app needs to launch Safari at the earliest opportunity.
Notice... the Google webkit doesn't do "rotate". It also doesn't use the "pinch" actions on search results. It doesn't let you save an image, or email a link. The longer Google fails to launch Safari for the user, the more users will request that Google replicate Safari features. It's NOT the way its supposed to work.
~ CB