Are you viewing the right article?
This article refers to Digital Publishing Suite. For the AEM Mobile article, see Windows publishing guide.
With DPS tools, you can create a DPS viewer app that you can submit to Windows Store. Your Windows app can be displayed on any device or computer that runs Windows 8.1. DPS apps do not support Windows Phones.
This document describes how to set up a Windows Store developer account, use the Windows Store Developer Center to set up app details, and submit the app. For information about building the Windows app, see Building DPS apps for Windows Store.
If you have not already done so, sign up for either an individual or company Windows Store developer account:
If your app includes retail content, specify banking information so that Microsoft can pay you for retail purchases.
When you use the Windows Store Dev Center to build an app, you specify app details, in-app purchases for retail content, and submit the app in a series of steps. No certificates are required.
Use the information that you provide during this process when using Web-based DPS App Builder to build the app.
Specify an unused app name for the Windows Store. Use this same name when using DPS App Builder to build the app.
The options in the Selling Details section refer to the app itself, not to in-app purchases. For most DPS apps, the app itself is free, and the folios within the app are either free or retail. You specify in-app purchases for folios in the next section, "Services."
- Set a price tier for the app.
- DPS apps do not use a third-party commerce system for in-app purchases. Leave the check box unselected.
- Under Hardware Requirements, leave "Available to all systems" selected for each option.
- Under Accessibility, leave the check box unselected.
in the Services section, you can specify in-app purchases for folios. Windows Store lets you specify only one price for all retail folios in your app, so you create only a single Windows Store Product ID for in-app purchase offers. You then specify this Product ID when using DPS App Builder to build the app.
Note: Even though you create a single Windows Store Product ID, it is important that you use different Product ID values (such as com.mycompany.myapp.issuename) for each folio when using Adobe Folio Producer to publish your folios.
- Specify a Windows Store Product ID for your retail folios. We recommend that you use the reverse DNS format such as com.mycompany.myapp.inapp.
- Under "Product Lifetime," choose Consumable. You must choose "Consumable," or purchasing will not work.
- Under "Content Type," select “Electronic magazine single issue.”
Specifying a shared secret (called the "Windows Main Package Identity Name") is required for Windows apps with in-app purchases. For information about obtaining the shared secret, see the related section later in this article. Then copy the identity name in the “Windows Main Package Identity Name” option in the Account Admin tool.
Drag and drop the required .appx file. You obtain this file by extracting the .zip file downloaded from DPS App Builder. After you submit the file, the filename should be displayed in green text.
- Specify the app description.
- Upload at least one screen shot of your app, and provide a caption for each image.
- If you specified an in-app purchase, specify a description. Microsoft requires this description, but it doesn't appear in the app.
The Main Package Identity Name is required when you use DPS App Builder to build an app for Windows Store. If your app includes in-app purchases, you must also specify the identity name in the Main Package Identity Name field in the Store section of the project settings.
Microsoft displays the Main Package Identity Name in the Windows Dev Center.
- Sign in to Windows Dev Center.
- Select your app in the Dashboard.
- Expand App Management in the left rail and click App identity.
- Copy the string to the right of "Package/Identity/Name."
Use Web-based DPS App Builder to build the app. For details, see Building DPS apps for Windows Store.
After you use DPS App Builder to build the app, download the .zip file and extract it. To test the app, you use the Add-AppDevPackage.ps1 script.
You cannot test in-app purchase in Windows Store prior to submitting your app. Folios published as public/retail will not display in the library until after the application is approved by Microsoft.
For in-app purchases to work correctly, please take the following actions:
- Make sure that you have followed the instructions in the "Services" section of this article. Use the same Product ID in DPS App Builder that you specify in the Dev Center, and set the product lifetime to Consumable.
- Specify the Main Package Identity Name in the Account Administration tool. Go to http://digitalpublishing.acrobat.com/, log in with your master account, click on Account Administration, and edit the settings for your app. Copy and paste the Main Package Identity Name as described earlier in this article.
Failure to follow these steps will likely result in errors when attempting to complete an in-app purchase.
- Use the Web-based DPS App Builder to build your app and download the .zip file.
- Extract the .zip file and obtain the .appbundle file.
- In the Windows Store Dev Center, upload the .appxbundle file in the Packages section.
- Once you have completed the necessary information in each section, click Submit For Certification. Follow the prompts to submit the app to Microsoft for approval.
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. Contact your Adobe representative for more information.
For distribution of the app file, use any supported Microsoft method. You can even use a simple command-line method.