In Windows Store apps for Windows 8.1 there are four basic input methods - touch, mouse, stylus and keyboard. In most of scenarios these input methods are all you need, but in case you want to offer more natural experience for controlling games on Windows 8.1, you can also add support for Xbox 360 and Xbox One controllers.
In this dev article I'll show you, how to use in any C#/XAML app or game for Windows 8.1 the Xbox 360 Controller API, how to detect presence of such controller and how to poll for current state of all buttons.
In my previous article I've shown a new way, how can we use Json file as a data source for design-time data in new Windows 8.1 apps. Luckily, it's possible to use similar approach in Windows Phone 8 apps as well!
When designing Windows 8.1 apps it's essential to have design-time data available in some way, so we can actually see how the app will look like.
Iris Class described in this great article, that there are several ways, how to achieve this:
- Using XAML – Design time data source set in XAML
- Using a ‘standalone’ data source class – Design time data source set in XAML
- Conditional data source – Design time data source set in code
But what I missed in this aticle is probably the most interesting way, how to use design-time data in Windows 8 apps - using external Json files. Here's a short guide, how to do it:
Just today I've published one of my first Windows Phone application Bugemos as Open Source on GitHub.
The app, that I created and published to Windows Phone Store back in late 2011, is just a simple RSS reader displaying latest comic strips from the web http://www.bugemos.com. The reason I'm publishing it as Open Source is that I think it might give a helpful insight to starting WP developers and to the community as well. Note the published source code is not the exact one, that was used in the currently published app. The app was updated from WP7.5 to WP8 and also instead of original AsyncCTP it now uses current Microsoft.Bcl.Async NuGet package.
So let's see, how is the application designed and what it does.
In this article I describe new developer APIs available in Windows Phone 8 GDR3/Update 3, at the time of writing this article the latest official version of Windows Phone OS.
First of all, GDR3 brings officially no new API, only minor changes in OS behavior, support for 1080p devices, devices with 2GB of RAM, couple of new Uri schemes and that's basically it. But what you might have noticed last week, Pedro Lamas described in his article Disabling screenshot functionality in a Windows Phone app one undocumented new property
After reading that article I was wondering, if there are another new APIs available in the GDR3 update, that can be accessed by reflection, so I stared my analysis.
In my third article of what to expect from Microsoft in 2014, I'll try to predict what we might see in the Xbox One ecosystem in the next year.
In my previous two articles about what to expect in 2014 in Windows Phone and Windows 8 I've already summarized my thoughts about these two platforms. I've been working with both these platforms for some time and I published already several nontrivial apps, but I've actually never written anything for any Xbox console (not counting my two XNA games for Windows Phone). I've also got my first Xbox 360 only about year ago, but the thing with Xbox One is different.
Let's start first with the current status of Xbox One ecosystem. Xbox One was released just 1 month ago in November 2013 with about 20 games released at the start, including several exclusive titles. Right now there is no option available for Indie game or App development. Program for Indie game developers ID@Xbox was already announced and smaller game studios or even independent developers can apply with a chance to get dev kit "sometime in 2014". All we know regarding this is probably on that page, nothing more. Note I'm not going to discuss the future of ID@Xbox program and indie game development on Xbox One in this article. I'm no game developer and as we know, the game development headed always in a bit different direction than app development on Windows, Phone and Xbox 360 platform.
Beside the ID@Xbox program, there nothing we know right now about possible indie App development for Xbox One. Although there are already some "major" apps on Xbox One, there is no public information how to create similar apps, even no information about used framework. As far as I know these are just modified web pages running on Xbox one with some private API for accessing Xbox One features.
Since the release of Xbox One there were only some rumors about possible indie app development, but just couple of days ago Microsoft announced the new Build 2014 conference in April 2014 and here is why I think we might get similar app Store on Xbox One just like we have on Windows 8.1 today...
In my second article of what to expect from Microsoft in 2014, I have gathered my thoughts on another popular platform - Windows 8 and Windows Store apps. My first article about Windows Phone in 2014 is here.
Just two months ago we've received the free Windows 8.1 update to all current Windows 8 installations, codenamed "Blue", almost exactly one year since the original Windows 8 release. This update fixed lot of quite annoying bugs when developing "Modern apps", added new tile sizes, various app widths, multi-monitor support, improved the sync between devices, added native SkyDrive integration, brought IE11 and also lof fixes and improvements under the cover. But since then there is no future plan of this platform. I guess it's quite early to predict any actual development in 2014, but let's do it anyway...
In my first article of what to expect from Microsoft in 2014, I'll gather my thoughts regarding the Windows Phone platform.
As we already know, there was no major update of WP platform in 2013. The last major update was WP8 in November 2012 and since then we have only seen minor updates called GDR1,2 and 3, or in Microsoft terms Update 1,2 and 3. These brought some small fixes and features asked by users + support for quad-core ad FullHD devices, but overall nothing breathtaking.
The year 2014 will be different. We can say almost for sure, that Microsoft will deliver the long awaited update with codename "Blue" and expected name Windows Phone 8.1. This update might be first mentioned on Mobile World Congress in February and maybe delivered as a beta version shortly after, or no later than after the BUILD 2014 conference in the early April 2014. Similarly to WP7.5 "Mango" that Microsoft delivered in 2011, WP8.1 should be available to all existing WP8 devices.
Beside WP8.1 we won't see most likely anything new that year, maybe only some kind of GDR5 update filling the gaps and bugs in not yet fully polished WP8.1 RTM version.
What to expect in WP8.1 from user's perspective?
This is my personal list of user features that we might expect in this update, sorted by my subjective probability.
Just a simple tip, what I just discovered recently - you probably know that when you play any music file or tune FM radio station on Windows Phone 8, this volume bar controls appear, when you press Volume Up/Down buttons. But even when you stop the music playback, there is no simple way, how to remove this media playback bar.
But since there is already at least one app, that can remove this Volume bar, I was wondering, how to do it in C# as well.
After couple of minutes tinkering with the MediaPlayer class I've discovered the solution, and it's pretty easy:
- You need to add into your app empty file with .wma extension and set the build action as "Content", for instance "empty.wma" into the app root folder.
- To stop the media playback and remove the media player just create dummy Song object and try to play it like this:
Song s = Song.FromUri("empty", new Uri("empty.wma", UriKind.Relative)); MediaPlayer.Play(s);
And that's all
Note I've tested this only on Windows Phone 8 device with GDR3 update, but I guess it will work on WP7.5 as well.
When developing Windows Phone application, which is more complex than just 3 screens and couple lines of text, you'll probably face the well-known problems of memory leaks. Even when using modern platform as Windows Phone 8, without pointers, with Garbage Collector, IntelliSense and everything, it is still quite easy to experience memory leaks in your apps.
In this article I'll go through 3 most common problems that are causing leaks when developing Windows Phone apps: Images, abandoned Pages and leaks in native controls. I'll also shown you simple trick, how to find your leaks early in the development and not two weeks before project deadline