Publish the app to the Windows Store.
- [Instructor] At this point, you've created your app package, and run the Windows App Certification Kit to ensure compliance. Publishing to the store is pretty simple after that. Let me show you what I mean. At developer.microsoft.com/windows, make sure you're signed in to your Dev Center account. Navigate to the Dashboard in the top right corner. You should see the app name that you just created. I'll click on mine, Todo Together. Click on "Start your submission" to start your first product submission.
Here you will see all of the forms that you will need to fill out in order to finish your submission to the store. I encourage you to start with Packages, as that will typically take the longest because it has to go through some store validation. Return to Visual Studio, and right click on your project in the Solution Explorer. Click on "Open Folder in File Explorer", and then click on the App Packages folder. You should see an AppX upload file, as well as a test file. Put this on one half of the screen, and the Dev Center on the other half, and drag the AppX upload to the store.
It's very important that you do select the AppX upload file, and not any of the other app packages. The AppX upload is designed to be submitted to the store, as it contains all of the relevant store metadata. Go ahead and make the Dev Center full screen again. You can then select "Device family availability", or just let Microsoft decide. For now, I'm just going to select Desktop, because that's the only device we've tested on in this video. I want to emphasize that you should always test your application on all of the devices that you plan your app to run on.
I'll then select Save. Now, go through each of the other submission flows in order to finish your app submission. In Pricing and Availability you can choose how to price it, I'll just select Free, and who to make it available to. I'll make it available to everyone. I want to publish this app as soon as it passes store certification. I'll click Save to finish the Pricing and Availability options. Under Properties, choose what type of application this is. This is a productivity app, so I will select Productivity.
For product declaration, I'll say that the customer can install this product to alternative drives, or removable storage, because performance won't be impacted severely. I can also let Windows include product's data in automatic backups to OneDrive. Since we didn't go through and fix all of the accessibility issues, I'm not going to say this product has been tested to meet accessibility guidelines. For system requirements, I'm not going to need anything special for my application, so I'm just going to leave everything as the default, and select Save. For Age ratings, I'm going to go through the process to determine who my app is available to.
In order to complete this, you'll first have to complete the International Age Rating Coalition questionnaire. This is for compliance. Select your app type, which for us is Utility, Productivity, Communication, or Other. Our app does not have violence, sexuality, language, or controlled substance references, and it does not have any promotion of age-restricted products or activities. "Does the app natively allow users to interact "or exchange content with other users "through voice communication, text, "or sharing images or audio?" No. "Does the app share the user's current physical location"? No.
Does the app allow you to purchase digital goods? No. "Does the app contain any swastikas, "other Nazi symbols or propaganda deemed unconstitutional in Germany?" No. Is the app a web browser or search engine? No. Finally, you can select the age for All, And none of these descriptors match our application, so we'll select "Save and generate". When the age ratings have been generated properly, you can scroll down and select Continue. Next for Store listings, you can have a listing for each of the languages supported in your package.
You can do that using the methodology we determined before, and give them the user email, and the password to sign in to your app and test the functionality. After all this is filled out, you're ready to publish.
- Working with .NET for UWP app development
- Establishing application architecture
- Configuring Azure services
- Configuring the mobile app service backend
- Testing and publishing the service backend
- Using Facebook authentication
- Using XAML
- Client server abstraction API
- Using the UWP community toolkit
- Styling app views
- Creating adaptive views
- Testing an app for multiple user accounts
- Publishing to the Windows Store
- Sideloading app packages