tmgrhm

The screen size looks wrong because the app is running in pillar box mode — it's only been compiled to run for 640x960 screens (i.e. iPhone 4S and older).

The keyboard is iOS 6 styled because the app hasn't been compiled for iOS 7.

Nothing out of the ordinary here.

>IMHO, feed reading should be integrated into the browser as a tab, not in the hands of commercial interests.

This is a really interesting idea. Has there been any talk in Chrome development about building a browser-side RSS reader? Google would still get all the information they get from Reader now but they'd be making the 'feature' exclusive to their browser. This coming not long after Apple removed their feed managing ability in the web browser, meaning they could get a load of Chrome converts on OS X just from that.

It'd be really interesting to see what happened if browser-side RSS became "the thing" again. Although, as julien pointed out, doing it browser-side doesn't necessarily mean your RSS isn't in the hands of a commercial interest.

There is none — the title is misleading linkbait. The article only mentions Apple twice, and even then it doesn't explain what "Apple's poisonous touch" has to do with GNOME 3 being almost universally disliked — or as the title puts it, "killed" (which is also completely untrue).

Minecraft isn't as popular as it is because it's the result of brilliantly-written Java; it sells so well because it's a brilliant concept.

Or, if on iOS 5, just go into Settings > About and change it in there.

The only technical limitation I can think of is the one which exists server-side. Siri has been having troubles from time-to-time with just iPhone 4S owners polling it. Imagine if all iPhone 4 (and even 3GS) owners were trying to use it too.

For some reason I didn't even consider that you could control it via normal text input, but you're obviously right as that's what Siri will eventually use after the voice-recognition software is used. This totally widens the possible market then, you're right.

I think the main bottleneck at the moment though (and why Siri was limited to the iPhone 4S even though the 4 and 3GS run it perfectly) is due to server load. They simply don't have the infrastructure to handle all the requests.

It wouldn't be competing directly with Google though, would it? Siri offers a limited range of functions (currently, though this will inevitably widen as Apple makes more modules (and possibly opens it up to third parties)) whereas Google indexes (almost) everything on the web and searches by text.

I agree though: due to its nature of remotely processing input, Siri could become a search engine accessed via a web browser assuming the computer has a mic (which most current Macs — especially the biggest-sellers, MacBooks — do). It would become a single interface for accessing dozens of services — like Wolfram Alpha and Yelp — and tapping petabytes of information.

>It would seem a full 50% of gruber's readers replaced their ipad's with the ipad 2.

What does Gruber have to do with this? Do you mean Marco?

>I hope that iOS 5's OTA updates we could get to the point where iOS versions older than a few months are considered obsolete.

While a very nice idea, I'm not convinced it much will change due to old hardware being incompatible with new versions of iOS. It's rarely the x.y versions which are the barriers to progress, but the x.0 versions.

As a designer (and soon-to-be programmer) I totally agree that iteration is key. Iteration is so important to producing a polished product with the best possible aesthetics and experience.

However, I really do not agree that the right approach is to not think about the best possible design beforehand. Ramming your fingers in there and fumbling around blindly is a terrible idea. Think beforehand about the best possible solution and then repair and iterate on that.

I'd hazard a guess at saying this was a 20% project and the individual is the engineer who led (or was sole member of) the project.