News for hackers. Stuff that matters.
Re:Which Platform You Should Target For Your First App: Andr... by j2labs on Tuesday December 25, 2012 @08:05AM (#4965901)
It's simple: if you intend to sell the app, build first for iOS. If the app isn't something users will use daily, just use HTML. If neither of those are true, build for Android and iOS with iOS first.
Re:Which Platform You Should Target For Your First App: Andr... by kashif on Tuesday December 25, 2012 @08:39AM (#4965949)
How did you deduce this?
Re:Which Platform You Should Target For Your First App: Andr... by j2labs on Tuesday December 25, 2012 @08:49AM (#4965968)
iOS users buy apps 6x as much as Android. The article itself says that.

HTML is fast to develop relative to native apps therefore if the app is ideally used infrequently, a native experience isn't worthwhile. There are exceptions, of course.

The last option is just a default last option.

Re:Which Platform You Should Target For Your First App: Andr... by mtgx on Tuesday December 25, 2012 @09:10AM (#4965996)
That data is from mid 2011. The difference should be much smaller now, if there is any. Android had like 150-200 million devices back then. Now it has over 500 million.

This is why this article is BS, because most of the data used in it is extremely irrelevant for the Android ecosystem right now. This article should've been written in 2011. Not at the end of 2012. The Android ecosystem has grown and improved a lot since then.

Re:Which Platform You Should Target For Your First App: Andr... by jacquesm on Tuesday December 25, 2012 @10:00AM (#4966105)
The difference is still huge, to the point that there are still plenty of companies that ignore android simply because they can't monetize on it.
Re:Which Platform You Should Target For Your First App: Andr... by j2labs on Tuesday December 25, 2012 @09:45AM (#4966071)
Can you share data showing otherwise?

Here's an article from a few weeks ago supporting my claim: http://m.guardiannews.com/technology/appsblog/2012/dec/04/io...

Edit: to clarify, Android is doing better, but it is still no match for iOS.

Re:Which Platform You Should Target For Your First App: Andr... by drivebyacct2 on Tuesday December 25, 2012 @10:32AM (#4966177)
I want to know how many of those apps replace basic functionality that is just built into Android. There are am absurd number of paid apps and services that have no purpose on android because the functionality is built into the OS or the Google Apps.
Re:Which Platform You Should Target For Your First App: Andr... by j2labs on Tuesday December 25, 2012 @10:38AM (#4966195)
Interesting point. Could you elaborate?
Re:Which Platform You Should Target For Your First App: Andr... by Ologn on Tuesday December 25, 2012 @01:08PM (#4966562)
"HTML is fast to develop relative to native apps"

I know how to write HTML as well as Android XML or Dalvik (Java) code. I do not see where pounding out HTML code is faster than say pounding out Android XML code.

The only thing fast about it is theoretically you can use it on both Android and iOS. Most companies go native. Facebook tried doing this before running into massive problems and going native.

I also do not see what the frequency of app usage has to do with anything. I might have two app ideas - one used once a month by 60 million people, another used daily by 2 million people. If they are ad based, they will both probably bring in the same amount of money. Why should I go native on the 2 million app but not the 60 million app?

Re:Which Platform You Should Target For Your First App: Andr... by j2labs on Tuesday December 25, 2012 @02:29PM (#4966850)
Comparing html and xml is silly. They are basically the same.

Platform independence was the point.

If people use the app daily, it's worth going native for the better performance.

Your example about 60m vs 2m is intentionally engineered to be an exception and I said there are exceptions.