We have put together a little set of guides which could help you along the way. Here they are.

• Write your apps keeping in mind that for a different set of options, one can install a second instance of the application. Embed codes DO NOT accept HTTP GET parameters. The only parameter is the access token and that should uniquely identify the application's working set of settings. Details here.

• Try keeping the number of API requests in production stage to a bare minimum, especially in the embed script. They are time-expensive and too many can severely influence your users' experience. You can use caching for CPU intensive operations.

• Write your applications in English and add localization support if you think it's necessary.

• Never show the AccessToken anywhere public. Always use the PublicToken for that.

• Don't reinvent the wheel. Search the knowledge base and the discussion groups for solutions to your problems. Look for API methods which accomplish the functionality you seek.