5 ms·
I am facing the exact same decision set in many respects. 1. I have one good app in dev process in a market segment that is hot, Custom HomeScreens 2. I know
by shareme 16y ago
I am facing the exact same decision set in many respects.
1. I have one good app in dev process in a market segment that is hot, Custom HomeScreens
2. I know that I need some more apps, was thinking some quick 2d games via using andengine.
3. I do have some fulltime inquiries that might work
as base income to fund the full 12 month weekend-evening dev cycle.
Pull Tim Bray's recent blog posts on making money in the android market. There also was some recent HN articles on
android dev's making $120,000 yearly with a paired free and
paid approach.
BTW, what dev processes are you using thus far? I am switching to combination TDD and BDD approach using robolectric and robotium/android-mock to take some of the pain out.
- riledhel 16y agothis blog post? http://www.tbray.org/ongoing/When/201x/2011/02/26/Mobile-Money http://www.tbray.org/ongoing/When/201x/2011/02/26/Mobile-Mon...
- shareme 16y agothat is one of them and he has some more in fact..
- makeramen 16y agoDev process? I do what I think my app needs. It's rather 37signals-esque. I was the original user, and that's just how it's grown, other people happened to like it. I only take on other peoples suggested features when they align with what I want out of the app, or when the screaming and yelling from my users gets unbearable. I have no tolerance for bugs, bullshit, or shitty customer support. Emails are answered within a day but usually hours, sometimes bugfixes even come out in less than an hour. I don't unit test, I just write good code ;) Seriously, none of the bugs I've encountered were really unit-testable, so I don't really bother.