Developer / Documentation / Application Guidelines
Usability guidelines
- User-friendly interface (clear icons, menu, etc.)
- App in the right format (no overlapping/clipping)
- Quick load times
- Use of available extensions for usability: autocompletion, albums...
- Integrated in logs (activities) without spamming
- In case there is a payment feature in the app or game, Netlog credits should be offered as one of the payment methods
- For games: high scores are highly recommended
- For apps: optimized flow (play again, play with others, tell a friend, etc.), no forced install
Netlog does not allow:
- External links to the application provider or affiliated sites (*)
- Autoplay
- Display of company logos in the logs or notifications (*)
- Registration procedure (email, telephone, password,...). All apps and games should be single sign-on
- Non-localized applications (Netlog can assist in the translation/localization process - contact us)
Netlog does allow:
- Branding, co-branding and sponsorships
-
Revenue sharing of Google Adsense (100% of net revenue):
A vertical rectangle or wide skyscraper can be displayed in the canvas view. All revenue is for the developer. There will be no ads allowed in the profile view. (*) - Monetizing through the use of a unique credits economy
(*) Exceptions may apply for privileged partners. Contact us for more information.
Articles for app developers
Must-reads: Tutorials: creating apps with JS and PHP- Tutorial 1: OpenSocial JS API
- Tutorial 2: OpenSocial REST API
- Tutorial 3: OpenSocial example app
- Tutorial 4: OpenSocial PHP client
- Tutorial 5: Flash and OpenSocial
- Deprecated: Netlog REST API Flash Applications PHP Applications
Por favor, espera...