Recently I have been working on some investigation of modern apps development on Windows platform, so I think it might be necessary to have a reading list for the new developers to start their journey.
Every app will have two parts: UI and app core, and we know there are so many technologies can power up either one of this. One of the unique feature of Windows modern app is its support of multiple language and UI design approach under the same platform – Windows. So a good start can be from “Meet Windows Store Apps”.
Also, it is worthy to read the languages’ roadmap on MSDN so that you may have a better idea which language is a good fit for your needs.
Back to UI part, two approaches XAML and HTML have both advantages and disadvantages. Go through the navigation pattern of Windows Store App and Phone App may give you some idea about the flexibility and how much you can control the UI. Then you will see the different control list of XAML and HTML.
- Store App Navigation Pattern
- Phone App Navigation Pattern
- List of XAML-based UI Controls
- List of HTML-based UI Controls
For Windows Phone development environment, I would recommend you to go through some specials about XAML concepts and design library.
After you have some fundamental idea of the app development, you may have a question about how the UI part interact with the user. Well, this is obviously working through
events. Then I think you need to read a little about how the
event-handling works. Again, this is language dependent and Windows Phone has a different name set of its events.
Now, if you are at language choice decision stage, you might want to read this article on MSDN.
The answer is absolutely YES. Generally, two ways to do it:
Windows Runtime Component and
|Phone 8||C++||C++, C#, VB|
If your app consider XBOX 360 or potentially XBOX ONE, the Portable Class is something you are looking for because it covers more than just store app and phone app now. But you can only use C# to create the portable class. The difference between portable class and the runtime component is that portable class is binary level which is powered by .NET 4 platform, while runtime component just share the same code and API which needs compilation for different platform. A sample app use portable class is PixPresenter.
In general, the problem has been automatically solved by XAML if you use flexible controls such as Grid, CSS Grid and CSS multi-column layout. Fixed layout design is not recommend except for some game apps, so I would recommend you to read this guide. For Windows Phone, the rotation may need some manual work to make the UI more smoothly, like change the position of some buttons. (More to read here)
What if you have a different screen pixel density and I have photos to show? The answer is you always use higher quality graphics to scale down instead of lower quality graphics to scale up. (More information is here)
Currently, it is not possible for your to write your UI with both XAML and HTML5, but XAML and DirectX is possible. Or you can use a
One more thing you need to know about the Live API is the
Scope and Permission, which generally defines what security and privacy level your app is on so that the user may have a sense to control how they want to use your app. (Article)