4 ms·
This story is moving in three directions at once, none of them very convincing. First, the bulk of this piece reads as an advertisement for Trapster. Second,
by harpastum 18y ago
This story is moving in three directions at once, none of them very convincing.
First, the bulk of this piece reads as an advertisement for Trapster.
Second, he's trying to make money by using advertising in a mobile app? yuck. I can only imagine what that would look like in Windows Mobile (or the 9 other platforms trapster is being built for).
Third, the last two paragraphs of the article come straight out of left field: "it's obvious that developers would have an easier time if their mobile apps could just run in the background." I don't see how this has bearing on my iphone app not being a 'surefire success'. But I digress.
Summary of the article in 75 words or less:
If you try to create a product that has a large critical user base, questionable utility and safety (I'm supposed to be examining maps while driving on the expressway?), and obfuscate your interface with advertisements, "adjust your expectations and strategy accordingly," because money won't magically appear in your bank account. Especially if you're not actually charging for the app.
- diN0bot 18y agogood points, though it is annoying when the "tracking my route, milage and pace while biking" get's deleted because of an errant phone call. perhaps the app could have been saving progress along the way rather than able to run or hibernate in the background?
- cpr 18y agoWhen a phone call comes in, your application delegate gets a notification that you're about to quit; you can save whatever you want at that point, and of course, should, so when you restart the app, it goes back to exactly where you left off.