Template designed by
Introducing the Windows Phone 8.1
App Development Platform
Lorenzo Barbieri
lorenzo.Barbieri@microsoft.com
@_geniodelmale
Template designed by
Template designed by
brought to you by
3
4
5
6
7
Decrease HW cost floor (support 8x26, Qualcomm Reference Design)
Dual-SIM support
Apps to help you get more out of your data plan: DataSense 2.0, Wi-Fi Sense, Storage Sense, Battery Sense
8
9
http://dev.windowsphone.com
http://appstudio.windowsphone.com
10
11
12
13
Windows 8.1 provides developers with a shared platform that renders the right app experience for the right form-factor
Apps come to life on Windows
• Live tile improvements
• Action Center for smart notifications
• Background execution + triggers
• Bluetooth-LE support for wearables + beacons
• Internet Explorer 11 improvements
Designed once; engaging everywhere
• Converged developer platform
• Converged app model
• Shared app identities + entitlement
• Unified push services (via WNS)
14
Windows Phone 7.5 Windows Phone 8.0
Convergence Begins with IE
• WP 7.5 shipped with IE9
• Same rendering engine as
Windows
• Same JavaScript engine as
Windows
Converged Core (NT kernel)
• Common kernel & file system
• Kernel mode driver framework
• Secure boot & storage
encryption (BitLocker)
• Core networking stack
Developer Platform
• Partial API convergence
(focus on sensors & IAP)
• Native Code (C++) and DirectX
• IE10
Converging the Dev Platform
• More skillset reuse
• More code reuse
• More seamless app experiences
Aligning the Stores
• Shared dev registration
• Shared entitlement
Common Core Platform
• Proximity & Location frameworks
• Security & identity
• Task scheduler
15
The Windows Runtime (WinRT) is the
shared runtime and API space used by
store apps across the Windows platform
(phone and client)
Dramatic convergence in 8.1
• Goal is 100% convergence for dev scenarios
• In 8.0, we had ~30% API convergence
• With 8.1, we move well past 90%+ convergence
16
| |
Legend
17
19
• One Visual Studio ‘Universal app’
project template for your app
• Shared dev and test tooling for both platforms
20
21
Provides a common layout coordinate
system that extends along the x and y
axis into infinity, allowing you to scale
up
22
10”
tablet
7” tablet
6”
5”
4.5”
Infinite virtual canvas
166 Logical DPI
23
80% exact same XAML 20% custom
Common SignatureOptimized
DatePicker
TimePicker
CommandBar
AppBar
Button
CheckBox
RadioButton ProgressBar
Slider
ToggleSwitch
Hub
Pivot
ListView
GridView
24
On Windows Phone 8.1 … and on Windows 8.1
25
26
Task
TimeTrigger
PUSH
Notification
LocationTrigger
PushNotificationTrigger
MaintenanceTrigger
InternetAvailable NetworkStateChange
TimeZoneChange
27
Windows Notification Service
(WNS)
• Shared push service for Windows +
Phone
• Improved queuing to limit lost
notifications due to intermittent
network connectivity
Tile templates + toasts
• Shared tile templates (more!)
• Periodic tile updates
• Toasts
Action Center
• Central location to surface
missed notifications
• Apps can intelligently manage
notifications
(silently add, update, and delete
notifications)
28
Device B
WP 8.1 – PFN 12345
Roaming Local
Local
Cache
Temp
Device A
WP 8.1 App
Roaming Local
Local
Cache
Temp
Backup [Device A]
30
31
32
Anna beats a level, with top
score!
The app asks her if she wants
to share this with her
friends? She says – “yes
please!”
Congratulations!
Shall we share this?
Share on:
Anna is playing her favorite
game. The level is almost
over, and Anna could break
her record. The application
starts recording the screen.
The application uploads the
MP4 file, which was
automatically transcoded to a
VGA resolution for quick
uploading, to a website for
sharing.
35
36
37
Internet Explorer 11 brings more life to the mobile web via better HTML5 support
38
Ability to code pinning behavior
• Specify high-resolution site icons
• Live tiles using notifications
Professional quality video
• Adaptive streaming
• Secure viewing
• Accessibility improvements
WebGL support
Web spec based on OpenGL ES 2.0, to enable use of low-level
3D graphics APIs on web sites and HTML-based apps
Rich user interactions
• Screen + device orientation APIs
• Pre-fetch and pre-render
39
40
41
42
43
http://dev.windows.com http://dev.windowsphone.com
44
Supported operating systems Windows 8.1 (x86 or x64)
Hardware
4 GB of free disk space
1.5 GB of RAM (recommended)
64-bit (x64) motherboard
To use the Windows Phone Emulators
Windows 8.1 Pro or higher (for Hyper-V)
and Second Level Address Translation
(SLAT)
Min 4GB RAM
46
47
48
49
Approach Pros & Cons
Keep using Silverlight 7.x/8
(Windows Phone 8 platform)
Pros
 Will run on Windows Phone 8.1 (app compatibility), still runs
on earlier Windows Phone devices
Cons
 Will not take advantage of new platform capabilities
 Will not enable targeting of Windows
Use Silverlight 8.1
(Move Silverlight app into new execution
stack and app package)
Pros
 Enables existing Silverlight apps to take advantage of nearly all
new APIs and platform capabilities
Cons
 Will not enable targeting of Windows
 Will not run on Windows Phone 8 devices
Use Windows XAML platform
Pros
 Enables targeting of Windows and Windows Phone
 Takes full advantage of new APIs and platform capabilities
 Better performance & reduced memory use
Cons  Will not run on Windows Phone 8 devices
52
53
Primary features:
Existing Windows Phone 8 apps run flawlessly
Windows Runtime XAML platform and HTML/WinJS support brings convergence with Windows 8.1,
and is faster and uses less memory than Silverlight
The core of an app can be built once for Windows and Windows Phone; you can share elements of
UI, though it’s best to tailor the user experience for each platform
Convergence is not just in the developer platform: it spans tools, store, commerce
Developer investment in the existing Silverlight platform is protected: Existing Silverlight apps can
be upgraded to access new Windows Phone 8.1 platform capabilities





Template designed by
Domande?
Lorenzo Barbieri
lorenzo.Barbieri@microsoft.com
@_geniodelmale
Template designed by

Mob02 windows phone 8.1 app development

  • 1.
    Template designed by Introducingthe Windows Phone 8.1 App Development Platform Lorenzo Barbieri lorenzo.Barbieri@microsoft.com @_geniodelmale Template designed by
  • 2.
  • 3.
  • 4.
  • 5.
  • 6.
  • 7.
  • 8.
    Decrease HW costfloor (support 8x26, Qualcomm Reference Design) Dual-SIM support Apps to help you get more out of your data plan: DataSense 2.0, Wi-Fi Sense, Storage Sense, Battery Sense 8
  • 9.
  • 10.
  • 11.
  • 12.
  • 13.
    13 Windows 8.1 providesdevelopers with a shared platform that renders the right app experience for the right form-factor Apps come to life on Windows • Live tile improvements • Action Center for smart notifications • Background execution + triggers • Bluetooth-LE support for wearables + beacons • Internet Explorer 11 improvements Designed once; engaging everywhere • Converged developer platform • Converged app model • Shared app identities + entitlement • Unified push services (via WNS)
  • 14.
    14 Windows Phone 7.5Windows Phone 8.0 Convergence Begins with IE • WP 7.5 shipped with IE9 • Same rendering engine as Windows • Same JavaScript engine as Windows Converged Core (NT kernel) • Common kernel & file system • Kernel mode driver framework • Secure boot & storage encryption (BitLocker) • Core networking stack Developer Platform • Partial API convergence (focus on sensors & IAP) • Native Code (C++) and DirectX • IE10 Converging the Dev Platform • More skillset reuse • More code reuse • More seamless app experiences Aligning the Stores • Shared dev registration • Shared entitlement Common Core Platform • Proximity & Location frameworks • Security & identity • Task scheduler
  • 15.
    15 The Windows Runtime(WinRT) is the shared runtime and API space used by store apps across the Windows platform (phone and client) Dramatic convergence in 8.1 • Goal is 100% convergence for dev scenarios • In 8.0, we had ~30% API convergence • With 8.1, we move well past 90%+ convergence
  • 16.
  • 17.
  • 18.
  • 19.
    • One VisualStudio ‘Universal app’ project template for your app • Shared dev and test tooling for both platforms 20
  • 20.
  • 21.
    Provides a commonlayout coordinate system that extends along the x and y axis into infinity, allowing you to scale up 22 10” tablet 7” tablet 6” 5” 4.5” Infinite virtual canvas 166 Logical DPI
  • 22.
    23 80% exact sameXAML 20% custom Common SignatureOptimized DatePicker TimePicker CommandBar AppBar Button CheckBox RadioButton ProgressBar Slider ToggleSwitch Hub Pivot ListView GridView
  • 23.
    24 On Windows Phone8.1 … and on Windows 8.1
  • 24.
  • 25.
  • 26.
    27 Windows Notification Service (WNS) •Shared push service for Windows + Phone • Improved queuing to limit lost notifications due to intermittent network connectivity Tile templates + toasts • Shared tile templates (more!) • Periodic tile updates • Toasts
  • 27.
    Action Center • Centrallocation to surface missed notifications • Apps can intelligently manage notifications (silently add, update, and delete notifications) 28
  • 28.
    Device B WP 8.1– PFN 12345 Roaming Local Local Cache Temp Device A WP 8.1 App Roaming Local Local Cache Temp Backup [Device A]
  • 29.
  • 30.
  • 31.
  • 32.
    Anna beats alevel, with top score! The app asks her if she wants to share this with her friends? She says – “yes please!” Congratulations! Shall we share this? Share on: Anna is playing her favorite game. The level is almost over, and Anna could break her record. The application starts recording the screen. The application uploads the MP4 file, which was automatically transcoded to a VGA resolution for quick uploading, to a website for sharing.
  • 33.
  • 34.
  • 35.
  • 36.
    Internet Explorer 11brings more life to the mobile web via better HTML5 support 38 Ability to code pinning behavior • Specify high-resolution site icons • Live tiles using notifications Professional quality video • Adaptive streaming • Secure viewing • Accessibility improvements WebGL support Web spec based on OpenGL ES 2.0, to enable use of low-level 3D graphics APIs on web sites and HTML-based apps Rich user interactions • Screen + device orientation APIs • Pre-fetch and pre-render
  • 37.
  • 38.
  • 39.
  • 40.
  • 41.
  • 42.
  • 43.
    Supported operating systemsWindows 8.1 (x86 or x64) Hardware 4 GB of free disk space 1.5 GB of RAM (recommended) 64-bit (x64) motherboard To use the Windows Phone Emulators Windows 8.1 Pro or higher (for Hyper-V) and Second Level Address Translation (SLAT) Min 4GB RAM
  • 44.
  • 45.
  • 46.
  • 47.
    49 Approach Pros &Cons Keep using Silverlight 7.x/8 (Windows Phone 8 platform) Pros  Will run on Windows Phone 8.1 (app compatibility), still runs on earlier Windows Phone devices Cons  Will not take advantage of new platform capabilities  Will not enable targeting of Windows Use Silverlight 8.1 (Move Silverlight app into new execution stack and app package) Pros  Enables existing Silverlight apps to take advantage of nearly all new APIs and platform capabilities Cons  Will not enable targeting of Windows  Will not run on Windows Phone 8 devices Use Windows XAML platform Pros  Enables targeting of Windows and Windows Phone  Takes full advantage of new APIs and platform capabilities  Better performance & reduced memory use Cons  Will not run on Windows Phone 8 devices
  • 48.
  • 49.
  • 50.
    Primary features: Existing WindowsPhone 8 apps run flawlessly Windows Runtime XAML platform and HTML/WinJS support brings convergence with Windows 8.1, and is faster and uses less memory than Silverlight The core of an app can be built once for Windows and Windows Phone; you can share elements of UI, though it’s best to tailor the user experience for each platform Convergence is not just in the developer platform: it spans tools, store, commerce Developer investment in the existing Silverlight platform is protected: Existing Silverlight apps can be upgraded to access new Windows Phone 8.1 platform capabilities     
  • 51.
    Template designed by Domande? LorenzoBarbieri lorenzo.Barbieri@microsoft.com @_geniodelmale Template designed by