Hacker Newsnew | past | comments | ask | show | jobs | submit | huntergdavis's commentslogin


Yeah I let it expire after the SOPA stuff with godaddy. Doesn't get quite as many hits as you'd expect, but I didn't exactly bend over backwards advertising it either.


Yep, I had a game pulled from the Android app store for using the word 'Pong' in the title. The game was ping pong. "Easy Custom Pong" was pulled about October I believe, so they've been prepping this for a while.


Counterpoint, and like I said on the original post: Within a few days of programming Android I had published a few apps. You just need the App-titude, and the attitude as they say. I'm on day 60 and have done 65 Android apps thus far. Perhaps my live-coding video that was up last week would help? http://www.youtube.com/watch?v=x8bu8nNUZSY&feature=chann...


Why 65 rush jobs instead of few polished apps?

Skillful Surround could be an attractive game if it got some TLC.


For anyone too lazy to read the article, I completed the challenge earlier today.


I actually predicted this about a year ago, and wrote a blog series about how to set one up yourself with generic scripts (later collected into an ebook here http://hunterdavis.com/build-your-own-distributed-compilatio...). It was featured a few times here on HN. Cross compilation can actually be quite speedy, but speed isn't the only reason to use such a machine, especially in a business situation.


Hey Chris,

Good luck! I know where you are coming from. Normally I'd suggest you read my book on the topic (LFF - free on www.hunterdavis.com), but it sounds like you're already over the first hump (saving for the startup). I'm 29, and last June along with a co-founder quit my 9-5 to start www.discursivelabs.com. We've got some upcoming products and some sites in active beta. The best three pieces of advice I would give you:

1. Be open to contracts when they come up. Seriously, just being open to the possibility of contract work and attending appropriate trade shows can get you through the lean times. 2. Betas. Always beta, beta often. Don't rush to go public with your beta. We've gotten so much valuable insight into our product from our beta testers It's staggering the difference in quality feedback between 100 motivated private beta testers and 10000 mediocre public ones. 3. Build your word of mouth with useful information and verify it exists with site analytics. I was lucky in that I had a fairly active community of programmers and hackers reading my personal website, but I had a fairly good number of folks email after a good StackExchange reply I posted. People appreciate useful information, and it's a good chance to mention your product.


I wrote a (fairly) successful e-book on this topic, freely available over at my site.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: