June 2009
5 posts
Paperwork Hacks
marco:
With iPhone OS 3.0, Apple introduced in-app purchasing. The idea is that applications can charge for additional functionality (or game levels), content subscriptions, or pay-per-use features.
There are two interesting caveats, though:
An app can only offer in-app purchasing if the app isn’t free.
…
If you want to charge money for your app, you have to jump through a lot of...
iPhone twitter clients and Push
I guess iPhone push notifications might be annoying. But you can always turn them off. This isn’t what worries me.
The biggest problem with this Twitter/push thing is that we’re not going to get it for Twitter apps any time soon. Obviously, Twitter won’t do it natively, it’ll be left for third parties. So some third party will have to run a server that polls Twitter for...
OpenSocial
Tom: seriously, opensocial is one of those 'can be used to solve any problem _except_ problems caused by too much javascript bogging everything down' solutions.
Tom: you just extend the container API with some verbs that describe your service.
Tom: for instance, dopplr public pages with embeddable widgets written by 3rd parties that can get your trip data and display pretty graphs.
Aaron: every webpage a portal
Aaron: OF QUICKSAND
Aaron: OF TIMESPACE
Tom: Also, once you cam EMBED WIDGETS IN OTHER WIDGETS..
Aaron: the web will eat itself
Tom: Actually, I can't even think of a _bad_ use for that.
Tom: it would be a more ELEGANT DESIGN to implement your entire site _as_ an opensocial widget!
Tom: PERFECT
Tom: I will now go looking for VENTURE CAPITAL
Tom: and maybe SLEEP.
Abuse of Twitter reply behaviour
jerakeen: proposal for twitter bot that public announces position changes from, say dopplr.
jerakeen: it just says '@blech has just landed in SFO'
jerakeen: but flags it as a reply somehow (handwave)
jerakeen: so I only see the travel movements of people who I also follow
blech: if you went to its page, you'd see everything, surely?
blech: so it'd have to be opt-in
blech: although depending on how it's fed it'd have to be opt-in anyway
blech: still, kind of a nice idea
jerakeen: sure, ignore the privacy angle
jerakeen: I'm just wondering about clever things you can do with the twitter limited distribution thing
jerakeen: also, note that its utility would be _totally_ dependant on twitter not randomly changing things again
jerakeen: you can design all sorts of clever things using conceptually very fragile bits of 'API'
jerakeen: which twitter can change at any moment.
jerakeen: TWITTER IS NOT INFRASTRUCTURE
jerakeen: etc etc
blech: indeed