The application uses Facebook Stream API to publish every "teaser" action on a wall feed. When a teaser is sent, it is published to the friends wall as a feed.
When the reciever replies to this feed, the reply is logged as a comment to the original feed. Similarly when common friends (of sender and reciever) comment on the teaser, the comments get logged to the original feed.
Facebook notifications API helped us solve a technically difficult problem, which was related to privacy of exchanges between friends. Below is a brief description of the problem and how we solved it.
Problem Statement
1. A teaser should be accessible to the sender of the teaser and the reciever from inside the application.
2. A teaser should be accessible to common friends of sender and reciever from inside the application. This is to enable friends to comment on the teaser and make it more interesting.
Technical challenge
Assume a user "John" logs into the application. Presenting the teasers sent or recieved by him is easy as this information is logged in Corners database.
Presenting teasers involving friends of John would require us to get a list of ids of John's friends (using Facebook API), and query for teasers sent and recieved by those ids (in Corners database). This would be an expensive query.
Facebook notifications API came to our rescue. Every action on a teaser is sent as a facebook notification to the sender, reciever and their common friends. These facebook notifications are now available to applications through Notifications API.
When John logs into our application, we present him with the list of notifications from this application. Each notification contains a link to the teaser that originated the notification.
Try teaser application and discover how we used facebook API to convert a simple exchange of information into a social game.
Thursday, September 17, 2009
A new facebook application from Corners
Corners is readying a new facebook application called 'repartee' for release in a day or two. Try it out.
This application uses advance facebook integration API - streams API and notifications API.
The application is a simple fun game involving friends, where friends tease each other, repartee (quick reply), and exchange comments on teasers involving common friends.
The application uses Facebook Stream API to publish every "teaser" action on a wall feed. When a teaser is sent, it is published to the friends wall as a feed.
When the reciever replies to this feed, the reply is logged as a comment to the original feed. Similarly when common friends (of sender and reciever) comment on the teaser, the comments get logged to the original feed.
Facebook notifications API helped us solve a technically difficult problem, which was related to privacy of exchanges between friends. Below is a brief description of the problem and how we solved it.
Problem Statement
1. A teaser should be accessible to the sender of the teaser and the reciever from inside the application.
2. A teaser should be accessible to common friends of sender and reciever from inside the application. This is to enable friends to comment on the teaser and make it more interesting.
Technical challenge
Assume a user "John" logs into the application. Presenting the teasers sent or recieved by him is easy as this information is logged in Corners database.
Presenting teasers involving friends of John would require us to get a list of ids of John's friends (using Facebook API), and query for teasers sent and recieved by those ids (in Corners database). This would be an expensive query.
Facebook notifications API came to our rescue. Every action on a teaser is sent as a facebook notification to the sender, reciever and their common friends. These facebook notifications are now available to applications through Notifications API.
When John logs into our application, we present him with the list of notifications from this application. Each notification contains a link to the teaser that originated the notification.
Try teaser application and discover how we used facebook API to convert a simple exchange of information into a social game.
The application uses Facebook Stream API to publish every "teaser" action on a wall feed. When a teaser is sent, it is published to the friends wall as a feed.
When the reciever replies to this feed, the reply is logged as a comment to the original feed. Similarly when common friends (of sender and reciever) comment on the teaser, the comments get logged to the original feed.
Facebook notifications API helped us solve a technically difficult problem, which was related to privacy of exchanges between friends. Below is a brief description of the problem and how we solved it.
Problem Statement
1. A teaser should be accessible to the sender of the teaser and the reciever from inside the application.
2. A teaser should be accessible to common friends of sender and reciever from inside the application. This is to enable friends to comment on the teaser and make it more interesting.
Technical challenge
Assume a user "John" logs into the application. Presenting the teasers sent or recieved by him is easy as this information is logged in Corners database.
Presenting teasers involving friends of John would require us to get a list of ids of John's friends (using Facebook API), and query for teasers sent and recieved by those ids (in Corners database). This would be an expensive query.
Facebook notifications API came to our rescue. Every action on a teaser is sent as a facebook notification to the sender, reciever and their common friends. These facebook notifications are now available to applications through Notifications API.
When John logs into our application, we present him with the list of notifications from this application. Each notification contains a link to the teaser that originated the notification.
Try teaser application and discover how we used facebook API to convert a simple exchange of information into a social game.
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment