App review checklist
How do you make sure your app gets approved?
Based on the app type you've built, we have created the following checklists for you to make the process even smoother.
Don't know which checklist to follow?
Find out more in our Lokalise apps page.
The following rules are applicable for all app types.
|Guidelines||App follows our content and coding guidelines.|
|User Experience||The app provides a high-quality user experience and does not degrade or compromise the performance of the Lokalise Platform.|
|Quality||The app is fully functional and not meant for testing purposes—it's not a work in progress. There are no obvious bugs and all actions, including edge or error cases, are fully functional.|
|Test data||When you submit your app for review, create a test account and share it with the Lokalise apps team for a faster app review.|
|Rate limit||Access to all endpoints are limited to 6 requests per second. This limit is applied per API token and per IP address. Read more|
Additional criteria for native apps
Native apps are hosted in a third party platform and provide users with a native experience within that system. Examples: Wordpress, Figma, or Sketch plugins.
|Software requirements||The app meets the Native app technical requirements.|
|Installation||Users are able to install and remove app/plugin in the native third party platform. After the user removes the app, all data about content objects should be deleted.|
|Authentication||When users install the app, they authenticate with Lokalise using OAuth 2 or API keys. The scope and credentials are saved in the app for all future communication with Lokalise.|
|Configuration||Users are able to connect to existing Lokalise projects.|
Content exchange guidelines for native apps (optional)
If your native app is working mainly with content (item selection, import, export, etc.), please follow some additional guidelines listed below:
|Item selection||Users should be presented with an interface listing all content that is available for translation, being translated, and has been translated. |
The interface should include the main information about translatable elements (field type, title, etc.) and the possibility to select any items for translation.
|Import||Users can import translated content from Lokalise back to the native platform.|
|Export||Users can export all translatable content to Lokalise. After the user clicks Export, new keys will be created in the selected Lokalise project.|
Additional criteria for hosted apps
These apps are hosted by Lokalise. Examples of such apps include GitHub and Bitbucket integrations, or custom placeholders, which are built right inside the Lokalise codebase.
|Software requirements||The app meets the Hosted app technical requirements.|
|Licensing||Your app is published under the acceptable OSS/commercial licenses.|
|Authentication||When users install the app, they authenticate with Lokalise using API keys. The scope and credentials are saved in the app for all future communication with Lokalise.|
|Packaging||Provide git repository with the source code containing a docker file|
Updated 9 months ago