they're called cops, and you should drive away from them as fast as possible whenever you see one. it also helps if you make a lot of fast turns in the process while still taking into account the locations of any nearby cherries when formulating your route.
@HeartBurnKid: Agent of R.O.A.C.H.: Memers. My friend was so proud to show me the carefully selected fart app he purchased for his new iPhone last month.
@jpaugh: But then the people that authorized it probably get a cut of the earnings of each app sold, so the bigger fool is still the person who buys the app.
@EBone: Nobody knows. Cyanogen is currently working on getting it to those with rooted phones but Qualcomm apparently hasn't released the drivers for it. But nobody knows if Google will do so officially.
@MarcusMaximus: This is what worries me about Android. While many complain about the closed Apple system, since Apple controls the hardware and software, even the older handsets get the new OS (minus a few hardware dependent features like compass).
With so many different hardware-specific tweaked versions of Android, you have to rely on the manufacturer to re-tailor the latest OS to their hardware. What if they decide they just don't want to? For instance, the Motorola Cliq would require a pretty refined upgrade for their custom software overlay. And if the Cliq didn't meet Moto's sales goals, they probably won't bother.
I guess only a *true* Google-branded phone would get all the upgrades. But then again, wasn't the G1 a Google branded phone?
@EBone: The G1 is a Google branded phone. There's also no word yet on just when or if it might get 2.0. I'm not exactly sure why, but for some reason the Droid get early dibs on Eclair. The source code didn't even drop until after the Droid was released.
Earlier this year, Google said there'd be at least 2 new updates this year. For what that's worth, and for whoever that's referring to, we may never know. T-Mobile/HTC haven't said anything for certain about the G1 not getting Eclair, so it may happen yet.
I will say this, though, as annoying as it is that each carrier has to modify it for their own handsets, they at least have the motivation of an lively group of early adopter nipping at their heels. ;-)
Hopefully each manufacturer will take the same approach HTC is and make a single UI for each of their phones, so they don't have to keep retweaking Android for each handset.
Question, what's the compatibility like with iPhone apps and iPod apps. I mean say I loaded Catpaint on to my iPod Touch could I use it with photos in memory?
I'm getting a Touch next Thursday so I'm curious how some apps work without the iPhones extra features.
Really I don't see the iPhone or Android as suitable platforms for commercial development. It's too high volume, low cost, competitive and open to every Tom, Dick and Harry with an SDK. It's fine for big companies to devote some resources to releasing their product on the platform as even if it's unsuccessful they'd be largely unaffected.
For small companies or individuals focusing on iPhone/Android development solely though I don't think it's a wise move. They have limited resources and have to rely on their application staying afloat in an ever expanding ocean. The worst thing is that a lot of the time other developers can just come along and release an app that's similar (and maybe even better) for a lower cost or possibly for free.
My view is that the app market is in a position where if you want to dip your feet in you shouldn't quit your day job to do so. It's just too volatile to risk your livelihood on it.
I feel it. I have a number of applications on the Android Market, and even on the apps that I get good feedback on that I'm charging as little as 99 cents on, I'm not making nearly enough to pay for my time. I love Android and will keep Android as my primary phone platform, but I am thinking of abandoning any hope of ever making a profit on it... meaning that I'll just keep on maintaining what I have but not release anything new.
I do blame Google for not having a for-pay application framework in place at launch. If they did, all app developers would be doing much better right now.
giz- thanks for adding the 'view as a single page' link. no snark or whatever, i really do enjoy reading it that way.. and if you default to the gallery no matter what nick denton gets his precious f'ing pageviews!
11/27/09
11/25/09
11/25/09
11/25/09
11/25/09
11/25/09
So where are the ghosts?
11/25/09
they're called cops, and you should drive away from them as fast as possible whenever you see one. it also helps if you make a lot of fast turns in the process while still taking into account the locations of any nearby cherries when formulating your route.
11/25/09
11/25/09
11/25/09
11/25/09
11/25/09
I am sooo not watching that.
11/25/09
11/25/09
11/25/09
11/25/09
11/25/09
11/25/09
11/25/09
11/23/09
11/23/09
11/23/09
11/23/09
With so many different hardware-specific tweaked versions of Android, you have to rely on the manufacturer to re-tailor the latest OS to their hardware. What if they decide they just don't want to? For instance, the Motorola Cliq would require a pretty refined upgrade for their custom software overlay. And if the Cliq didn't meet Moto's sales goals, they probably won't bother.
I guess only a *true* Google-branded phone would get all the upgrades. But then again, wasn't the G1 a Google branded phone?
11/23/09
Earlier this year, Google said there'd be at least 2 new updates this year. For what that's worth, and for whoever that's referring to, we may never know. T-Mobile/HTC haven't said anything for certain about the G1 not getting Eclair, so it may happen yet.
I will say this, though, as annoying as it is that each carrier has to modify it for their own handsets, they at least have the motivation of an lively group of early adopter nipping at their heels. ;-)
Hopefully each manufacturer will take the same approach HTC is and make a single UI for each of their phones, so they don't have to keep retweaking Android for each handset.
11/23/09
I'm getting a Touch next Thursday so I'm curious how some apps work without the iPhones extra features.
11/23/09
For small companies or individuals focusing on iPhone/Android development solely though I don't think it's a wise move. They have limited resources and have to rely on their application staying afloat in an ever expanding ocean. The worst thing is that a lot of the time other developers can just come along and release an app that's similar (and maybe even better) for a lower cost or possibly for free.
My view is that the app market is in a position where if you want to dip your feet in you shouldn't quit your day job to do so. It's just too volatile to risk your livelihood on it.
11/21/09
I do blame Google for not having a for-pay application framework in place at launch. If they did, all app developers would be doing much better right now.
11/20/09
11/21/09
11/23/09
Unfortunately, Hitler has three million points, but the lightning round is coming up next, so it's still anybody's game!