I was kind of hoping for an article that actually started where this one ends. Since I run a mobile focused startup, I think a lot about what to put your money

I was kind of hoping for an article that actually started where this one ends. Since I run a mobile focused startup, I think a lot about what to put your money (well, time actually) on: PhoneGap / Titanium / native (or simply web browser based). PhoneGap seemed like a wonderful thing when I first started working with it. Even if speed is not an issue, the 300ms click delay is, and so are all the hassles to get around this and around other peculiarities. And that's only when testing on a single platform. Same holds true of course for in-browser apps. So far I found myself spending way too much time on debugging and coming up with workarounds. The problem being that the more freaky you get with JS/HTML/CSS, the less compatible things will get, so the more time will be spent debugging. My current opinion about this matter is: I'd rather spend this time on coding the whole thing twice. This is of course, all under the assumption that Android + iOS support will do. Yes, then there's Titanium. I haven't tried it. But as with PhoneGap, I think that adding an abstraction layer creates a dependency, and this by itself is a downside (which requires justification). I feel that once you're working with native UI, you could just as well work with 'native' IDE & code, because that brings you much closer to the actual system (and benefit from its strong points) and you are not limited to whatever has been opened up for you by the abstraction layer. But I've been coding since I was like 8, and I already worked with Java a lot. So adding one more language seems doable. But perhaps I should try Titanium first before using it. Then again, trying takes time that could also be spent on learning objective C. So, that's basically what I would have liked someone else his/her perspective on, something I miss in the article.