I agree with all that - whilst I've referred a few times before to the concept of a "distributed app store", I probably haven't been clear that I meant it in terms of the infrastructure - a way of connecting the 1000s of different apps together and presenting them in a uniform way, without that necessarily involving a full app store environment where users can purchase and checkout etc. I think an API focus is very much the way to go, leaving the community to decide how to make use of the data. Time and time again businesses and projects have found that the best use of their platform has come from third parties in ways they never envisaged, and we definitely want that to be the case here.
So in this respect I don't see
app.net as immediate competition. However, in encouraging developers from all platforms and devices to use their platform as a landing page for their apps they are doing the same as we will be doing, albeit with different objectives. So in this respect they are competition and we will need to make sure we clearly spell out the benefits of .app in this respect, and that developers (and search engines) can clearly distinguish the two projects.
There's also the fact that there's every chance
app.net will seek to offer a similar API in the future and/or engage the community more, which would bring them closer in line with .app's objectives.
At this stage I don't think we need to care too much about what they're doing. But I think it's useful to have on our radar.
Luke
http://lukebennett.comTwitter: @developerluke