News for hackers. Stuff that matters.
Re:How much did Twitteriffic for iOS cost to develop? Craig ... by danilocampos on Wednesday October 13, 2010 @04:19PM (#1788702)
It's actually a bit harder to create an Android app of comparable quality, isn't it?

Apple gives you a boatload of really thoughtful, usable UI classes. What I've read is that Android's SDK UI code isn't nearly as substantial or mature. Can you confirm if this is the case?

edit: Then there's Core Data for object modeling and persistence, which is a huge time saver. Is there an Android analog of this with comparable power?

Re:How much did Twitteriffic for iOS cost to develop? Craig ... by yish on Wednesday October 13, 2010 @04:44PM (#1788822)
The other challenge is developing for all the variants on Android (OS version, different manufacture idiosyncrasies, hardware speeds, screen resolutions, orientation, virtual vs hardware keyboard) all increase the development time and especially the QA time on Android.
Re:How much did Twitteriffic for iOS cost to develop? Craig ... by gte910h on Wednesday October 13, 2010 @04:26PM (#1788733)
Mobile developer here: Most definitely android is costlier to produce feature for feature than iOS.
Re:How much did Twitteriffic for iOS cost to develop? Craig ... by jlmendezbonini on Wednesday October 13, 2010 @06:34PM (#1789160)
Can you elaborate? You develop for which platforms (iOS, Android, Symbian, etc)? What type of software (games, utilities, etc)? Thanks
Re:How much did Twitteriffic for iOS cost to develop? Craig ... by jrockway on Thursday October 14, 2010 @12:55AM (#1789880)
Android is costlier because designers don't like Google's widgets, so every Android app (that involves a "designer") makes their own instead.

This results in shitty apps that are costly to develop. Fortunately, most of the apps that people actually use don't do this, so it's not really a big deal for users.

Re:How much did Twitteriffic for iOS cost to develop? Craig ... by gte910h on Thursday October 28, 2010 @12:55PM (#1843685)
Android is costlier to produce because:

The API's have more gotchas and simple bugs than the Apple ones.

The 1.6 API in particular has some hairy bugs.

The debug cycle takes considerably longer (almost 3x as long as the iPhone debug cycle for a non-media app).

The debugger doesn't work as well.

The lack of a GUI UI layout tool (there are some, they don't work well yet).

The project setup is considerably more time intensive (barring signing issues, which experienced iPhone shops don't have issues with really).

Now it's not all against android: The lax approval criteria and ease of market publications are awesome. I'm just saying it costs MORE to do android, I'm not saying don't do it.

And yes, you're right, custom widgets are harder in android than in iOS. If it makes you feel better, I find the amount people change iOS custom widgets silly too.

Re:How much did Twitteriffic for iOS cost to develop? Craig ... by gte910h on Wednesday October 13, 2010 @11:08PM (#1789683)
iOS, android, typically media centric applications, never games.
Re:How much did Twitteriffic for iOS cost to develop? Craig ... by Skroob on Wednesday October 13, 2010 @04:32PM (#1788753)
I can't speak to Android SDK's maturity, but I can say that the foundation of the iOS SDK has been around a long time. All our Foundation classes are still prefixed with NS. Almost all of the most basic stuff, and even a lot of higher level stuff as well, has come over from MacOS X and NextStep before that.
Re:How much did Twitteriffic for iOS cost to develop? Craig ... by danilocampos on Wednesday October 13, 2010 @04:38PM (#1788794)
Yeah, OS X is an enormous, and often underestimated asset of Apple's. Put them on great footing from the very iPhone SDK.

On the NS prefix: Lots of fun to switch between iOS and OS X dev. Wrote my first OS X app a couple months ago and it was weird to stop using the UI prefix for all the view classes.

My big wish for the next major iOS SDK is to get bindings. Those are awesome on the desktop.

Re:How much did Twitteriffic for iOS cost to develop? Craig ... by jsolson on Wednesday October 13, 2010 @05:59PM (#1789066)
> My big wish for the next major iOS SDK is to get bindings.

I wouldn't expect this. Honestly I'd expect things to go the other way: 10.7 maybe deprecating bindings on the Desktop for things like table and outline views. Particularly since they added NSTableViewDataSource/Delegate and NSOutlineViewDataSource/Delgate in 10.6.

Re:How much did Twitteriffic for iOS cost to develop? Craig ... by danilocampos on Wednesday October 13, 2010 @06:19PM (#1789122)
Really? With bindings you get to write so much less glue code for labels, button states and other UI widgets. It's a dramatic time saver for UI minutiae.
Re:How much did Twitteriffic for iOS cost to develop? Craig ... by jsolson on Thursday October 14, 2010 @01:45AM (#1789955)
I actually do like them for labels, button states, and other what I'll call "scalar" widgets.

For collections, though, I feel like they're more likely to get you into trouble than to actually solve your problems.

I think you could do something substantially less complicated/powerful than bindings for the cases that bindings handle well, though, and I'd rather Apple did some innovating there than bring bindings over to iOS.

I'm also with the other folk who would much prefer to see Garbage Collection first. I rarely get into trouble with the reference counting system, but when I do it usually takes me forever to track down why my app is crashing without a single line of code written by me in the stack trace. Usually it's because I assigned an autoreleased value to an ivar in an init method while failing to retain it (a stupid mistake that I still make once every few months even after 5 years of Cocoa/Cocoa Touch work).

Re:How much did Twitteriffic for iOS cost to develop? Craig ... by Zev on Wednesday October 13, 2010 @07:51PM (#1789330)
I've never found myself wishing for bindings on the iPhone. Maybe when I'm using Core Data, but thats not too often. And even then, its relatively easy and quick to abstract it all away.

I want GC on the iPhone. Not for the GC itself, just so Apple will make NSPointerArray, NSHashTable and NSMapTable part of the public API.

Re:How much did Twitteriffic for iOS cost to develop? Craig ... by bonaldi on Thursday October 14, 2010 @11:55AM (#1791356)
I have seen bindings running on iOS, and it has massive potential, especially for areas like live updating of on-screen table rows etc. Fully expect them there soon.

Will be astonished if they get deprecated on desktop, too. Value is far too high.

Re:How much did Twitteriffic for iOS cost to develop? Craig ... by Skroob on Wednesday October 13, 2010 @04:45PM (#1788828)
Yeah I took on a short Mac project a number of months back and got really messed up with the switch. The ubiquity of Core Animation on the iOS was what spoiled me I think. Don't hold your breath for bindings on iOS though. I'd rather have garbage collection anyway.
Re:How much did Twitteriffic for iOS cost to develop? Craig ... by sudont on Wednesday October 13, 2010 @06:02PM (#1789075)
I'm sure garbage collection's on the way with the increases in processor and memory in iOS devices.

Lack of GC seems to be an artificial constraint designed to force dev's to take charge of a situation with very limited memory. Unless there was some major overhaul to the Foundation classes.

Am I way off?

Re:How much did Twitteriffic for iOS cost to develop? Craig ... by nimms on Wednesday October 13, 2010 @08:06PM (#1789355)
I'd think it also has to do with battery life. Especially with long running apps.
Re:How much did Twitteriffic for iOS cost to develop? Craig ... by guelo on Wednesday October 13, 2010 @05:33PM (#1788985)
I can't really say whether Android is harder, but I think Apple's tight design guidelines make the design easier if you're using the default built-in controls.