Easiest Apps

[pcslookout]

What is the easiest to make a iOS or Android app ?

Moved from MD&G to Programming
-ViRGE

 

[pcslookout]

I forgot it is for a tablet.

 

[Cogman]

Flashlight apps.

If you are talking platform. They are both comparable. If you can make an app for one you can make an app for the other.

 

[Graze]

Flashlight apps.

If you are talking platform. They are both comparable. If you can make an app for one you can make an app for the other.

When I look at Objective-C I often wonder what the hell is going on there(syntax wise).

 

[nickbits]

Objective c took me a bit to get used to and I consider myself highly proficient in c/c++/c#. But I'm fine with now.
I think ios is easier to work with from an app design perspective. There are only a few screen sizes and that makes things a lot easier for allot of apps.
But if you're good with java it isn't too much to learn to get things going for android.
Both eclipe and Xcode blow compared to visual studio. The ios emulator is a lot better than the android one.

 

[Subyman]

I think for a complete newbie, the Apple platform is a little easier to get started with. The documentation is excellent and everything is well integrated. The up front cost can be more if you do not already have a Mac.

 

[pcslookout]

Thanks everyone.

 

[SearchMaster]

I have found iOS easier and faster overall, but I prefer Java to Obj-C. If your app has any of those annoying little bugs, I've found them easier to track down in Android than iOS. Getting a new view/activity going is faster in iOS.

Getting your app to market is much, much easier in Android. You publish it, it shows up in a couple of hours. With iOS, it can take a week and a half (or more) and they will reject it for spurious reasons. I have an app that is just a tool for my users to help utilize their subscribed service more efficiently, and it was rejected twice by Apple for reasons that were not particularly clear. When I resubmitted the same app as a paid app instead of free, it was approved. I understand their network has costs but my customers should be able to use my program on their iDevices IMO, and I would rather they just come out and tell me that instead of saying my app description doesn't meet their guidelines.

 

[purbeast0]

yeah the apple submission can be a pain in the ass. i've had things rejected multiple times. i had to appeal one because they said my app had to be submitted as a book to their bookstore, even though it was an app with functionality you couldn't even do in a book. then they've had issues with the names of my apps as well even though my previous apps all had the same naming scheme and went through just fine.

i'm working on a small game right now on ios and as much as i've always hated objective c for my past apps, i'm actually starting to enjoy it more now with the game programming. i'm using the cocos2d library for the game. and making games is much different than making apps as far as like non-game apps. i find this much easier to be honest with less quirkiness.

this is the 6th or 7th ios app i'm working on and i'm just now starting to get the hang of the syntax. it's very funky but now it's starting to click.

knowing java much more efficiently than objective c though, i prefer that for sure though. it just feels right, but the whole android activities and what not are not as easy to get up and running as the ios stuff imo.

also, i'm not sure if this matters, but in my personal experience, there is much more money to be made on the ios side than the android side. i make 6-7 times more on ios than android with the same apps on both. it's not like this is a ton of money or anything though since it's a very niche app, but that has been my experience. it will be interesting to see how the game downloads go once i finish it and port it to android though. it's a free game so i'll be curious about how many dl's it gets.