Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

Checklist: Getting your app world-ready

apps for Office and SharePoint

Identify the items in your app that could be customized for the markets where you expect people to use your app.

Last modified: March 09, 2015

Applies to: apps for SharePoint | Office 365 | Office Add-ins | SharePoint Add-ins | SharePoint Foundation 2013 | SharePoint Online | SharePoint Server 2013

Note Note

The names "apps for Office" and "apps for SharePoint" are changing to "Office Add-ins" and "SharePoint Add-ins". During the transition, the documentation and the UI of some Office and SharePoint products and Visual Studio tools might still use the terms "apps for Office" and "apps for SharePoint". For details, see New name for apps for Office and SharePoint.

When getting your app ready for different markets it’s a good idea to consider all the different interactions that your app has with users. Your app might make an extensive use of words, either written or spoken, or signs and icons. Whatever means of communication your app uses you should consider if it’s appropriate for your target markets.

Store listing

Checklist box

I want to apply different descriptions, screenshots, and title (the metadata) for each language my app is in. I have my information and graphics ready to load.

Checklist box

I want to provide specific licensing terms in every language that my app supports. I have that information ready to upload. My license terms are really clear about what my app offers, and whether you have to pay for the app.

For more information, see Submit apps for SharePoint to the Seller Dashboard.

Core app experience

Checklist box

The text I use in my app for menus and controls is stored in resource files. For more information, see How to use application resource files (.resx) to efficiently create a localizable ASP.NET Web application.

Checklist box

The text in my error messages is stored in resource files.

Checklist box

I made sure that the formatting is correct and the information is displayed in the correct order in languages where the text is displayed in different directions. For example, English is displayed from left-to-right, Arabic is displayed from right-to-left.

Checklist box

The text my app presents is easy to understand and fits in the space designated for it in every language that my app supports.

Checklist box

Text in images and graphics is translated. Or use letters in the image and then explain what the letters indicate close by in a description.

Checklist box

I provided resource files for audio and video clips. In case that I am not providing multimedia content for every market, notify the user that the content is going to be presented in a different language.

Checklist box

I’ve checked that the content in my app, including signs, icons, and images, is not offensive in any of the markets that my app supports.

For more information, see Build a localized app for Office and Localize apps for SharePoint.

Supporting resources

Checklist box

Help and support material is provided for every market that my app supports. If this is not feasible, I let my users know that they are about to see content in a different language.

Checklist box

I have a get started experience appropriate for every market that my app supports. If that isn’t possible, I’ve provided clear information about how to get started in some other content for those markets.

© 2015 Microsoft