haseman

[citation needed]

I did Brew and J2ME device development before Android. Believe me, I _feel_ your pain.

Since 2003 I've written BREW, J2ME, Blackberry, a smidgen of iOS, and a metric ton of Android. I now write Android software for a living, first for doubleTwist and now for Tumblr.

comment from the end of the bug:

"To all the apple fanboys: the emulator code is open source. Go ahead and fix it yourselves. Apple doesn't provide a multi platform SDK. If I want to develop an app for iPhone I must own an Apple PC. Now, that's messed up!."

Not sure how relevant a question that is. Apple explicitly chose to be on AT&T and no-one else. I'm sure Verizon would have put their phone on the network, just not on terms Apple wanted.

Being exclusive to AT&T was as much Apple's choice as Android's was to be on them all.

Yes I'm sure it impacts adoption rates, but we didn't see a huge rush to the Verizon iPhone. But, as you say, the real test won't come until people's contracts end over the next 2 years.

The conventional wisdom was exactly the same 2 years ago concerning android phones vrs the iPhone. Android has since moved to match the iPhone for market share. The same will probably happen for tablets. It'll just take a few years. I think the android tablets aren't very good right now, but I felt the same way about the android phones when they first came out.

If Google Checkout is any measure, I'm cowering in fear of Google Wallet.

I think I've read this exact article dozens of times since almost since I began writing mobile applications in 2003. The message is always the same 'Web Apps are Coming! They're going to take over! Steve Jobs thought so!'

In reality, we'll probably see something that's half-way between a web-app and a mobile app. In the meantime, can we stop predicting the doom of mobile software and get on with fixing what's broken about it?

Android is always a late bloomer. The G1 sorta, for lack of a better word, sucked. Later incarnations of the devices ironed out a lot of the UX issues plaguing the early Android builds. Don't write off Honeycomb or Moto yet. It's still got a lot of growing to do.

Perhaps that statement came out slightly more hyperbolic than I meant it.

The fact remains that Android's fragmentation is something I deal with on a daily basis. Any time spent fixing issues that crop up on particular phones is time I don't spend adding features to our application. Keeping customers from knowing the joys of fragmentation is one of the things I spend a lot of thought and work at.

As someone who's been working with Android from the beginning, I have to say: About Time.

This is a required step if Google wants the platform to be taken seriously. The only way to keep fragmentation out is to exert a fair amount of control over the OEMs and Carriers who wish to differentiate (or Fragment) Android for their own purposes.

It's going to be a fine balancing act for Rubin. If he pushes the carriers/oems too far, they'll walk. If he doesn't push them hard enough, the platform will disintegrate Java ME style.

Google is using the only leverage they have (early access and the google apps) to make the platform one worth developing for. I, as someone who makes his living doing it right now, am all for this move.

My parents gave me a copy of typing tutor and said "For one hour of video games you need to do 10 minutes of typing." I was a comfortable touch-typest in weeks.

I didn't learn to really hammer out the words until I started dialing into the local collage modem pool to play muds.

lost me at 'login with facebook'

I bought an iPad thinking I'd be able to access my Kindle books from it. In fact, I bought more books on the Kindle system specifically because I could read and sync them across the most number of devices. I'm not saying Apple isn't within their rights to make this move, it just really pisses me off. This is the kind of crap I'd expect from Verizon, not Apple.

This article seems light on facts but heavy with opinion. "My sense is Groupon’s popularity and star power has peaked even though sales may continue to grow for awhile..." That's an interesting theory, is there any evidence to support this?

Further, the headline is misleading, as they're talking only about groupon and nothing about how this might impact the tech economy as a whole.

It's times like these that I wrap myself in Google's neglect for the Android marketplace like a warm blanket.

-Shattered my collar bone and had it screwed back together

-Turned 30

-Proposed to my girlfriend of 7 years

-Got a new job

-Wrote an app that was (briefly) #1 in the paid section of the Android Market

-Moved to New York

It's been a big year for me :-)

I'm fairly sure the fact remains that you cannot, under any circumstance, give up your rights.

I'd just like to quickly define "Fragmentation" from a developer perspective. "Fragmentation" occurs when I have to write code to support oddities on a specific device. Diversity is good. 'Fragmentation' is bad. I think it's an important distinction that's often missed in the constant Is-Android-Fragmented discussion.

You're looking for pattern based AR (unless the words on your paper have precise GPS coordinates)

I haven't look at it much yet, but you might have some luck with the new Quallcom AR SDK.

https://ar.qualcomm.com/qdevnet/sdk

I second the other comment on this thread. Android is still in wild-west mode. Don't give up!

I've totally neglected it (and it's been in rough shape for a while) but I have a functional Geographically based Augmented Reality library. If someone's interested I'd love to hand the reigns of the project over. Right now it's very much in a proof-of-concept state.

http://github.com/haseman/Android-AR-Kit

No problem! Keep writing, we can always use more Android examples.

Please, if you're an Android developer, be very careful with this one. As one commenter on the site mentions...this can chew up a huge amount of stack space. If you want an example of tabbed applications done correctly I'd recommend checking out the source for the ugly but amazingly-well-designed built-in music player. http://source.android.com/source/download.html

I admire your honesty. I find it is, by default, the best policy ;-)

Continue helping (try to get paid) and tell them about the exploit. Even if it's their project your name will still be on their lips when someone else figures it out. Also... being able to sleep at night is nice.

Just came from San Francisco to NY. If you think it's bad here...walk around downtown SF sometime ;-)

Fair point, I guess if a movement to burn the Koran "...contains harassing content or hate speech" I have to wonder what other ideas and writings, in Rackspace's considered opinion, might violate that clause in their TOS? As this isn't a legal or constitutional issue, one presumes they aren't using the legal tests for hate speech/hate crimes. Is this a 'I'll know it when i see it' sorta test?

While I like this in theory (because burning the Koran en mass is a stupid idea) I'm troubled by it in practice. Does this mean that if I espouse on an idea that Rackspace doesn't like they'll pull my service? Obviously this has nothing to do with the 1st amendment... Rackspace may terminate my use of their property by grounds in the contract I've signed with them. I'm not sure, however, I like the idea of a hosting company policing the ideas that are posted on their servers.

An imagined future with no grounding in the present is as useful as an oil rig on a hot air balloon. ;-) Keep inventing the future...but ignore the Luddites at your own peril.