Universal Windows Platform apps: Difference between revisions

Content deleted Content added
Line 52:
Metro-style apps are suspended when they are closed; suspended apps are terminated automatically as needed by a Windows app manager. Dynamic tiles, background components and contracts (interfaces for interacting with other apps) may require an app to be activated before a user starts it.<ref>{{cite web|last1=Joshi|first1=Bipin|title=Understanding Windows Store App Lifecycle and State Management|url=http://www.codeguru.com/win_mobile/win_store_apps/understanding-windows-store-app-lifecycle-and-state-management.htm|website=Code Guru|publisher=[[QuinStreet]]|date=22 February 2013}}</ref><ref>{{cite web|last1=Hale|first1=David|title=App lifecycle|url=https://msdn.microsoft.com/en-us/windows/uwp/launch-resume/app-lifecycle|website=[[MSDN|Windows Dev Center]]|publisher=[[Microsoft]]|date=7 March 2016}}</ref>
 
For six years{{citation needed|date=May 2020|reason=While the introduction of command line activation is sourced and dated the part about 'six years' is not}}, invokingInvoking an arbitrary Metro-style app or UWP app from the command line was not supported; this feature was first introduced in the [[Windows Insider|Insider]] build 16226 of Windows 10,<ref>{{cite web|last1=Whitechapel|first1=Andrew|title=Command-Line Activation of Universal Windows Apps|url=https://blogs.windows.com/buildingapps/2017/07/05/command-line-activation-universal-windows-apps/|website=Building Apps for Windows|publisher=[[Microsoft]]|date=5 July 2017}}</ref> which was released on 21 June 2017.<ref>{{cite web|last1=Sarkar|first1=Dona|title=Announcing Windows 10 Insider Preview Build 16226 for PC|url=https://blogs.windows.com/windowsexperience/2017/06/21/announcing-windows-10-insider-preview-build-16226-pc/|website=Windows Experience Blog|publisher=[[Microsoft]]|date=21 June 2017}}</ref>
 
==Development==