Re: The First College Hockey iPhone App!
Not sure why I'm even bothering to reply, but I will anyway.
"Program in Linux"
Linux is a operating system. Well, really a kernel that many operating systems use, not a programming language. Android apps are programmed in Java, which I am more than capable of programming in, but it's clunky, awkward, and tends to be everything that modern programming languages abhor. I, and plenty of other programmers, hate Java. So, yes, I choose not to do it (I don't think I've ever implied otherwise), not because I can't, but because I simply don't want to. I would prefer to spend my time making the iPhone app better than tackle an Android version. Besides, that would be twice the code to maintain and, at least right now, I just don't have time for it.
"this belief you (and other Apple Snobs) have that Android is teeny tiny and no one uses it is ridiculous"
Where exactly did I say anything even remotely close to that? I said it was a "fragmented hardware base on the wild west of operating systems." I'm fully aware of how many Android devices are sold. The problem is there are, what, a couple hundred different Android devices out there? And each manufacturer and carrier is free to customize the Android OS to suit their needs, often installing different versions across models within a brand or carrier. Plus, Android's rapid development means you have a wide range of OS versions across the install base, so in the end you have no idea what you're ultimately deploying to and it sounds like a nightmare to support. Android outsells iOS and has a bigger install base, but it comes at a price.
"My guess is with Androids open source you could put together something rather quickly anyways"
Your guess would be wrong. I have a friend who recently finished his PhD, was looking for something to do, and wanted to give an Android version a whack. I gave him my source code to play with and access to the data I'm parsing (since, you see, iOS developers are also very open and willing to help). He got very (very) basic functionality working, but pretty quickly came back to me and said, "Man, you've done a lot of work on this." And therein lies the rub. I could reasonably-quickly throw together something for Android that might work but would suck, but that's not how I roll. I spent untold hours shaving milliseconds off functions, making the memory footprint as small as possible, and optimized the data delivery to use as little data as possible. If it's not worth doing right, it's not worth doing.
See above, re: snap.