Googler: "we pushed a bad version of our iOS app for Gmail"
plus.google.com
plus.google.com
1. No one has taken time to address the real issue—yes, there's a weird bug on launch, but the real issue is that the app itself blows. It's terrible. It's basically entirely a web view that runs even slower than the GMail webapp itself. As Scoble says in the comments: "The bar is high for apps. Make it better than a web page or DO NOT RELEASE! Please."
2. This an absurdly easy thing to check for. This has happened first with the Google Voice app, then with the Google+ app, now with the GMail app. Is Google committed to systematically destroying their own brand?
I don't know the current situation, but for example Nitro was not available on UIWebView in iOS 4.3 ; also UIWebView does not do any caching by itself and doing it yourself is tricky. So this may explain why the performance of this GMail app is worse than the web app.
I understand why one would release native apps with web UIs. It's totally fine if you're on a budget. But the iPhone already has a perfectly fine email app and it also syncs well with your Google Apps account through its Exchange integration.
If an official GMail app is not better than the built-in functionality, then it's not only useless, but also affects their credibility.
Isn't Apple destroying their brand with the original iPhone 4's crappy antenna and with the new iPhone 4's crappy battery life?
Bugs happen. It's software.
It's not about whether Apple writes better iOS apps than Google does for Android, it's about whether Google makes any good apps for iOS.
The OP isn't complaining about this bug. He's complaining of what appears to be a systemic problem both technically and in product design with Googles iOS apps. These issues can't just be hand waved away as easily as "It's software"
Bugs happen, always. And, of course, there are compromises you have to make to product, always, in order to ship.
What matters is where you draw the line. I'm sure that nobody will say that the antenna problem 'ruined' the iPhone. After all, it still launched, people still bought it, and all was well.
Three times now, for some reason, Google has * completely* ruined their launches. The Google Voice app, the Google+ app, and the GMail app all had easily caught, gamebreaking bugs that were so major that they required a full recall of the app.
For a tiny startup, this sort of launch-fumbling would be pretty bad. For an enormous company, it's almost laughable.
Every new iPhone I've bought -- and I've owned them all except the 3G -- has run down quickly the first couple of times I charged it, and every one has eventually achieved reasonable battery life after the break-in period. The 4S was no exception. Non-story, move on. It's unclear why Apple doesn't explain this.
I did discover one such issue. I have the New York Times app and access to a subscription for it. After updating to iOS5, the first time I tried to use the NYT app, it moved itself into the new "Newsstand" and changed its behavior so I started getting "alerts" whenever anything allegedly newsworthy happened. I had never gotten such alerts before, because I had that feature turned off. It was ridiculously hard to find the option to entirely turn off unattended polling related to the NYT app because the setting isn't where you'd expect it to be. (It's in Settings:Store)
(Apple has apparently identified some of the issues and just started beta-testing an update that is alleged to fix them.)
That alone makes it better than the native iPhone Mail application for me, since now I'm not going to get automated messages, newsgroup messages, etc., in my phone's main inbox.
So far I'm quite happy with it (I noticed the error on initial launch but ignored it - stupid mistake for Google to make, but didn't seem to affect my use of the application) and I'm kind of relieved it doesn't have push notifications, since I'm not sure I want them unless I can turn them off. Not so sure why everyone is piling on so hard.
In particular, it often blocked the main (UI) thread while waiting for data from the network, so it would hang for seconds at a time. Not doing that is pretty much application development 101.
In contrast, Android's gmail client is one of Android's biggest draws, and has never in my two years of using Android had a bad release. Instead it just keeps getting better.
Google Reader being released to universal complaints that it's made reading more difficult due to too much whitespace (a mistake that Gmail didn't make even though it uses the same design).
Gmail app being released and seemingly universally panned as being such a bad app, plus it's released with a major bug requiring the app to be pulled.
Since I actively use all three Google products, I'm a little more biased/sensitive to these mis-steps and may be making more of their mistakes than I should. But it seems to me that Google is really struggling to execute anything successfully these days. I can't decide if my expectations of Google has changed, whether Apple has caused me to have higher expectations on the release of a product, or if Google is genuinely stumbling - but my impression is that Google is making basic fundamental errors in the management of their products. Fragmented release dates alienating your loyal users, buggy releases and just outright bad design - to me, it seems like no-one is in control at Google - their work is becoming sloppy and I can only imagine that will hurt their brand in the long term if this isn't turned around.
Edit: Removed the 'over a year late' bit from the first line . Thanks to those who pointed that out - I actually did know it was released this year - I'm probably guilty of running on auto-pilot and inserted a 'cliched phrase' as I typed :S
I don't think Google+ launched a year ago.
https://plus.google.com/102053381273068034374/posts/gc4Jj4wX...
" The iOS app we launched today contained a bug which broke notifications and caused you to see an error message when first opening the app. We’ve removed the app while we correct the problem, and we’re working to bring you a new version soon. In the meantime, everyone who’s already installed the app can continue to use it.
"We want to bring you a great Gmail experience, and we're sorry we messed up here."
Loopt had this problem a few times, despite an explicit item in our submission checklist to manually check the manifest file in a text editor. XCode often, but not always, messes this up - and in my experience - only for distribution builds.
Crashing apps generally don't pass that review.
I'm not saying they should have covered for Google, of course. But it's a bit strange.
http://venturebeat.com/2011/07/19/google-plus-iphone-app-lau...
Why exactly? I love google+ and tons of hackers are using it too.
But, yeah, these apps are mediocre. Compare their search app with Dragon Go!, compare Google Plus with Facebook. Heck, Facebook's ancillary Messenger app blows away anything Google's put on any other platform. Why? Far smaller companies with far less talent are delivering far superior experiences on many platforms. The ability of these devices is so great and the tools have advanced so much that having apps of this caliber is like being the company with crappy web 1.0 website well into the 00's.
Apple Employee: thank you, we'll review it and put it up there
.. 2 days later ..
Apple Employee to Tim Cook: boss, this app is crashing a lot, but it's from Google. What should we do ?
Cook: publish it!
I'm happy with the occasional step back when the pace of change is as fast and progressive as Google have accomplished this year.
Keep it up guys.
Keep it up guys.
Judging by their unfortunate string of broken iOS releases, they have been.
1) 1-click archiving
2) stars
3) labels
4) priority inbox
5) aliases
6) spam marking
7) filtering
8) searching through message archives (messages not downloaded to iOS device)
9) drafts
10) proper conversation threading
There are probably a lot more. Those ones came to mind in <30 seconds.
I sincerely hope Sparrow for iOS will address these issues so that I can get push notifications without missing Gmail's best features.
I use Sparrow on the MBP and hope we get Sparrow iOS soon enough.
Seriously though, why hype something one has never used? Egg on his face.
I don't have an iPhone. I'm just going off what I've understood from iPhone users and developers over the years.
The process is in place to make sure that your app is doing what it is supposed to do and is not using any private APIs and stuff like that.
Keep downvoting me; I don't care. I'm asking honest (and I guess dumb) questions.
Sorry, couldn't resist.