Create world-ready apps for Office and SharePoint
Learn about apps that are ready for more than one market and more than one culture. Discover the opportunities and learn what is needed to get your app ready for the world.
Last modified: December 16, 2013
Applies to: apps for SharePoint | Office 2013 | Office 365 | Office Add-ins | SharePoint Add-ins | SharePoint Online | SharePoint Server 2013
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".
In this article
Plan ahead to be ready to sell your app to the world
Design for everyone, or just specific markets
Develop and test to be sure your app’s behavior and UI are world ready
Publish to a global market
The Office Store supports multiple markets in which you can sell your apps, with more added frequently. As a developer, you can create apps for Office and SharePoint that automatically adapt themselves to the culture of the markets that interest you.
Before you get your app ready for multiple markets, there are some crucial things to know in addition to app development basics that can make your app more ready to succeed— specifically, by designing your app to be world-ready from the start--before you write a single line of code. We have resources to guide you in applying world-ready practices through the lifecycle of your app.
There are many benefits in getting your app ready for multiple markets. From reaching more costumers to providing a better experience you should make sure that you’re not missing out on the opportunities that global markets offer you. You can find more information in Plan to make your app for Office or SharePoint world-ready.
Even if your users are in a market that is not opened yet, they can still benefit from your world-ready app. Users see a message informing that their market is not open yet and either get redirected to the EN-US store if they are on the Office client. If users are on SharePoint they get a message asking him to choose from a list of available markets. In any case, you can still support a specific language even if there’s no store for it, and users can benefit from it.
Getting your app ready for multiple markets requires some thought in advance about your design. Depending on the level of support that you want to offer to a particular market, your app could require more than just translation services. What does your UI look like for that? For example, colors and signs could have completely different meanings in different cultures. See Checklist: Getting your app world-ready and Localization for apps for Office for details.
When your app is ready to go out to the markets, learn the steps to Publish apps for Office and SharePoint. And specific resources you’ll need: