TweetDeck CEO: Developing for Android "not a nightmare"

Oh yeah, the shareholders are really worried about their sky-high stock values...

Yeah something like twitdeck isn't a nightmare.. But try developing something like morphwiz or nano studio and have it work on all 3 devices currently offered just at sprint. In this thought experiment, we'll forgive that it's currently impossible to dev anything close on ANY android device..

Oh and first gen ios users.. At this point got them as a hand me down.. Let's hear from slighted ds users whom want to play dsi titles.. Technology moves forward.. The problem with android is that mfr.'s are making obsolete devices in their current lineup vs. 3 year old iPhones and iPods that still get a lot of love from ios devs.

I think this should clear things up.

"only 2 developers" ... lol ... "only" 2 full time developers to port an app that is already finished. ahahahahhaa

"only 2 developers" ... lol ... "only" 2 full time developers to port an app that is already finished. ahahahahhaa

Steve never said it was a nightmare; he just said it was fragmented. I'm not sure why the TweetDeck developers took it the wrong way.

Or, 100% opposite of what you just said.

Maybe the developers of Tweetdeck should focus more on making it more iOS 4/iPhone 4 friendly.

I mean, three months later, and STILL no fast app switching or retina display support? Ridiculous.

(in case my previous comment doesn't make it through)

Dave: That was a random comment on from a visitor to their blog, referencing an anonymous "big company". Nice try.

Developing for Android might not be a pain.

But using it sure is.

Jobs did not make a fool of himself by saying one would need sand paper for smaller devices. In fact he is quite right about it. The problem seems to be that some people seem not to have understood what he was saying and are opening their mouth without thinking.

Why is that?

Because the iPad compared to the iPhone does follow a completely different UI paradigm. When looking at iPhone user interface guidelines and most of the apps, one will notice that content is presented on various screens. One screen per major task. Hence, most interfaces are presented by either tabbars at the bottom or by navigating 'sideways' through hierarchy.

Now... iPad apps are something totally different. They don't work that way and in fact user interface guidelines strongly discourage this approach. The screen is much bigger than the one of iPhones and most of the apps, especially productivity apps do not really feel much like a mobile app but rather like a desktop app because we're presented most of an apps functionality on one screen. Seriously, go and compare. Especially pay attention to the button size on one typical iPhone screen.

Jobs was not saying 7" is too small to use your fingers for navigation reliably. He said that 7" is too small in a tablet context. And he's damn right about that. Because assuming an iPad with applications of the kind we've seen wouldn't be any fun on less than half of the space of a nearly 10" screen, because that's how much space would be sacrificed. Now imagine your favourite iPad app and cover half of your iPads screen with a piece of paper. Now toggle your keyboard... great, huh?

And that's what people need to understand. Arguing the iPhone is much smaller than 7" really shows that you didn't pay any attention to what he was referring to.