Windows 10 Development Lifecycle - Windows 10 Development

What is Windows 10 Development Lifecycle?

Traditionally, Windows has setting, where users can run numerous applications concurrently. User can switch between diverse applications easily. This model does not work well for phone or tablet devices where the usage is classically single-application focused.

One of the most important challenges facing Windows 8 Store application programmers will be managing and understanding the application lifecycle. If you have been building Windows phone applications, then much of this would be familiar.

Under Windows 8, the operating system achieves the lifetime of an application, and while the user can terminate an application, classically the user opens new applications without deliberately terminating running applications.

The Universal Windows Platform (UWP) for Windows 10 addresses these issues, offering some cool stuff to the desktop users so that multiple applications can run with a multiple windowed experience.

Windows applications can exist in three states at the basic level as shown below.

  • Running
  • Suspended
  • Terminate


  • When a user sendoffs/activates any application, then it goes in the running state.
  • Applications can be postponed if a user does not use it and it is no longer in the foreground.
  • From the Suspended state, applications can either resume that application or terminate the OS in order to reclaim system resources.

Process State Transition

It is significant to comprehend the process state transitions in a running application. When the user first launches the application, the splash screen is shown and then the application starts running.

The procedure can be described as follows −

  • When the application is appending, your app gets five seconds to handle that suspended event.
  • When the application is suspended, completely no code runs and no resources are allocated.
  • When it resumes, the app is notified that it has resumed. If you are coming from a suspended state, you need to take no action.
  • Under memory pressure, it is possible for your application to be terminated.
  • Remember that you will not be notified at that point, and so any saving you do, you have to do when you enter into the suspended application state.

When the application transits back and forth between Running and Suspended states, fire suspending and resuming events respectively.
Sometimes, you need to save data. Then you have to call asynchronous methods as shown below.

Let us study an example in which controls are added as shown in the below given XAML file.

Assumed below is the C# code in which the Suspend and Resume events are applied. The current data will be stored in the suspend eventin local settings and then the data will be retrieved in the resume event from local settings as shown below.

When the overhead code is compiled and executed, you will see the resulting window. Now write the desired information.


Let us go to the Lifecycle Events dropdown menu and select suspended. Now your application will be suspended and the desired information will be stored in local settings. See the screenshot given below.


Currently, when you want to resume your application, select the option Resumefrom the Lifecycle Events menu.


Currently you will see that the stored information is recovered from local settings and the application is resumed at the same state from which it was suspended.


All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd Protection Status

Windows 10 Development Topics