Windows
Windows
Today, we are pleased to introduce a for app developers that aligns software development concepts across the iOS, Android, and Windows platforms. App developers new to Windows 10, who are already familiar with Android or iOS, will be able to use this reference to quickly orient themselves on building for the UWP.
Like the 2nd century B.C. Rosetta Stone tablet, which enabled translation between three different ancient languages, this Windows app concept map can be used to translate ideas between Android, iOS, and Windows, making porting much easier between platforms. You can use the concept map side-by-side with other useful resources found in our section on MSDN. Reviewing this guide will help you port your apps to Windows and expose them to a larger user base.
Excerpt from the guidance document: a side-by-side map of data concepts in Android, iOS, and Windows.
The is broken out into 15 sections to make navigation between concepts and platforms simple:
At a glance, you’ll be able to see the difference between platforms and identify which features and functionality are available to each. The guidance is laid out in a convenient table that let you easily locate and learn more about the platform details you are most interested in. Android supports app widgets, for example, but iOS does not. iOS supports badges, on the other hand, while Android does not. Windows supports badges and also has a tile system.
Beyond development concept mapping, it’s worth noting that the Dev Center provides a large array of additional resources to help app developers bring their existing code to Windows 10. Here are just a few links to help get you started:
Bringing your mobile apps to the Universal Windows Platform (UWP) provides new reach for your existing code beyond mobile. For iOS developers, it’s also worth looking at the , which makes it easier to use your existing Objective-C codebase on Windows.
Like the 2nd century B.C. Rosetta Stone tablet, which enabled translation between three different ancient languages, this Windows app concept map can be used to translate ideas between Android, iOS, and Windows, making porting much easier between platforms. You can use the concept map side-by-side with other useful resources found in our section on MSDN. Reviewing this guide will help you port your apps to Windows and expose them to a larger user base.
Excerpt from the guidance document: a side-by-side map of data concepts in Android, iOS, and Windows.
The is broken out into 15 sections to make navigation between concepts and platforms simple:
- – overview of controls and styling– overview of controls and styling
- – toolbars, layouts and back buttons
- – speech recognition and beyond
- – databases, REST calls and web sockets
- – comparing IDEs
- – suspend and resume events as well as background tasks
- – threading, async calls and performance best practices
- – in-app purchases and trials
- – responsive layout and device capability testing
- – push and scheduled notifications as well as display widgets
- – video and audio
- – accessing raw and processed sensor data
- – maps, geofencing and geocoding
- – talking between different apps
- – overview of preferred design patterns by platform
At a glance, you’ll be able to see the difference between platforms and identify which features and functionality are available to each. The guidance is laid out in a convenient table that let you easily locate and learn more about the platform details you are most interested in. Android supports app widgets, for example, but iOS does not. iOS supports badges, on the other hand, while Android does not. Windows supports badges and also has a tile system.
Beyond development concept mapping, it’s worth noting that the Dev Center provides a large array of additional resources to help app developers bring their existing code to Windows 10. Here are just a few links to help get you started:
- ?
Bringing your mobile apps to the Universal Windows Platform (UWP) provides new reach for your existing code beyond mobile. For iOS developers, it’s also worth looking at the , which makes it easier to use your existing Objective-C codebase on Windows.