Certainly, I think your point about performance is a very valid one. Adobe Air lacks performance, especially combined with Flex - but I think that's more of an issue with Flash on OSX than anything else.
In my experience, Titanium (which Bowline is built on) has good performance. Certainly they're using all the native APIs on each platform.
Personally, I find coding native trickier than html/js/ruby - but that may just be lack of practice. However, I'm sure you'll agree with me when I say developing and maintaining one codebase, instead of three, is easier.
So, it comes down to developer laziness ;), and here I agree too. However, you could apply the same argument to use of Rails to build a website over C.
It's certainly an argument that's been around for a while. I personally prefer to think of it in terms of efficiency, if being lazy (writing less code) will help me build something faster, I'm all for it. I certainly couldn't code up 3 native apps in the same time as it took me to write that Twitter client.
In my experience, Titanium (which Bowline is built on) has good performance. Certainly they're using all the native APIs on each platform.
Personally, I find coding native trickier than html/js/ruby - but that may just be lack of practice. However, I'm sure you'll agree with me when I say developing and maintaining one codebase, instead of three, is easier.
So, it comes down to developer laziness ;), and here I agree too. However, you could apply the same argument to use of Rails to build a website over C. It's certainly an argument that's been around for a while. I personally prefer to think of it in terms of efficiency, if being lazy (writing less code) will help me build something faster, I'm all for it. I certainly couldn't code up 3 native apps in the same time as it took me to write that Twitter client.