I can only assume that there's some desire within Google to make sure the iPhone versions of their products are complete dogshit to try and encourage Android adoption.
Do people think companies really behave this way? "Hey guys, how can we make our products crappier? Surely if people think our iPhone apps stink, they'll be motivated to go out and buy a whole phone from us!"
There are a whole host of mundane reasons why products turn out worse than they could be, and they almost never include conspiracy or malice.
Who told you that? I just launched iTunes on my Lion machine, it started up in 5 seconds and started syncing with my phone wirelessly while I scrolled through 18,000 tracks without stuttering & a track played.
iTunes for OS X is arguably a little bloated and lacking direction, but it's still hands down the best library based music player/jukebox for OS X. Nothing else even comes close.
To be fair, you come right out and say you have little experience on the topic either way, so why cast an opinion? As someone who uses Apple's software on Macs and PCs extensively, there is not even a debate to be had about where Apple puts its effort.
You can even test it yourself. Take any Mac, put Windows 7 on it. Launch a clean copy of iTunes in OS X, then reboot and do the same in Windows 7. The OS X version will start up instantly, the Windows one will stall for at least 10-15 seconds. This is just one obvious example, there are plenty more out there.
An interesting anecdote from the Steve Jobs biography:
Finding Nemo had just been released to critical acclaim and Pixar were in renegotiation talks about their deal with Disney.
(Disney's) Michael Eisner had one powerful trump card. Even if Pixar didn't renew, Disney had the right to make sequels of Toy Story and the other movies Pixar had made, and it owned all the characters from Woody to Nemo. Eisner was already planning -- or threatening -- to have Disney's own animation studio do a Toy Story 3, which Pixar had declined to do.
The threat had teeth not because Pixar would lose control of some of their characters, but because Disney's animation studio had been releasing flop after flop. After ten years of The Lion King, Beauty and the Beast, and Aladdin, there were ten years of rubbish. As a company, Disney had been creatively brain-dead for a decade.
(Pixar's) John Lasseter was aghast at the prospect of breaking up with Disney. "I was worried about my children, what they would do with the characters we'd created," he recalled. "It's like you have these dear children and you have to give them up to be adopted by convicted child molesters."
Effectively, Disney's negotiation tactic was "re-sign with us, or else we'll spin up a shitty division to make shitty sequels of your movies!"
That's from Pixar's perspective.
From Disney, it was more like this: "re-sign with us or we will utilise out right to produce sequels, for which you won't be paid"
ie, It wasn't a threat to do a bad job - as the parent comment says, companies (almost never) deliberately do bad work.
Eisner might not have been thinking 'shitty', but I bet he was thinking similar things when approving The Return of Jafar. (http://www.imdb.com/title/tt0107952/)
That poster could only have been made to intimidate Pixar.
Come on, hasn't everyone had to work on a project where the boss/manager didn't want it to succeed? Whether for political, personal, or boredom, people don't do their best work all the time. Not everyone is as demanding as Steve Jobs.
I find it interesting that Google is intentionally using its own icons for pre-existing iOS conventions (Floppy disk for save, weird action menu, nonstandard trash can, buttons without borders, etc.) I can understand being in love with your own system, but making a native app look non-native is just odd.
Personally, Google Sync/Exchange works great, gives me calendars as well, and plays nicely with my other accounts. The only hiccup is archive v. delete, but that's not a huge one. I've had no desire for a GMail app.
* freezing irrecoverably when opening the app/going to inbox very often
* losing all the text you've typed when anything causes the textfield to lose focus
* things like gaining network connectivity causing said textfield to lose focus
Perhaps this qualifies as ad hominem, but this experience was biblically awful and from a major software company. Seeing how this new Gmail app is a bunch of Web views and needlessly non-standard widgets (=> part of the worst dredge of apps), it makes me start to feel pretty cynical about their iOS strategy.
Then again, taken the experience using the Android browser while developing mobile websites, maybe it's an institutional inability to develop polished mobile applications.
EDIT: I don't really know why I'm being downvoted for this. Wouldn't you switch apps too if you relied on google voice for your text messages and you couldn't log into it anymore without it instantly crashing?
The Android version is far better, though, due to its OS integration. I don't think Apple would ever allow what it does on Android.
http://stackoverflow.com/questions/2452086/no-valid-aps-envi...
This is a problem with Apples review process as much as anything else, since you can't test the properly signed release version of the app until you publish it to the appstore for all to see.
2.1 Apps that crash will be rejected 2.2 Apps that exhibit bugs will be rejected
It is indicative of a larger problem I have with the App Store. I am not a fan of requiring a review process. But once you crossed that bridge, make it a damn good and tough review process. The amount of crap that gets through is amazing. You already pissed off people who don't like apps getting Apple's approval, you might as well crack skulls and make sure there is real quality in every app.
There may be no additional value to nerds like you and me, but there are plenty of normal people who want GMail on their homescreen and want to get it from the App Store.
I'm not sure this is still the case in iOS5.
Having a JIT requires you to execute writable memory which is a privilege given on a per-process level. So for an embedded webview to be able to do it, your app would need it, but third party apps are never allowed this.
It's possible that they changed UIWebView to spawn a background process for the actual rendering, but I guess we would have heard about that (we haven't we only heard about homescreen links now being JITed)
Trying to mark memory as executable will cause your app to be terminated. Jumping into non-executable memory will also cause your app to be terminated.
Aside of protecting you (as a user or as a developer) from a big class of security issues, this also ensures that nobody ever gets to run code that's not loaded from the App Store (and thus would generate revenue without giving a share to Apple).
It still is. The JIT was enabled for "pinned" web applications (added to the home screen), but for the JIT to be enabled the whole process needs to be allowed to execute code from writable memory. There's absolutely no way Apple is going to allow arbitrary applications to do that.
As pilif notes, a workaround would be to have UIWebView's content exist in a separate, JIT-able process.
Because Safari gets to JIT-compile JavaScript and UIWebView embedded into apps can't, this actually feels slower than the website (~0.5 seconds between clicking on a message and seeing it load? really?)
I really think I'll move back to using their Exchange-Sync for push together with the standard web shortcut for mail management as this is faster and supports multiple accounts.
(edit) On a related note: Doing these "let's add a native toolbar to my website and publish this in the AppStore"-apps feels nearly as stupid as when everybody felt the need to add flash intros to their website. There's next to no additional value (especially with the currently broken push) provided by such a half-assed pseudo-native app.
This does nothing but hurt both native development (by leaving a bad impression on what's possible with native apps) and the open web (by making people believe that a website is not good enough)