Nearly all mobile devices (not necessarily cell phones, but anything that’s mobile enough) these days have sensors. And that will be our topic for today.

By the way, the way the term “mobile” is used today, reminds me an old anecdote with lady asking an IT guy, who tried to explain the difference between floppy disk and hard disk, whether that floppy disk isn’t hard enough for him. So, let’s settle on the definition that mobile devices are not stationery.

As we found previously, Windows 8 supports many platforms, and each platform has it’s own sensors, and new sensors are invented and need to be supported by OS.

Also, you may find out that your mobile device has more sensors than listed in your device specs. For instance, you may enjoy such sensors as compass and inclinometer, even though you have no such hardware in your device, and that’s because some sensors are “fusion”, or “virtual” – i.e. their data are results of computational analysis of data from other, “real” or “raw” sensors.

More...

As you, perhaps, already know, in Windows 8 you can develop Windows Store applications by using one of 3 ways:

It’s either C++ native application using DirectX, or C# / VB .NET application using XAML, or HTML5 / CSS3 / JavaScript application.

Although Microsoft says that it’s more a matter of style, there are some advantages and disadvantages in using each of these methods and we are going to discuss them now.

As you know, Windows 8 is the first Microsoft’s operating system whose kernel works on servers, workstations, tablets and even mobile phones, which means that it supports a lot of scenarios beyond the scope of any single platform. Windows 8 shares it’s kernel with Windows Server 2012 (servers), Windows RT (ARM based tablets) and Windows Phone 8 (mobile phones), but fortunately you can’t build application that would work on each platform without changes. This reminds me Linux (shares kernel with Android) and MacOS (shares kernel with iOS) – even though at low level it’s the same OS, what’s stands on the shoulders of that kernel is what makes real difference. As Ludwig Mies van der Rohe said, “the God is in the details”.

More...

New technologies allow us to reach new goals. Different tool sets enrich scenarios and it becomes easy to do things we couldn’t dream about before. We implement features so fast, that sometimes we just can’t analyze the impact until the most loyal customers uninstall our app.

Once upon a time I’ve downloaded the mobile application which made my phone a toy that could be handed to a kid. Just like the Kid’s Corner in Windows Phone 8, but for Android. It contained a few badly written games, but it was not the reason why I uninstalled it.

In Android, just like in Windows 8, you can use other apps to enrich your application with their services. Connect to social networks, send e-mails and whatever else.

What this particular application did – it used my e-mail application to send e-mail to developer of that application, to automatically register me as it’s user. I realized that only when I’ve received an e-mail with the password and warm “thank you” for registration which I didn’t commit or solicit.

In some countries that’s crime which could cost you your business.

The morale is – sometimes you can’t do what you can do. You can use contracts in Windows 8 (or their analogs in Android and iOS), but you shouldn’t do anything that your customer is not aware of and can’t cancel before it happens.

Here is a short story of a good idea gone bad, and a good lesson for mobile application developers.

The Preamble

We find ideas everywhere. The best place to find a good idea is where you wouldn’t look for it. The dump, graveyard, museum, park or simply the street of your city at night (in other words – any uncommon place for you) may bring something that would keep you busy for the next year. Or show the pitfall to avoid, and sometimes this knowledge comes with the price.