Re:Show HN: Our first iPhone app, built entirely in JavaScript
by stevenou on Wednesday February 15, 2012 @12:07AM
(#3593109)
Exactly the same sentiment. That's the reason we did not launch with an Android version today. We will probably write it natively when the time comes. Titanium has proven to be a nightmare with Android.
Re:Show HN: Our first iPhone app, built entirely in JavaScript
by grobolom on Wednesday February 15, 2012 @01:01AM
(#3593231)
Boy, do I feel you there. I've been working with Titanium since last March and I've yet to develop some semblance of a cross-platform application. It's a bloody mess in there.
Re:Show HN: Our first iPhone app, built entirely in JavaScript
by skat_et_dieu on Wednesday February 15, 2012 @07:21PM
(#3596819)
Have you looked into the new Enyo framework to deploy apps?
We have built our app ( Icebreak for Couples - http://itunes.apple.com/app/id476063944 ) using Titanium.
When we started building it, Titanium was very very buggy. It has since improved, but still has a lot of really basic stuff that is broken. Their forums have a lot of questions that have been unanswered for over an year.
Our reason for picking Titanium was basically to have an app that is just like a native app on both iPhone and Android without writing the code twice.
We have found out that porting a Titanium app to Android is taking a ton of effort, lot more than we originally thought. I would be curious to hear what the RAVN team has to say regarding their Android version.
Its just not as cross-platform as we thought :(. I would be extremely careful before picking it in the future.
Basically, if you build native apps:
Native App: iPhone=1X, Android=1X. If you want both Android and iPhone: 2X
Titanium App: iPhone=2X,Porting to Android: 0.7X. Total effort: 2.7X
Native Wins.