Its hard to fairly compare the two because Android is an operating system that runs on multipule machines. The iPhone is just one well refined device.
Market maturaty also has a big impact. People are more acustomed to and know waht to expect from the app store. The Android market is still young. On Jan 17, 1:35 pm, Kevin Duffey <[email protected]> wrote: > Keep in mind there are a number of factors for a less populated market than > iPhone/app store. First.. app store has almost 2 years head start. Even when > there wasn't app store (until 3G came out), people were jail breaking and > building apps for the original iphone. Second, a LOT of developer are both > iPhone and Android.. and have come away with the knowledge of what is pure > crap on the app store. More likely you see less "bad" apps than on app store > right now. That's not to say tho with the ease of development, no > restrictions on apps (for the most part) and lower cost to entry barrier > that you wont see a flood of bad apps sooner than later, but so far it seems > that there are less crap apps on the market. > > Next up is the differences in platforms. A lot of developers, myself > included, realize that Android has quite a ways to go to catch up to the > iPhone capabilities. Presently, it is very difficult if not impossible to > build similar apps. For example, the low latency real-time music apps on > iPhone are top notch... impossible to do on Android right now. High end > games as well are impossible right now. There is an expected Open GL and > Open CL updates along with a JIT coming soon we all hope that will > substantially help Android take off. The JIT will boost performance quite a > bit for most apps, and the hardware level audio and video libraries once > they are part of Android should allow for much more robust/real-time low > latncy games and music apps. A large population of the content on app store > are high end video games.. as I think something like 30% of their sales come > from iPod touch sales... mostly for video games use. I forget the number now > tho..but it was quite a bit. So until Android is as capable, I think you'll > see a lot less high quality games and music apps. > > As well, Android is still new, and only the past couple months has seen > devices of iPhone caliber (moto droid, nexus one) arrive on the market. It > will take some months for developers to really tap all the Android 2.0 and > later features. > > I would give a fair bit of time, maybe another year, before you can compare > fairly the two devices, and by then iPhone will be working on their 5th > version... their 4th, rumored to be a dual-core beast, is due out in a > couple months. > > > > On Thu, Jan 14, 2010 at 9:39 AM, Kenn Lisudza <[email protected]> wrote: > > Thats a really nice good insight. Me particularly being a java developer > > for a while now must agree Android development is quite intuitive. Not to > > say that Objective C is any harder just depends on YOU. > > Well I must say that the android platform (market) isn't well stocked with > > lots of apps like the apple store but with psyched up developers and more > > people getting onto the bandwagon slowly we will get there. > > > On Thu, Jan 14, 2010 at 2:18 AM, Kevin Duffey <[email protected]> wrote: > > >> There are a number of factors I think you run in to for a fair answer. As > >> Danny said, the market is MUCH larger on iPhone...for now. But you run in > >> to > >> some issues... which if you already developed for iPhone you may not have > >> yourself. The primary one being forced to use mac hardware to develop on. > >> The cheapest hardware for Mac is not very cheap and for most of us 1-off > >> developers doing this on the side, most likely out of reach. Therefore, the > >> choice is easy in that case, Android. I suppose it depends on the actual > >> device you own too. If you already have iPhone and can't break contract to > >> grab an Android device.. or don't want to pay either full price just for > >> the > >> hardware, or sign a 2nd contract with Verizon, T-Mobile or Sprint, then you > >> may have to weight that in on your decision. > > >> For me, the other day I read a post on here (or another forum..can't > >> remember) that I already knew, but it sort of woke me up. The biggest pain > >> point of the iPhone for end users is the issue of switching apps. You > >> can't. > >> Any time you launch an app from another, you most of the time can't go > >> back. > >> I think there are a few cases where you can go back to FaceBook from the > >> browser, for example. But most of the time, you have to completely restart > >> the app and often times navigate your way back to where you were when you > >> launched another app. Or, you hit their one "home" button, which > >> effectively > >> closes the app you were running, and start another. Then go back..and you > >> just started it again. Again there are some apps that may save state > >> between > >> runs, I've not found one myself that does this. > > >> I asked my wife... a sort of anti-computer person who loves her iPhone, > >> what her biggest complaint with it was. Without me saying anything to her, > >> she said she hates having to switch to another app because she loses her > >> place in the first app and has to start all over. > > >> I am gong out on a limb to guess that Apple, in their soon to be announced > >> iPhone 4 might address the multi-tasking issue. But if they do, they are > >> either going to have to make the underlying OS do true multi-tasking > >> between > >> multiple apps.. at the risk of potential battery life draining.. or update > >> their SDK and require iPhone 3gs and previous apps to be recompiled to take > >> advantage of say, some new lifecycle requirements in order to work in the > >> new multi-tasking iPhone. I had a hard time understanding the one Activity > >> running while all others are paused situation with Android, but now I > >> understand that is due to battery concerns that this is done. It will be > >> interesting to see if iPhone 4 will offer multi-tasking and if it does, how > >> it handles it. My understanding is the new iPhone will be dual-core with > >> more memory, dual cameras and some other things. We'll find out in April. > > >> I also consider the coding barrier. I did C a long time ago, been doing > >> Java for years. Java to me is far easier to work with than Objective-C, > >> although, to be fair, Android is a ways off from being nearly as capable as > >> iPhone in areas like high-quality video games, high-quality music apps and > >> so forth that you can find on the iPhone right now. But I think the Java vs > >> Objective-C (for most things) is far easier for most to get in to.. and you > >> can pretty much develop and test on any platform. Once you get into NDK > >> native code, it may be a bit more level playing field. > > >> Anyway..that's my .02. > > >> On Wed, Jan 13, 2010 at 11:17 AM, Danny Pimienta <[email protected]>wrote: > > >>> I would say do both. But if youre looking for a bigger audience then > >>> iPhone is the way to go for now. But the Android market will catch up. > > >>> Sent via my Google Android device... > > >>> On Jan 13, 2010 12:14 PM, "gony" <[email protected]> wrote: > > >>> Hi, > > >>> I developed an iphone app about 6months ago and due to time > >>> constraints hadn't managed to write anymore. > >>> I would like to start work on a new app but I would like to consider > >>> developing on Android instead (esp after seeing the announcement of > >>> "Nexus One" in the UK). > > >>> I was hoping that group members would consider sharing their views on > >>> what platform would be best to develop on. > > >>> Thanks, > > >>> -- > >>> You received this message because you are subscribed to the Google > >>> Groups "Android Beginners" group. > > >>> NEW! Try asking and tagging your question on Stack Overflow at > >>>http://stackoverflow.com/questions/tagged/android > > >>> To unsubscribe from this group, send email to > >>> [email protected]<android-beginners%2Bunsubscr > >>> [email protected]> > > >>> For more options, visit this group at > >>>http://groups.google.com/group/android-beginners?hl=en > > >>> -- > >>> You received this message because you are subscribed to the Google > >>> Groups "Android Beginners" group. > > >>> NEW! Try asking and tagging your question on Stack Overflow at > >>>http://stackoverflow.com/questions/tagged/android > > >>> To unsubscribe from this group, send email to > >>> [email protected]<android-beginners%2Bunsubscr > >>> [email protected]> > >>> For more options, visit this group at > >>>http://groups.google.com/group/android-beginners?hl=en > > >> -- > >> You received this message because you are subscribed to the Google > >> Groups "Android Beginners" group. > > >> NEW! Try asking and tagging your question on Stack Overflow at > >>http://stackoverflow.com/questions/tagged/android > > >> To unsubscribe from this group, send email to > >> [email protected]<android-beginners%2Bunsubscr > >> [email protected]> > >> For more options, visit this group at > >>http://groups.google.com/group/android-beginners?hl=en > > > -- > > Kenn Lisudza > > Systems Developer > > Cellulant Kenya LTD. > > > -- > > You received this message because you are subscribed to the Google > > Groups "Android Beginners" group. > > > NEW! Try asking and tagging your question on Stack Overflow at > >http://stackoverflow.com/questions/tagged/android > > > To unsubscribe from this group, send email to > > [email protected]<android-beginners%2Bunsubscr > > [email protected]> > > For more options, visit this group at > >http://groups.google.com/group/android-beginners?hl=en
-- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
