| 8:13 pm on Sep 22, 2010 (gmt 0)|
Good Question jamie - we have been looking at Titanium and would like some feedback on this as well.
Obvously it makes sense to develop once and distribute across multiple platforms - but there must be some drawbacks - either functionality or overheads.
| 2:28 am on Sep 23, 2010 (gmt 0)|
It's more expensive, more risky and more work, but developing the same app from scratch for each platform gives the best results.
| 7:18 am on Sep 23, 2010 (gmt 0)|
maybe you don't get access to all the api functionality which programming in Obj C would allow, but it seems like a pretty good compromise.
if the app you want to create isn't that complicated, why should "creating" an app in titanium be any different to writing a native app?
| 12:50 am on Sep 24, 2010 (gmt 0)|
There's some apps that just need to be written once and then ported, like games and stuff where the experience is self contained within the app and doesn't involve using the UI or the scheme of the platform.
Then, there's other apps that touch upon interface elements from the OS, interact more natively with the OS and are not self contained boxes. This kind of app will benefit from being developed specifically for the platform. You can draw on specific features from each platform and really make your app shine for your users.
If you're making a game, with its own interface and where everything stays within the game, hell yeah, use titanium or one of the many other solutions.
But if your app involves integration with the Ui or specific features of the platform, even other apps, it's best do everything from scratch.
| 11:40 am on Sep 24, 2010 (gmt 0)|
many thanks for explaining harry.
we are aiming at porting some of our travel information into an app. at the moment we'll only need to access gps data from the device. i'll give titanium a go and report back with findings.