This document provides an overview of Windows 8 Metro apps. It discusses the prerequisites for developing Metro apps, the available programming languages and technologies, the app sandbox model, capability declarations, contracts and extensions, the application lifecycle, app packages and deployment, file access and permissions, the Windows Store, and takes questions. It is intended as an introductory guide for developers interested in creating Metro apps for Windows 8.

1. Windows 8 Metro apps
© 2012, Eugene Kirian

2. Windows 8

3. Agenda
1. Introduction to Windows 8 Metro
2. Practice
3. Windows Store
4. Questions

4. Prerequisites
• Windows 8
• Visual Studio 2012
• Knowledge of C#/VB.Net/C++/JavaScript
• Windows LiveID

5. Languages and Technologies
The choice
• JavaScript + HTML 5
• C#/VB.Net + XAML
• C++ + XAML JavaScript C#/VB.Net
• C++ + DirectX
HTML XAML
C++ C++
XAML DirectX

6. Sandbox

7. App capability
declarations
Metro style apps that need programmatic
access to user resources such as the Pictures
library or connected devices such as a
webcam, must declare the appropriate
capability. An app requests access by
declaring capabilities in its package
manifest.

8. App capability declarations
Capabilities
• Music library
• Pictures library
• Videos library
• Removable storage (USB, External HDD)
• Microphone
• Webcam
• Location (GPS)
• Proximity (Locate nearby devices)
• Internet and public networks
• Home and work networks
• Enterprise authentication
• Shared User Certificates
• Documents library (Require to have at least one app
supported file extension)

9. App contracts and
extensions
Metro style apps use contracts and extensions
to declare the interactions that they support
with other apps. These apps must include
required declarations in the package manifest
and call required Windows Runtime APIs to
communicate with Windows and other contract
participants.
Contracts - an agreement between one or more
apps.
Extension - an agreement between an app and
Windows.

10. App contracts and extensions
Contracts & Extensions
• Account picture provider (extension)
• App to App Picking contract
• AutoPlay (extension)
• Background tasks (extension)
• Cached file updater contract
• Camera settings (extension)
• Contact picker (extension)
• File activation (extension)
• Game Explorer (extension)
• Play To contract
• Print task settings (extension)
• Protocol activation (extension)
• Search contract
• Settings contract
• Share contract
• SSL/certificates (extension)

11. Application lifecycle
• App deployment
• App launch/activation
• App suspend/change visibility/resume
• App close/crash
• App removal

12. Application lifecycle

13. App packages and
deployment
Package is container - Open Packing
Conventions (OPC) standard. OPC defines a
structured means to store data and
resources for the app using a standard ZIP
file.
• Package manifest
• Content
Installation to
%ProgramFiles%WindowsApps

14. File access and
permissions
You can get access to:
• Application install directory
• Application data locations
• User’s Downloads folder
• Additional locations
(Documents, Music, Pictures, Videos
libraries, removable devices, etc…)

15. Lets get started!

16. Windows Store
• Over 200 countries and over 100
languages to sell the app
• Developer account ISN’T available for
Ukraine

17. For those, who can…
• 70% payoff when net sales is less than
$25,000
• 80% payoff, after that
• Minimum app price is $1.49

18. Windows Store Features
• Buy and download
• Time-limited trial
• Feature-limited trial
• In-app purchases
• Advertising (Windows Advertising)
• Third-party transactions

19. Questions?