Requirements for building Windows apps

  • App icons in PNG format. We recommend a square (310x310-pixel) and a rectangular (310x150-pixel) PNG file for display in Windows.
  • A 620x300-pixel PNG splash screen.
  • Valid Windows Store developer account.

Building a Windows app

You can use either a Windows or a Mac OS computer to build Windows apps.

  1. When building your app, some of the fields need to match the information you specify in Windows Dev Center if you plan to submit the app to Windows Store. Follow the steps in Windows Publishing Guide for AEM Mobile to reserve your app name.

    After you complete the initial process of reserving your app name, return to this article for information about building the app.

  2. In the On-Demand Portal (, click Apps on the left rail. If you have access to more than one project, choose the project from the drop-down menu.

  3. Click the Add icon to create an app.

  4. Choose Windows as the platform, and click Next.

  5. Follow the prompts to build the app. For detailed option descriptions, see the related section later in this article.

  6. If your app includes in-app purchases, you must copy the shared secret information to the "Windows Main Package Identity Name" field in the Store section of the project settings. For details, see Obtaining the Main Package Identity Name.

  7. After you build the app, download it and test it. When ready, submit it to Windows Store. See Windows Publishing Guide for AEM Mobile.

General settings

App Name. Specify the name of the app. This name appears in the app library.

Description. Write a brief description of the app. This description does not appear anywhere at this time. The description that appears in the Windows Store is added in the Windows Store Dev Center.

Short App Name. The short app name appears on the live tile. Consider leaving this field blank if your app icon provides the app name.

Publisher Display Name. If you're submitting the app to Windows Store, the publisher display name you specify must be identical to the name you specify in the Windows Store Dev Center. Look in the  Account Settings.

Windows Store Dev Center
The Publisher Display Name and the Publisher ID are listed in the Windows Store Dev Center.

Publisher ID. If you're submitting the app to Windows Store, the publisher ID you specify must be identical to the ID you specify in the Windows Store Dev Center. Look under Profile > Account.

Main Package Identity Name. If you're submitting the app to Windows Store, the Main Package Identity Name you specify must be identical to the one that Microsoft auto-generated. Select your app in the Windows Dev Center Dashboard, expand App Management in the left rail, and click App Identity. For details, see Obtaining the Main Package Identity Name.

Tablet App Orientation. Select whether the app has a landscape or portrait orientation.

App Languages. This option affects the localized information in the store, not the availability of the app. For each language you list, Microsoft requires you to add a separate description and screen shots. Most publishers specify only one or two languages.

Enable Preview. If this option is selected, the testing app you create displays all valid content, published or unpublished. Use this option only for previewing unpublished content, not for submitting to the App Store. For details, see Previewing project content for AEM Mobile.

Show Analytics Opt-in Dialog Box. If you select this option, your customers can opt out of data tracking. They can use app settings to opt in or out at any time. This option is especially useful for regions in which you are obligated to allow users to opt out of data tracking.

Privacy Policy URL. This is required if you're submitting the app to Windows Store. Specify the URL of a web page that describes your privacy policy. Failure to include a privacy policy URL might result in your app being rejected by Microsoft.

Override the App Version Number. This option is necessary if you are updating an app and you used a different tool to create your existing app. Select this option and specify a more recent marketing version number. The version number for your current app is displayed in the My Apps page in the Windows Store Dev Center.

Assets settings

In the Assets pane, specify these settings.

Square Tile/Wide Tile. Specify a 310x310 and 310x150-pixel PNG images for the square and wide app tiles that appear on the Windows start screen. See Building AEM Mobile app icons and launch images.

Splash Screen. Specify a 620x300-pixel PNG image that appears briefly while your app is being loaded. The splash screen image is not scaled. It is centered in front of the background color you specify. Consider using transparency in your splash screen image.

Live Tile URL. If desired, specify a URL that displays images for Windows live tiles. For details, see The tile template catalog.

Background Color. Specify a 6-digit hex color for your splash image background. The color is displayed behind your splash screen when the app launches. For color picking, see Adobe CC Color or other related website.

Plug-ins settings

For information about Cordova plug-ins such as File Access and Geolocation, see Using Cordova plug-ins in AEM Mobile.

When to rebuild and resubmit apps


In general, you should rebuild your app for these reasons:

  • To edit an app setting, such as changing the app icon.
  • To take advantage of new viewer features or bug fixes in the latest release.
  • To use newly uploaded fonts.
  • To include any changes made in the Mobile Marketing apps settings. 

When you change nearly all project settings, you do not need to update your app. For example, you can specify store settings, set up entitlement, add subscription and product IDs, and enable social sharing without having to update the app. One exception to this rule is uploading fonts for cards. Fonts are built into the app, so you need to rebuild the app to use new fonts.

To rebuild an app, do this:

  1. Select the app in the Apps section of the On-Demand Portal and click the edit (pencil) icon.
  2. Make any changes, and click Submit.
  3. Download and sign the app.

Doing this rebuilds the app with the newest viewer code.

Create private enterprise apps for Windows

Microsoft has two requirements for enterprise deployment of Windows Store apps:

  • The app's device must be joined to a domain.
  • The certificate used to sign the .appx must be in the trusted list of certificates on the device.

The .appxbundle file provided by DPS App Builder is signed for submission to Windows Store. For enterprise deployment, you might need to re-sign the .appxbundle and its contents with your own enterprise certificate.

For distribution of the app file, use any supported Microsoft method. You can even use a simple command-line method.