Common App Rejections

Re:Common App Rejections by jn4 on Sunday August 31, 2014 @08:40PM (#8251029)

There is rightly a consensus that iOS Apps are generally better than Android Apps.

IMO this is mainly because of the iOS SDK/Xcode and not due to the App Store review process.

The review system is geared for consumer focused apps. Business Apps need specialized domain knowledge and complex setups to review. That is why there are so many consulting firms doing this for clients.

The review process currently just drains some resources but may really start hurting the iOS ecosystem when business Apps become the driver for mobile platform choice. It already is in the developing world because for many, the phone is their only computer.

A user may really want to use iOS, but if my key problem is solved by an Android only App - I will need to use Android.

This is one of the reasons why we ended up with Windows dominating.

iOS now has a robust sandboxing and an excellent permission system - so the risk of an App doing harm is low. All apps without in-app purchases should be automatically approved. Approvals can always be revoked later if issues surface.

[ Parent | on HN ]

Re:Common App Rejections by cageface on Sunday August 31, 2014 @11:14PM (#8251360)

In my experience this is less and less the case. I think it's largely a function of developer effort. In fact, at this point I consider a number of apps (WhatsApp, Wechat, Zalo, Viber, Twitter, all of Google's apps) to be more usable in their Android incarnations than they are on iOS. This is partly to do with the greater degree of platform integration Android allows and, I suspect, the fact that it's just harder to introduce crash bugs in Java than Obj-C. Text entry on Android is currently vastly superior thanks to Google's very good stock keyboard and the plethora of excellent third party keyboards.

iOS is clearly ahead when it comes to anything having to do with multimedia but for a very large class of apps these days it's either a tossup or a win to Android. iOS 8 will probably close the gap to some degree because it allows devs to hook into the OS to a degree that was never possible before but I also expect Android apps to improve now that people can afford to ignore 2.x and the baseline for cheap phones has been raised by the Android One program.

[ Parent | on HN ]

Re:Common App Rejections by gurkendoktor on Monday September 01, 2014 @03:17AM (#8251825)

> it's just harder to introduce crash bugs in Java than Obj-C

I am not convinced. ObjC pointers are a lot safer than C pointers under ARC, and sending messages to nil won't even crash. It's almost more likely to have bloody AutoLayout crash your app :)

[ Parent | on HN ]

Re:Common App Rejections by deong on Monday September 01, 2014 @10:07AM (#8252863)

ARC is still awfully fiddly. Between all the bridging casts that are often necessary and the interaction with strong/weak/etc. modifiers you can put on properties, it's really easy to crash or leak memory with ARC. It's an improvement I guess, but I'm not sure it's much of one, because it lulls people into thinking they don't need to understand the underlying reference counting.

[ Parent | on HN ]

Re:Common App Rejections by gurkendoktor on Tuesday September 02, 2014 @04:01AM (#8256276)

I agree that it's terrible in theory, but it I've rarely had a memory bug slip into the App Store. Would love to see statistics from HockeyApp or others on reasons for app to crash.

I've only found statistics about the number of crashes: http://www.forbes.com/sites/tomiogeron/2012/02/02/does-ios-c...

[ Parent | on HN ]