[Networking] quicksite:
Chris, thanks... Sorry I was pontificating there. Let me clear up a few things. (1) I don't have an iphone; I've never had one in my hand for more than a half hour exploring, so have never used it in "real life" scenarios. (2) I wasn't suggesting Apple could magically make all the login and acceptance requirements go away! I just meant that they do focus on exactly these kinds of common bottlenecks, to try to reduce the clutter of steps, and get the goal accomplished. (3) #2 above is not based on my having used an iphone at a coffeehouse, nor watching someone with an iphone login at a coffee house. I was commenting because this thread had been dormant for a good while, then suddenly yesterday someone commented about frustration he was having with this very issue -- and HE concluded something like "this is why Apple is winning the war".

I never took that as any kind of fanboy comment, or instigating remark. I am just imagining this person had some similar problems that I have had, and searched XDA, and came upon this thread -- because there are no other threads that I know of on this site on this subject matter of wifi utility to help smooth out the coffee house login process. And he probably read thru it thinking at the end was a solution... only to find the thread dropped off because nobody presented a solution... I merely did my best to comb the web and XDA to find potential solutions, but it stopped there because most of the utilities were about turning your device's wifi on or off, then selecting an access point. But that's not the problem that needs solving.

What I was suggesting is that just like a Google mail app connects to the web within its own UI, and NOT opening up a browser, which on some older devices like mine does take a while just to get the browser open and loaded to its home page... And it queries for username and password then pulls in your mail. And just like T-mobile has a Hotspot Utility that is a very niche specialized version of such a wifi utility limited to its access point locations like starbucks and airports and fed ex kinkos offcies, it similarly establishes a web connection without opening a browser. But it's purpose is exactly what I am talking about: to make that stuff happen as much as possible in the background so that you then get confirmation of being logged in and connected,and you can then use whatever browser you like, including opera mini.

So, though I am not a programmer, it seems to me this would not be so hard to master if someone who IS a developer applied some resource time to the problem (but that's just it, it doesn't seem to be a problem that most feel warrants any resource time applied to it). To me it would be very simple.

(1) Click a button and it queries the state of all data connections on your phone noting if wifi is on or off, and makes sure to turn wifi on if needed. (2) Like most wifi utilities, it then seeks the strongest connection and tries to login to any unsecured access point, or, if it recognizes even a secured access point, follows a login proceedure. (3) I am not sure how best to explain step 3 but to me it happens in the background: A dedicated web client/ thin-browser (something to build) opens and issues the normal commands that = "open my browser and after it loads, hit the home button to then have the browser connect to the coffee house's login page. (4) My hope would be that at this point the thin browser client can present the login page, user clicks "i agree" as normal, then (5) the connection to the wifi access point in made, and (6) the utility puts itself away, opening my preferred or default browser... and (7) I just start using my browser which is now connected via wifi.

As a user experience designer I can envision this thin client speeding up this process because it doesn't have to load a full featured browser, and it includes the wifi on/off function, essentially resulting in this, as far as user is concerned:

(1) arrive at a wifi spot that requires accepting TOS, click "SuperWifiLogonUtility" and all the wifi on/wifi off stuff happens in background.

(2) I select the access point i am trying to connect to, done.

(3) Background processes occur, and the next thing I see is the wifi provider's login page and I check "yes, i agree"

(4) That goes away, my preferred browser opens and I begin using browser connected to wifi.

Of course, I could be wrong, and perhaps this is complicated. It doesn't seem so to me :)