I mentioned in a previous post that we're working on a new App Communications Channel ("ACC"). As you probably guessed, we're not quite going to get it out in June as we were shooting for, but the good news is that we're very close, so I want to give you guys a quick preview.

A lot of your apps are already making good use of the communications tools we've made available so far: our "Post To" functionality enabling apps to initiate user messages, comments, bulletins and blog posts. The goal for ACC is to provide new types of messages that are unique to applications and that have app-specific functionality. The first of these new message types are App Invites. Here's how this new invite will look to a recipient:

Quite a few things to point out here. First, App Invites will appear in a new Mail Center folder called "Notifications". This new folder will also contain other important messages including Comment requests, and there will be specific indicators for all these messages in the Updates box on Users' Home Pages.  Second, the App Invite will include your app picture and allows you to specify the custom text that recipients will see. We think this leads to a much clearer presentation than invites contained in standard messages.  Finally, these new invites allow recipients to add your apps right from the invite itself rather than having to go to the app profile or canvas. Here's what recipients will see when they click "Add..."

This dialogue will appear as a "lightbox" overlay right from the Notifcations inbox, so we hope it makes adding your apps much easier for MySpace users.

So how will these new Invites get generated? As with Post To messages, your apps can initiate App Invites from the Canvas page, but using the OpenSocial requestShareApp method. We'll provide more details in next few days on the exact syntax to use so you can start preparing your code. Here's a view of what the sending user will see after initiating an invitation:

I want to emphasize that the same guidelines we've put in place for existing messages apply just as strongly to App Invites: no incentivizing invitations, no tricking users, no auto inviting, etc. The goal for App Invites and ACC generally is to make app communications clearer and easier for end-users. If that goal is achieved, your apps will spread naturally and effectively. On the other, if users perceive these new messages as "spam" we all lose. To prevent that, we are also limiting App Invites to one recipient at a time initially. Utlimately, though, it's really up to you guys to show that we can utilize these tools responsibly and in ways that bolster the ecosystem.

Finally, now that I've whetted your appetites, I'm sure you're wondering when this cool new stuff will be ready. Be assured your trusty MDP Team is working long hours to get this out, and we expect to have it live in the next couple of weeks. Also, as mentioned above, we'll be providing more implementation details and info in advance.

/Kyle