|
|
The documentation in this wiki has been arranged in a series of tracks, grouped by the style of development they describe. Depending on what type of application you want to write, one of the following patterns should fit your needs.
A social mashup is a lightweight OpenSocial application which runs inside of a social network. Because such applications do not rely on a server, they typically scale extremely well but may be limited in terms of data storage and/or processing. A social mashup is typically created using HTML, JavaScript, CSS, OpenSocial Templates, and/or Flash.
|
The Social Mashup Tutorial will walk you through creating a simple application from start to finish. |
|
A social application runs inside of a social network but relies on an external server for processing and rendering data. These applications can provide advanced functionality but may run into scaling problems when they become very popular. Social applications can be created using a variety of technologies, including HTML, JavaScript, CSS, OpenSocial Templates, Flash, PHP, Python, Java, Perl, .NET, or Ruby.
|
The Social Application Tutorial will walk you through creating a simple application from start to finish. |
|
Social websites and social mobile applications run outside of social networks but consume social data through REST or RPC APIs. Users of these apps can grant access to their data using 3-legged OAuth without needing to add an application on a social network. This design pattern grants the most flexibility - almost all languages and platforms can take advantage of this data.
|
Here is a list of the articles available on this site, grouped by category.
Building a complete social gadget from start to finish. |
|
Write a simple gift giving app using OpenSocial templates. |
|
Write a gift giving app which relies on an external server. |
|
Write a gift giving website which allows users to log in with OpenSocial accounts. |
Learn the basics of writing OpenSocial-based gadgets. |
|
Fetch social data from inside a gadget. |
|
Read and write persistent data without needing a database. |
Learn the basics of writing non-social gadgets. |
|
Reference for the gadget specification XML. |
|
Display locale-appropriate content based on the user's country and language settings. |
|
Render your gadget in different sections of the container. |
Fetch remote content. |
|
Securely transmit OpenSocial IDs to a remote server. |
|
Validate that information from a container has not been modified. |
Simplify your display code by using templates. |
Access social data from your server. |
|
Use PHP, Java, Ruby, Python, and ActionScript or other languages to access social data. |
Follow best practices for designing social applications. |
|
Avoid the use of the |
|
Learn how to measure the latency and performance of your app. |
|
Reduce the latency of your app. |
|
Learn how OpenSocial uses OAuth authorization. |
|
Including the comparison on first-time gadget rendering performance, and the data requesting performance. |
Experiment with social JavaScript calls inside of a social network. |
|
Learn how to build social gadgets locally, using the OpenSocial Development Environment |
|
Automatically translate gadgets using this Windows tool. |
|
An example social networking site based on PHP Shindig. |
|
An example social networking site based on Java Shindig. |
|
An Open Source Silverlight 2 Kit for the MySpace Developer Platform. |
Build an OpenSocial application using Google App Engine. |
|
Access the Google Data APIs from a gadget, using the Google Accounts APIs for authentication. |
|
Integrate OpenSocial and Google Friend Connect on your PHP website. |