News for hackers. Stuff that matters.
Re:Why you should (not) create a mobile app by programminggeek on Wednesday June 29, 2011 @11:17AM (#2709755)
You could probably apply much of this logic to building a webapp or native app for that matter. The rules all apply everywhere, it is just a matter of how mature the market is.

Mobile is still new. Tablet is VERY new. Motion/kinect is basically nonexistant. So, understanding where the market is should change the way you target it.

Launching an app on the app store is probably akin to launching a blog in 2002-2005. There was competition, but it was still relatively little compared to now, but there was still enough competition that you had to hustle to get noticed. Launch a blog now and nobody cares. You have to make them care.

If you think pushing an app is hard now, wait 5 years.

Re:Why you should (not) create a mobile app by salbright on Wednesday June 29, 2011 @11:32AM (#2709809)
Good article.

While I don't follow the app market that closely, it seems as if all of the new apps I see aim to enhance very specific functions of human life. Five years from now, with a mature market, seemingly just about every moment of my day could be enhanced by the use of a mobile application.

When this time comes, how am I suppose to organize and manage all of these applications? I have enough going on in my life without having 500 different applications to manage. Are any companies working toward aggregating related applications to create "definitive" applications?

For example, I play guitar. I don't want to have 50 different apps for tuning, techniques, music theory, etc. I just want a single "definitive guitar app" that covers everything. The same principle could be applied to daily functions across the board.

Who's doing this?