Start Flighting Your Apps for the Windows Store

Start Flighting Your Apps for the Windows Store

Flighting is a word we have heard more since the inception of the Windows Insider Program (WIP) than ever in the history of Windows.

The concept behind flighting​ is to have multiple rings that you use to distribute software for testing.

We used to commonly refer to these as Alpha, Beta and Release Candidate versions of software but now that most software on the Windows platform is constantly being tweaked and updated, including Windows itself, we have changed that approach.

Under the WIP those various levels of testing are referred to as Fast and Slow Rings.  The expectation of these rings is that Fast Ring participants would get earlier releases of the software with the potential that there could be more bugs and issues. Slow Ring testers would follow those in the Fast Ring and the updated software would include fixes made for bugs discovered by Fast Ring testers.

Finally, your regular software users would then get the current release of your app after issues identified by Slow Ring testers were fixed. 

This process means your daily app users would remain on a stable release build while your testers through the Fast and Slow Rings were testing the new version. This results in less disruption and allows you to adequately test your app before it is widely available.

If you are interested in implementing a flighting strategy to your app development process then you should check out this update in the Windows Dev Center about Package flights.

"When you set up package flights, you can choose the specific people who should get specific packages by adding them a flight group. Anyone in a flight group who is using a device running a version of Windows 10 that supports package flights (Windows.Desktop build 10586 or later; Windows.Mobile build 10586.63 or later) will get packages from the package flight(s) that you designate for that particular group. Anyone who has not been added to one of your flight groups, or is using a device that doesn’t support package flights, will get packages from the non-flighted submission."

This article will walk you through through these steps for flighting your app:

  • Creating a new flight group
  • Creating a new package flight
  • Specifying what to include in your package flight
  • Configuring additional package flight options
  • Submitting your package to the Store
  • Updating/Modifying your package flight
  • Adding and Ranking additional flight packages
  • Make packages from a flight available to all customers
  • Deleting a package flight

But, wait...there's probably more so be sure to follow me on Twitter and Google+.

----------

Looking for an awesome, no-nonsense technical conference for IT Pros, Devs, and Devops? Check out IT/Dev Connections!

IT/Dev Connections

Hide comments

Comments

  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Publish