Headline FeedsTechNewsWorld Talkback
|
|
See Full Story
A survey of more than 3,600 Appcelerator Titanium developers has revealed that they would rather develop mobile apps for iOS than for Android. iOS led Android by 16 percent in the Appcelerator/IDC Q2 2012 Mobile Developer Report. Fifty-three percent of the respondents believed that iOS was winning in enterprise app development, whereas only 37 percent believed Android was. The survey's numbers for consumer app developers indicated a similar preference for iOS.
Re: App Developers Tilt Toward iOS
Posted by: acebone 2012-07-31 06:59:19 In reply to: Vivian Wagner
I am at Titanium dev, and I gotta say this: It's not surprising that a majority of Ti-Devs prefers to develop for iOS.
Appcelerators definition of 'multi-platform' seems to be: We'll make it work on iOS, and then we'll do a half-assed implementation on Android, just so that we can claim we support that too.
Android bugs just live on and on and on. When I started in sept. last year with Ti, they were at 1.7.0. I started out on a Mac doing iOS, and it was very nice. Soon however an Android-only project came along, and that's when the hurting started. Image-views that can't show images. Small mistakes in assigning refs to Ti objects leads to crashes that have no errormsgs etc ...
In regards to Android, their doc-site should be called a 'spec-site' - because specs are about how things ought to work, while docs are about how things DO work.
Today things are better, but still: I recently made a small app for my self. It plays various sounds. The sound object exposed by Ti of course does not work properly. You cannot change the sound-url of the object once it's created (the docs says you can of course) - in Android the method to do it (setUrl) is even lacking, with no mention of this in the docs - you have to do it by assignment. Still it does not work, and at one point you'll lose playback ability, because you have to keep creating new soundobjects and that drains resources. After a while, when Android itself kills the objects, playback returns.
Also - the workflow with Ti is ... eh ... interesting. Especially so with Android. Right now I have to compile my projects a couple of times before they will run. I do not change any code, coz' it's in the build-system things are fubar. So I just compile two or three times, and sooner or later I can start working. Often I have to restart the entire Ti Studio, because it lost something, and will only compile and install the app, but not run it properly.
In short: If you make a terrible Android experience, and a tolerable iOS experience - what kind of developers will you send away screaming and what kind of developers will you retain? How will the results of any survey look?
I am afraid that Appcelerator will use this survey to conclude that more resources are to be directed towards iOS and less towards Android - which would be awful and not reflect the current state of Ti.
Appcelerators definition of 'multi-platform' seems to be: We'll make it work on iOS, and then we'll do a half-assed implementation on Android, just so that we can claim we support that too.
Android bugs just live on and on and on. When I started in sept. last year with Ti, they were at 1.7.0. I started out on a Mac doing iOS, and it was very nice. Soon however an Android-only project came along, and that's when the hurting started. Image-views that can't show images. Small mistakes in assigning refs to Ti objects leads to crashes that have no errormsgs etc ...
In regards to Android, their doc-site should be called a 'spec-site' - because specs are about how things ought to work, while docs are about how things DO work.
Today things are better, but still: I recently made a small app for my self. It plays various sounds. The sound object exposed by Ti of course does not work properly. You cannot change the sound-url of the object once it's created (the docs says you can of course) - in Android the method to do it (setUrl) is even lacking, with no mention of this in the docs - you have to do it by assignment. Still it does not work, and at one point you'll lose playback ability, because you have to keep creating new soundobjects and that drains resources. After a while, when Android itself kills the objects, playback returns.
Also - the workflow with Ti is ... eh ... interesting. Especially so with Android. Right now I have to compile my projects a couple of times before they will run. I do not change any code, coz' it's in the build-system things are fubar. So I just compile two or three times, and sooner or later I can start working. Often I have to restart the entire Ti Studio, because it lost something, and will only compile and install the app, but not run it properly.
In short: If you make a terrible Android experience, and a tolerable iOS experience - what kind of developers will you send away screaming and what kind of developers will you retain? How will the results of any survey look?
I am afraid that Appcelerator will use this survey to conclude that more resources are to be directed towards iOS and less towards Android - which would be awful and not reflect the current state of Ti.
