Quote (AName2 @ Aug 22 2013 01:48am)
Let me rephrase that...why would you want to avoid native development?
yeah, that's what i was referring to. i'm not saying you should always avoid writing native, but rather that there are times you might wanna look at alternatives. it can seem unintuitive but you might not always want best performance above all else. if you can get acceptable performance and you have the features you want but reduce the cost, that might be the better choice. instead of making 2+ separate apps (1 for iphone 1 for android 1 for xyz), you can save a lot of time writing something cross-platform. much more beneficial if you're making a lot of changes over time. and it makes even more sense if the performance loss doesn't lose revenue, eg internal business app. if it's public facing on the other hand, your goals might change since users will shy away if there are better alternatives.
but if android is the only os you'll ever target or you need very specific features/performance, then native is prolly the way to go.
This post was edited by carteblanche on Aug 22 2013 06:28pm