haseman

6 ms·

1.
by haseman 15y ago
[citation needed]
2.
by haseman 15y ago
I did Brew and J2ME device development before Android. Believe me, I _feel_ your pain.
3.
by haseman 15y ago
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.
4.
by haseman 15y ago
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, t
5.
Sales requires trust, especially in the Android Market(haseman.tumblr.com)
2 points by haseman 15y ago|0 comments
6.
by haseman 15y ago
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'
7.
by haseman 15y ago
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 t
8.
by haseman 15y ago
If Google Checkout is any measure, I'm cowering in fear of Google Wallet.
9.
Show HN: A full time Telecommuter's typical day(haseman.posterous.com)
2 points by haseman 15y ago|0 comments
10.
by haseman 15y ago
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'l
11.
by haseman 15y ago
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
12.
by haseman 15y ago
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
13.
by haseman 15y ago
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 contr
14.
by haseman 15y ago
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
15.
by haseman 16y ago
lost me at 'login with facebook'
16.
by haseman 16y ago
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 withi
17.
by haseman 16y ago
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
18.
by haseman 16y ago
It's times like these that I wrap myself in Google's neglect for the Android marketplace like a warm blanket.
19.
by haseman 16y ago
-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
20.
My take on Android and Fragmentation: It's a problem, but not the way you think(developer.com)
2 points by haseman 16y ago|0 comments
21.
by haseman 16y ago
I'm fairly sure the fact remains that you cannot, under any circumstance, give up your rights.
22.
by haseman 16y ago
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 importan
23.
by haseman 16y ago
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
24.
by haseman 16y ago
I second the other comment on this thread. Android is still in wild-west mode. Don't give up!
25.
by haseman 16y ago
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
26.
by haseman 16y ago
No problem! Keep writing, we can always use more Android examples.
27.
by haseman 16y ago
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 check
28.
by haseman 16y ago
I admire your honesty. I find it is, by default, the best policy ;-)
29.
by haseman 16y ago
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.
30.
by haseman 16y ago
Just came from San Francisco to NY. If you think it's bad here...walk around downtown SF sometime ;-)

More ›