Category Archives: windows

microsoft, mobile, nokia, windows

Nokia at Mobile World Congress: aiming for a bigger market

At Mobile World Congress there are endless identikit Android smartphones. Does that justify Nokia’s decision two years ago to adopt Windows Phone? We will never know; but there is some merit in a distinctive offering, even though it comes with the pain of being a minority choice.

image

The press would prefer to see jaw-dropping new features on state of the art mobiles, but instead Nokia is delivering what the Windows Phone ecosystem actually needs: cheaper phones. Along with a couple of new feature phones, the 301 with a reasonable camera and Exchange email support, and the 105 at €15 and with a battery that lasts for a month, Nokia CEO Stephen Elop announced two new Lumia devices.

image

The 520 is €139 but still a full-featured Windows Phone 8 device, with a 4” screen, apparently the same camera lens as on a 920, and Nokia’s location apps which are now branded HERE: Maps, Drive and Transit, and Nokia Music with free “Mix Radio” or premium quality, lyrics and download for €4 per month.

The 720 has a more advanced camera with a large f/1.9 aperture and a wide-angle front camera (usually front cameras are rubbish). Wireless charging with an optional cover. The 720 will be €249.

These devices will be in Asian territories this quarter and Europe probably in the second quarter of this year.

Android phones are also available at this kind of price; but my observation is that Windows Phone plus Nokia design and manufacturing compares well to the cheaper Android offerings.

The significance of these phones is that they have the potential to grow the market for Windows Phone apps and maybe to persuade key names like the BBC (there is no iPlayer for Windows Phone) that the platform is worth supporting.

Nokia also announced that its mapping technology will be in Firefox OS. It wants more users for its location services in order to improve their quality. More users means more data.

Another announcement is that the API for Nokia location and imaging features are being opened to third-party developers.

hp, microsoft, mobile, windows

HP goes Android: what does that say about Windows 8?

1 Comment

Here at Mobile World Congress in Barcelona HP has announced a 7” Android tablet which will be available in April.

I took a quick look at the Mobile Focus event today. The back of the device is more interesting, showing logos for HP and for Beats Audio.

image

From the front you would be pushed to distinguish it from, say, Google’s Nexus 7. Black screen, runs Android.

I asked the guy on the stand what is distinctive about HP’s little Android slate in a crowded market. He said it had above average build quality, above average sound thanks to Beats Audio (you can find this discussed here), and support for HP’s printing system.

Not much, in other words; but the more interesting question is why HP is doing this. One reason is price. This will be a relatively cheap device, substantially less than any of HP’s windows machines, and without it HP would have little to no presence in the consumer tablet market.

Why not a Windows RT or Windows 8 device? That is the heart of it, and more interesting than the slate itself. HP is not giving up on Windows tablets, but it is positioning them more as business machines whereas the new slate is a consumer device.

The problem is that Microsoft has so far failed to make Windows 8 viable for this kind of market. It is too expensive, too peculiar, and there are too few worthwhile apps. That, and the Windows Runtime platform is not yet good enough, as developers at the sharp end discover. This means that HP has little choice but to go Android.

The form factor is also a problem. 7” seems to be beyond Windows Phone 8 territory, but too small for Windows 8 or RT bearing in mind the desktop and Office aspect. It is an awkward gap in the Windows offering.

The impression I got from several vendors at the show is that Microsoft is on the right lines with Windows 8, but the first release is disappointing on the tablet side.

What if HP starts to experiment with Android tablets that can be used like laptops, with neat keyboard cases and office-style applications? In the end the market will decide on the balance between Android and Windows, with the signs currently that Microsoft will struggle to gain momentum in the consumer tablet market.

.net, microsoft, mobile, mono, open source, professional, software development, windows

Xamarin 2.0 and Xamarin Studio announced, build for OSX, iOS and Android with C#

2 Comments

Xamarin has announced significant updates to its developer platform. Xamarin is the company formed around 18 months ago, when Novell discontinued its investment in Mono, a cross-platform implementation of C# and the .NET Framework. Its focus is on mobile platforms, in particular iOS and Android, though there is also support for the Mac. On Windows and Windows Phone, the presumption is that developers will continue to use Microsoft’s .NET Framework.

“If you look at what you can develop with C#, there’s about 1.2 billion Windows machines out there, but there’s now about a billion Android and iOS devices. Together we can make C# a universal language for application development and reach 2.2 billion devices,” Xamarin co-founder and CEO Nat Friedman told me.

“There’s a wonderful built-in audience of C# developers, millions of them, who need a bridge to mobile. We can help them take their existing skills and tools, and even code they’ve already written, and bring them to mainstream mobile platforms like iOS and Android.”

The key announcements:

  • Xamarin Studio is  an updated version of MonoDevelop, the Mono IDE. It runs on Mac and Windows.#
  • You can now develop iOS apps in Visual Studio for the first time
  • MonoTouch, the framework for iOS, has been renamed Xamarin.iOS
  • Mono for Android is now called Xamarin.Android
  • A new component store has pre-built components for download, some free, some commercial.
  • Xamarin now offers a free Starter edition, and pricing plans for independent developers, smaller businesses, and enterprises. Indie is $299 per platform per year, Business is $999 per platform/year, and Enterprise $1800 platform/year.

The Starter edition is not much use. It has a limited app size, and even the sample project I downloaded, an Employee Directory, exceeded that size and I had to register for a trial.

Xamarin’s philosophy is to share non-visual code, but to create a user interface that is native for each platform. This is a compromise in terms of the effort involved in supporting multiple platforms, but ensures a native experience on each device. “That’s fundamental to our platform,” says Friedman. “We tell our developers to separate the UI layer from the rest of the app. That allows them to share all the non-UI code across platforms, but to deliver a fully native UI, even though the whole app is written in C#. That’s what users demand now, people want native experiences.”

“We’ve been building tools that essentially project the underlying iOS APIs or Java [Android] APIs into C#”, explains co-founder Miguel de Icaza. “What it means is that people need to build a new UI for each platform.” He adds that Microsoft platform developers should be used to this, as Microsoft itself has several similar but incompatible .NET platforms. “There’s the one on Silverlight, the one on WPF, the one on Windows RT, and the one on the phone, it’s four,” he says. “Developers have had to resort to putting their logic into shared libraries, and build a per-platform UI. We’re reusing that knowledge.”

The ability to develop for iOS in Visual Studio is new. “It’s our most-requested feature of all time.” said Friedman.

I downloaded Xamarin Studio, which in my case was around 1.3GB including an updated Android SDK.

image

The IDE itself is clean and fast, and very much code-centric. It lacks the bloat of Visual Studio, though you will miss many of the features of Microsoft’s IDE.

image

I build the sample Employee Directory app and deployed it to an Android emulator which I use for Nexus 7 development. Deploying the runtime components took a long time, but after waiting patiently the app launched successfully.

image

If you want to do iOS development you will need a Mac of course. Although you can code on Windows, if you then the code is pushed over the the Mac side for compilation and debugging. In order to use Visual Studio, one option is to run Windows in a virtual machine on a Mac, as I have done with reasonable success using Embarcadero’s cross-platform tools.

Xamarin says it is growing fast. There have been 230,000 downloads of its tools, increasing by around 700 per day, and over 12,000 paying customers.

Despite Xamarin’s roots in the open source world (and Mono is still open source), a quick look at the pricing table shows that this is a fully commercial offering and priced accordingly. Presuming customers keep on subscribing, that is a good thing, ensuring the future of the platform; but it is not so good for the smallest developers who might otherwise give it a try.

mobile, reviews, smartphones, windows

Review: Nokia Lumia 620, a winner when the price is right

1 Comment

Nokia’s Lumia 620 is now widely available in the UK, and was offered recently at just £120 (including VAT) by O2 on a pay as you go deal (which means that the amount of operator subsidy is small). That struck me as an excellent deal, especially as I already have an O2 sim, so I got one to take a look.

image

The Windows Phone with which I am most familiar is the first one Nokia produced, the Lumia 800, which is still widely available at a similar price to the 620. The 800 is a beautiful phone with a high quality feel, though my early model has a dreadful battery life and suffered from charging problems (going into a state where it could not be charged without much coaxing) until at last a firmware update seemed to fix it.

The 620 is lighter and very slightly smaller than the 800, and feels more ordinary in design and manufacture. On the other hand, it is up-to-date and runs Windows Phone 8, whereas the 800 is stuck with Windows Phone 7.5 or 7.8. The 620 also benefits from a Qualcomm Snapdragon S4 Plus system chip, 1Ghz dual core, versus the 1.4Ghz single core Scorpion and MSM8255 Snapdragon in the 800.

In the picture below, the Lumia 620 is on the left and the 800 on the right.

image

Do not be misled by the apparently faster clock in the 800 (1.4 Ghz vs 1.0 Ghz). In practice, I found the 620 performs much better than the older single-core CPU. Here are my Sunspider Javascript results:

  • Lumia 800: 6987ms
  • Lumia 620: 1448ms

I also have a Lumia 820 on loan. This is the true successor to the 800 and has a gorgeous 4/3″ AMOLED display plus a Snapdragon dual-core 1.5 Ghz chip. It completed Sunspider in just 910ms.

Still, the 820 is around £350 on pay as you go deals, more than double what I paid for 620. It is in a different high-end market, whereas the 620 is in an affordable category alongside dozens of budget Android phones like the HTC Desire C, Samsung Galaxy Ace 2 or Sony Xperia U. If Microsoft is to make real progress with Windows Phone 8, it has to be competitive here as well as at the higher end of the market.

You can see how Nokia has reduced the cost of the 620. The screen is TFT Capacitive, not AMOLED, and looks dim and small next to an 820. The battery is a small 1300 mAh affair, slightly smaller than the one in an 800. The side buttons feel like cheap plastic.

That said, I would rather focus on what the 620 does have, including A-GPS, Bluetooth 3.0, microSD card slot, 5MP camera with flash, front VGA camera, NFC (Near Field Communication) support, accelerometer and compass.

Two significant advantages over the old Lumia 800 are the removable battery (so you can carry a spare) and the microSD card slot, supporting up to 64GB of additional storage.

One thing I noticed with the 620 is that charging the battery is super quick. I have not timed it yet, but it charges considerably faster than the 800.

Battery life when on standby is substantially better than the Lumia 800. With light usage and wi-fi off, I am getting more than 2 and half days.

image

There is 512Mb RAM and 8GB storage; reasonable at this price. The Lumia 610, predecessor to the 620, had only 256Mb RAM which caused app compatibility issues.

Getting started

The out of box experience for me was pretty good. I put in my O2 sim, which worked without any issues. The setup asked for my Microsoft account and password which also worked, though as is typical with Microsoft, I found myself having to enter this several times more when setting up the SkyDrive app.

I have my own Exchange server which uses self-signed certificates. I installed the certificates and rather to my surprise auto-discover then worked and I was able to add my Exchange account to Outlook on the device without my having to enter the server details.

So far so good; but I was expecting some sort of automatic or semi-automatic process of installing the apps I was using on the Lumia 800, but this is more difficult than it should be. Nothing appeared automatically. You have to go to the store and re-install. You can reduce the work slightly by going to your purchase history online and selecting Reinstall; but in many cases that does not work and there is a message saying “App not available on the Web. Try downloading it on your phone.”

That is a shame, since this works well for Windows 8 store apps. The experience of upgrading to a new Windows Phone should be like this:

  1. Buy new phone.
  2. Enter Microsoft account details.
  3. Wait a bit, then carry on where you left off with all apps in place.

Unfortunately we are not there yet.

The new Windows Phone 8 Start screen is a considerable improvement. The big deal is that you can get four times as many icons on the screen, so no need to waste all that space. The Live Tile concept works better on the phone than it does in Windows 8, since you see the Start screen more often. I might work for hours on a PC and never see the Start screen.

The supplied earbuds/microphone are functional but not very good. The sound is mediocre and the earbuds do not feel secure. Incidentally, a much better set comes with the 820; but in practice most of us have our own favourite headset already and I would not mind if Nokia did not bother to include this in the box. Audio with a better quality set is fine, and after copying some MP3s to the device I was happy with the sound.

Once during the course of this review the phone rebooted itself for no apparent reason. Once it froze and I had to remove and replace the battery. Hmm.

Fitting a memory card

The 620 accepts a microSD card up to 64GB. Fitting is not too difficult, though slightly fiddly. First remove the back. Then slide back the silver card holder until it pops up.

image

Insert the card and close the holder.

image

Camera

The camera captures images at 2592 x 1936 pixels. It is fine for the use I am likely to make of it, bearing in mind that I am not yet ready to abandon carrying a separate camera. The camera software supports extensions called “lenses” which let you process the image. An example is Translator which lets you point the camera at some text and have it translated, an intriguing idea from which I got mixed results.

image

I was disappointed to find that Blink, from Microsoft Research, will not install as apparently the 620 does not meet minimum requirements, though I cannot quickly see in what way it falls short.

One small feature that I like on Windows Phone is that you can press the camera button even the phone is locked and use the camera.

Nokia Apps

Nokia has some exclusive apps, of which my favourite is Nokia Drive. I have found it works pretty well for turn-by-turn directions and no longer use my Tom Tom. The 620 lets you install Nokia Drive + Beta, giving you free downloadable maps and offline directions.

City Lens is a fun app that uses augmented reality to superimpose nearby attractions on the image from the phone’s camera. It has some promise, though it asks me to “Calibrate your compass” every time it starts up, which means waving your arms in the air and probably hailing a taxi by mistake.

More seriously, City Lens is only as good as its data, and in my part of England it is not good enough yet, with only a few local businesses showing.

Nokia Transit gives you public transport directions, and worked OK when I asked for directions to my nearest airport, giving a sensible bus route. The app integrates with Nokia Maps for directions and I found the user interface a bit perplexing. The app also freaked out when I asked how to get to London. Sensible options would include my local railway station, which has an hourly service, or a National Express coach from the nearest city centre. Instead, Nokia Transit proposed a seven hour bus journey with numerous changes, starting yesterday (I am not joking). Then the app crashed. Still, looks like it could be useful for local bus journeys.

Nokia Music gives you “Mix radio” for free, and a download service for a per-track fee. Fair enough, though the quality of the Mix radio is indifferent.

Nokia Smart Shoot takes five pictures at a time, and lets you select the best, superimpose faces from one on those of another, or remove people or objects. Face transposition is not my thing, but taking five images at a time makes sense. You can then flip through to find the best, and save it. Useful.

Creative Studio (I am surprised Nokia can use that name) is a simple photo editing app that lets you crop and rotate, remove red eye, adjust colour balance and brightness and so on. It is simple but rather good.

SkyDrive

Microsoft’s cloud storage service SkyDrive is integral to Windows Phone 8. If you follow the setup defaults, photos and videos end up there, though in slightly reduced quality, and it also forms storage for the Office Hub. It is free for up to 7GB of storage and generally works well. Windows Phone would be crippled without it.

Local Scout

Local Scout is an official Windows Phone app that is meant to give information and ratings for local businesses such as shops, restaurants and attractions.

Excuse me while I have a rant. Local Scout was introduced in Windows 7.5 “Mango”, made available in September 2011. It has potential, but I noticed at the time that the data was not that good. In my local area, it included a restaurant that has closed, for example. I hit the link that said “Tell us this place is closed.”

As you can guess, the restaurant is still listed, more than a year later.

There is also a bit of a mystery about Local Scout. It has ratings and reviews, but there is no obvious way to add your own rating or review. The data must come from somewhere, but there are relatively few contributions for the places near me and the app would be more useful with community content.

Local Scout on the Lumia 620 (and on the 820) seems to have got worse. There is no longer a “suggest changes” link so you can no longer easily report that a place has closed. You still cannot add ratings or reviews for places you visit.

All a bit of a disaster. My hunch is that some team created Local Scout for Mango and made a reasonable but incomplete job. Since then, someone decided that it is not important and the thing is essentially frozen. It is still there though; it seems to me that Microsoft should either improve it or abandon it.

This is important because it influences the experience when you pick up a Windows Phone and try to use it. Of course you can use Yelp or TripAdvisor or something else instead; but why does Local Scout occupy a precious spot on the default Start Screen, on most Windows Phones I have seen, when it is so broken?

Office

The Office hub on Windows Phone lets you create, view and edit Word and Excel documents, and view and edit PowerPoint documents. At least, you might be able to. I tried some recent documents on SkyDrive. A PowerPoint opens beautifully, and I can easily edit or hide individual slides. On the other hand, another document I have been working on will not open; it downloads, then the screen flashes slightly, but it never opens. An Excel document downloads and views OK but comes up with a message “can’t edit workbook”.

In both cases, there are in the old binary Office document formats. I tried converting them to the new XML based formats (docx and xlsx) and they worked fine, both for viewing and editing. My recommendation then is to use the new Office formats if you want full access on your Windows Phone.

You can add comments to documents, which is a great feature for collaboration.

If you want to know in detail what will work on the phone, see here, and especially the entry “Why can’t I edit some Microsoft Office documents on my phone?”. This lists “common reasons” why a document cannot be edited. It does not say anything about documents which simply will not open so I guess that is unexpected behaviour.

Given the complexity of Office documents, it is not surprising that there are limitations. On the other hand, it does seem to me problematic that the question of whether you will be able to edit any particular document is, from the user’s perspective, rather hit and miss; and if there are many instances where documents do not open at all I will soon lose confidence in the app.

In an emergency, you could try going through the browser instead, since SkyDrive supports the Office Web Apps.

It may be imperfect, but the Office hub is miles better than nothing.

Other apps

Windows Phone remains a minority taste, and if you want the best and widest selection of apps, you should stick to Apple iOS or Google Android.

That said, the Windows Phone Store does have over 125,000 apps, increasing at around 500 apps per week according to windowsphoneapplist.  Some big names are present, including Twitter, Spotify, Amazon and Google; others are missing or only supported by third party apps, including BBC iPlayer, Dropbox and Instagram. Whether any of these (or others) are deal-breakers is up to the individual.

On the other hand, the strong web browser (see below) means good performance from web apps, which mitigates issues with missing native apps.

YouTube works well full-screen in the browser. Unfortunately BBC iPlayer does not.

A bonus for Xbox users is Xbox SmartGlass, which gives remote control of your console plus a few extras.

image

Internet

Windows Phone 8 includes the Internet Explorer 10 browser, and it is excellent, fast and with decent standards support. It gets a score of 320 at html5test.com, which by no coincidence is the same as IE10 in Windows 8.

image

The 620 also includes the simple, effective internet sharing hotspot feature which was introduced in Windows Phone 7.5, but worth mentioning since it is so useful.

Conclusion

Any budget smartphone is a compromise. The Nokia Lumia 620 is not beautiful to hold, the screen is not the best, the processor is 1.0Ghz rather than the 1.5Ghz on the high-end Lumias, and the battery a bit small.

Nevertheless this is a full Windows Phone 8 smartphone, performance feels snappy, and it supports a generous range of features. It fixes annoyances seen in some earlier Lumias, with a replaceable battery and no fiddly flap over the micro USB port.

The Lumia 620 is a better choice than the old Lumia 800, still on sale at a similar price. It performs basic functions admirably, and has valuable extras like Nokia Drive +. Outlook and the Office hub make it a good choice for Microsoft platform users on a budget.

The Windows Phone 8 OS itself is nice to use but in some areas not as good as it should be. Some of the supplied apps, like Local Scout, are not good enough, and a few crashes suggest bugs.

Web browsing is great though, and strong features like add-on “lenses” for the camera app make up for a few flaws.

In summary, a Lumia 620 is a great way to see what Windows Phone can offer at a budget price. If you can find one for under £150 it is a great deal.

Lumia 620 Key specifications

3.8” display

Dual-core Snapdragon S4 1.0 Ghz, Adreno 305 GPU

Wi-fi 802.11 a/b/g/n, Bluetooth 3.0, NFC

5MP camera with flash, front-facing VGA camera

8GB storage, 512MB RAM, MicroSD up to 64GB

1300 mAh battery

A-GPS

Magnetometer

Ambient light sensor

Orientation sensor

Proximity sensor

microsoft, mobile, windows

Windows Phone 7.8 Live Tiles are buggy, say users

When Microsoft announced Windows Phone 8, one disappointment was that existing phones would not be upgraded to the new mobile operating system. In mitigation, Microsoft promised Windows Phone 7.8 instead, an upgrade to Windows Phone 7.5 that implements the most visible feature of WP8, a new Start screen with more flexible live tiles that can be sized small and other new features.

Some users are now receiving 7.8 upgrades, but the news is not all good. According to reports on the Windows Phone Central forum, many users find that the Live Tiles are not refreshing correctly after the upgrade.

image

The idea of Live Tiles is that they refresh in the background with the latest data, such as news alerts or incoming emails.

Developers Heathcliff writes in detail about the problem. He describes three methods to update a Live Tile. The basic ShellTile.Update method works OK, he says. However, if you use an external URL to update a tile, using ShellTileSchedule.Start, it “behaves erratically” and may trigger a problem that drains your battery and makes excessive use of your data connection. Finally, HttpNotificationChannel.BindToShellTile, which uses Microsoft’s notification servers, does not seem to work at all.

On WP 7.5 this method just works as expected. I actually hope I did something wrong here. Or else I don’t understand how this could ever get past the Microsoft Quality Assurance department.

he says.

Finally, users also complain of slower performance after the update, which makes starting apps more laggy.

If Microsoft has put more effort into its new Windows Phone 8 operating system than into an update for existing user, that is understandable, but short-sighted. Those existing users are the best possible evangelists for the platform as well as potential repeat customers; and Windows Phone with its tiny 2.6 per cent global market share, according to IDC, needs all the help it can get.

That said, with decent new WP8 phones like the Nokia 620 available cheaply (O2 in the UK offered this for £120 pay as you go earlier this week), existing Windows Phone 7 users who want to stay up to date are better off buying a new device.

microsoft, windows

Windows 8: Forget Surface Pro, what matters is the app platform

9 Comments

Microsoft has launched Surface Pro, its own-brand Windows 8 tablet, causing the usual agitation.

  • The 128GB model is sold out online, but has it sold well, or did Microsoft only make a few?
  • Is it too expensive for the spec?
  • Is the battery life too poor?
  • Can you type properly with it on your lap?

All reasonable questions, but to me rather unimportant.

When Microsoft “reimagined” Windows, its goal was to establish its operating system as a new tablet platform. Otherwise, there would have been no sense in upsetting millions of Windows users who were broadly happy with Windows 7, by imposing a new touch-friendly, blocky, mainly single-tasking platform on top of the old familiar Windows.

How is it doing so far? Not well. The reviews for Surface Pro are a symptom of this. It is being treated mainly as an Ultrabook with a detachable keyboard rather than as a tablet. That is a shame, since Surface (RT and Pro) is designed to be tablet-first, with the keyboard cleverly designed into the cover to mitigate the difficulty of using touch alone when you have to use desktop apps.

There are several reasons why Surface is seen as a kind of laptop rather than as a tablet.

First, Microsoft has so far failed to change the way Windows is perceived. People buy Windows devices to run Windows apps, by which they mean Microsoft Office, Skyrim, Foobar2000, and/or their corporate apps written in Visual Basic or C#. The existence of the new Windows Runtime platform is incidental and mainly annoying, since it can get in the way if you only want to run Windows.

This could soon change if there were numerous compelling apps on the new platform; but there are not, and that is reason number two. Which Windows Store apps are better (presuming you have a tablet) than their desktop equivalent, or which are great apps that have no desktop equivalent? It is a short list. Personally I would name the Wordament game, Maps, and the Weather app as examples; and yes, I know how lame that sounds.

Microsoft slipped up badly by spending so little effort on the built-in apps, especially Mail, but also Music and others. The result is that users spend little time in the new user interface (I am guessing but have anecdotal evidence). The further result is that the platform is unattractive to developers, despite the size of the Windows market.

Take a look at the MetroStore Scanner  and you can see that around two hundred apps are added most days (green is updates rather than additions).

image

That in itself does not tell us much. Just one hundred great new apps would be fantastic news for the platform. But no, they are mostly trivial and/or poor and/or repetitive and/or uninteresting.

Why are developers not building more and better apps? That indeed is the question. The main reason of course is that size of the market, not in terms of the numbers of Windows 8 users out there, but in terms of likely sales or adoption.

This is circular though. Good apps will increase the size of the market. So what else?

My views on this changed when I sat down to build my own app, simple though it is. This was harder than I expected, and there is still a z-order bug which I have not got round to fixing. A core question though is this: does the platform help developers to build apps that delight the user? In this respect it is not yet good enough. The kind of app you will build if you follow all the guidelines will be genuinely touch-friendly, but look a bit blocky and spaced out too much. There is also the problem of the disappearing menu bar and the fact that users do not always discover options hidden in the Charms bar. It is too easy to build apps that are not good enough. I regard the poor quality of apps like Mail as evidence of this.

Put another way, it is not yet a platform that inspires developers and makes them want to support it, despite its immaturity.

Windows 8 is not going well then; but I do not write it off. Better apps surely will appear. Further, Microsoft’s next go at this, whether it is called Blue or Windows 8.5 or Windows 9, should be better as the team fix annoyances and add compelling features.

As yet though, there is no sign of Microsoft averting the march of Windows towards being a business-oriented, desktop platform occupying an ever-smaller niche in a world of mobile and browser apps. If I were CEO Steve Ballmer, I would find that a concern.

microsoft, windows

Why is Windows 8 not selling better?

6 Comments

The Register reports a rumoured blame game playing out between Microsoft and its OEM partners concerning why Windows 8 sales have not taken off in the hoped-for manner.

A separate source at a major Windows 8 PC maker confirmed frustration is simmering inside Microsoft, and the blame is settling on PC makers. He said [Microsoft] "is pinning the blame on the manufacturers for not having enough touch-based product".

PC makers on the other hand:

PC makers, though, are hitting back after Redmond’s finger-pointing – countering that if they’d followed Microsoft’s advice they’d have ended up building very expensive tablets and would have been saddled with the costs of a huge piles of unsold units. Those who did buy Windows 8 PCs ultimately bought the cheap laptops not high-end Ultrabooks or hybrids.

This is a silly discussion. I agree that not enough tablets were available at launch. On the other hand, the OEMs are correct: the market for high-end expensive hybrids is limited, and rightly so as they are not good value for most users.

What both sides seem to be ignoring is that Windows 8 was always going to be a hard sell. Microsoft made a conscious and deliberate decision to create a new tablet platform and bolt it on to desktop Windows in order to establish it. The added value for users who just want to run Office and other desktop apps is small, while the cost in terms of learning to find your way around a new Start screen is significant.

This could yet work out well for Microsoft. As the platform matures and better new-style apps appear, Windows 8 will become more attractive. Further, as users discover that Windows 8 is not really hard to use, the reasons not to upgrade will diminish. In theory, users will gradually be able to spend more time in the touch-friendly user interface rather than in the desktop, making pure tablet use of Windows 8 (no keyboard or mouse) more attractive.

The counter-argument is that Windows may never shake off its desktop inheritance and that the Metro-style platform will never be important.

Maybe Microsoft should have communicated "let’s have a low-key launch and build this slowly" rather than spending big on marketing in the hope that nobody would notice these issues.

It is true that there are big and long-standing problems with the way Windows machines are designed, built and marketed, problems that have caused Microsoft to create its own Surface devices (I am typing this on Surface RT) and to copy Apple by opening its own stores, selling "signature" PCs with third-party rubbish removed.

In addition, Microsoft made inexplicable mistakes with the launch of Windows 8 and Windows RT, such as building a mail app that is barely competent – one app that almost everyone will try and which could have been used to show off the potential of the new platform. Check the reviews; there is even something odd about the few five-star ratings.

That does not mean that the subdued launch of Windows 8 is mainly Microsoft’s fault, or mainly the fault of its partners. The reasons are more obvious and more fundamental.

azure, microsoft, professional, systems, windows

Making sense of Microsoft’s Cloud OS

4 Comments

People have been talking about “the internet operating system” for years. The phrase may have been muttered in Netscape days in the nineties, when the browser was going to be the operating system; then in the 2000s it was the Google OS that people discussed. Most notably though, Tim O’Reilly reflected on the subject, for example here in 2010 (though as he notes, he had been using the phrase way earlier than that):

Ask yourself for a moment, what is the operating system of a Google or Bing search? What is the operating system of a mobile phone call? What is the operating system of maps and directions on your phone? What is the operating system of a tweet?

On a standalone computer, operating systems like Windows, Mac OS X, and Linux manage the machine’s resources, making it possible for applications to focus on the job they do for the user. But many of the activities that are most important to us today take place in a mysterious space between individual machines.

It is still worth reading, as he teases out what OS components look like in the context of an internet operating system, and notes that there are now several (but only a few) competing internet operating systems, platforms which our smart mobile phones or tablets tap into and to some extent lock us in.

But what on earth (or in the heavens) is Microsoft’s “Cloud OS”? I first heard the term in the context of Server 2012, when it was in preview at the end of 2011. Microsoft seems to like how it sounds, because it is getting another push in the context of System Center 2012 Service Pack 1, just announced. In particular, Michael Park from Server and Tools has posted on the subject:

At the highest level, the Cloud OS does what a traditional operating system does – manage applications and hardware – but at the scope and scale of cloud computing. The foundations of the Cloud OS are Windows Server and Windows Azure, complemented by the full breadth of our technology solutions, such as SQL Server, System Center and Visual Studio. Together, these technologies provide one consistent platform for infrastructure, apps and data that can span your datacenter, service provider datacenters, and the Microsoft public cloud.

In one sense, the concept is similar to that discussed by O’Reilly, though in the context of enterprise computing, whereas O’Reilly looks at a bigger picture embracing our personal as well as business lives. Never forget though that this is marketing speak, and Microsoft consciously works to blur together the idealised principles behind cloud computing with its specific set of products: Windows Azure, Window Server, and especially System Center, its server and device management piece.

A nagging voice tells me there is something wrong with this picture. It is this: the cloud is meant to ease the administrative burden by making compute power an abstracted resource, managed by a third party far away in a datacenter in ways that we do not need to know. System Center on the other hand is a complex and not altogether consistent suite of products which imposes a substantial administrative burden on those who install and maintain it. If you have to manage your own cloud, do you get any cloud computing benefit?

The benefit is diluted; but there is plentiful evidence that many businesses are not yet ready or willing to hand over their computer infrastructure to a third-party. While System Center is in one sense the opposite of cloud computing, in another sense it counts because it has the potential to deliver cloud benefits to the rest of the business.

Further confusing matters, there are elements of public cloud in Microsoft’s offering, specifically Windows Azure and Windows Intune. Other bits of Microsoft’s cloud, like Office 365 and Outlook.com, do not count here because that is another department, see. Park does refer to them obliquely:

Running more than 200 cloud services for over 1 billion customers and 20+ million businesses around the world has taught us – and teaches us in real time – what it takes to architect, build and run applications and services at cloud scale.

We take all the learning from those services into the engines of the Cloud OS – our enterprise products and services – which customers and partners can then use to deliver cloud infrastructure and services of their own.

There you have it. The Cloud OS is “our enterprise products and services” which businesses can use to deliver their own cloud services.

What if you want to know in more detail what the Cloud OS is all about? Well, then you have to understand System Center, which is not something that can be explained in a few words. I did have a go at this, in a feature called Inside Microsoft’s private cloud – a glossary of terms, for which the link is currently giving a PHP error, but maybe it will work for you.

image

It will all soon be a little out of date, since System Center 2012 SP1 has significant new features. If you want a summary of what is actually new, I recommend this post by Mike Schutz on System Center 2012 SP1; and this post also by Schutz on Windows Intune and System Center Configuration Manager SP1.

My even shorter summary:

  • All System Center products now updated to run on, and manage, Server 2012
  • Upgraded Virtual Machine Manager supports up to 8000 VMs on clusters of up to 64 hosts
  • Management support for Hyper-V features introduced in Server 2012 including the virtual network switch
  • App Controller integrates with VMs offered by hosting service providers as well as those on Azure and in your own datacenter
  • App Controller can migrate VMs to Windows Azure (and maybe back); a nice feature
  • New Azure service called Global Service Monitor for monitoring web applications
  • Back up servers to Azure with Data Protection Manager

and on the device and client management side, new Intune and Configuration Manager features. It is confusing; Intune is a kind-of cloud based Configuration Manager but has features that are not included in the on-premise Configuration Manager and vice versa. So:

  • Intune can now manage devices running Windows RT, Windows Phone 8, Android and iOS
  • Intune has a self-service portal for installing business apps
  • Configuration Manager integrates with Intune to get supposedly seamless support for additional devices
  • Configuration Manager adds support for Windows 8 and Server 2012
  • PowerShell control of Configuration Manager
  • Ability to manage Mac OS X, Linux and Unix servers in Configuration Manager

What do I think of System Center? On the plus side, all the pieces are in place to manage not only Microsoft servers but a diverse range of servers and a similarly diverse range of clients and devices, presuming the features work as advertised. That is a considerable achievement.

On the negative side, my impression is that Microsoft still has work to do. What would help would be more consistency between the Azure public cloud and the System Center private cloud; a reduction of the number of products in the System Center suite; a consistent user interface across the entire suite; and simplification along the lines of what has been done in the new Azure portal so that these products are easier and more enjoyable to use.

I would add that any business deploying System Center should be thinking carefully about what they still feel they need to manage on-premise, and what can be handed over to public cloud infrastructure, whether Azure or elsewhere. The ability to migrate VMs to Azure could be a key enabler in that respect.

microsoft, mobile, visual studio, windows

Hacking Windows RT and Surface RT to run desktop apps

3 Comments

A developer on the XDA Developers forum, known as clrokr, has figured out how to run unsigned applications on Windows RT (Windows on ARM), including Microsoft’s own-brand Surface RT device.

The technique is described here and involves patching the Windows kernel. Currently it is not possible to jailbreak Windows RT completely, because Secure Boot prevents tampering with the system files, but it can be done after booting by using the remote debugger:

The minimum signing level determines how good an executable’s signature is on a scale like this: Unsigned(0), Authenticode(4), Microsoft(8), Windows(12). The default value on x86 machines is of course 0 because you can run anything you like on your computer. On ARM machines, it defaults to 8.
That means that even if you sign your apps using your Authenticode certificate, the Surface or any other Windows RT device (at this moment) will not run them. This is not a user setting, but a hardcoded global value in the kernel itself. It cannot be changed permanently on devices with UEFI’s Secure Boot enabled. It can, however, be changed in memory.

There is further discussion on the forum here. The technique is not practical for most users yet.

According to clrokr:

The decision to ban traditional desktop applications was not a technical one, but a bad marketing decision. Windows RT needs the Win32 ecosystem to strengthen its position as a productivity tool. There are enough “consumption” tablets already.

Personally I have mixed feelings about this. If I understand the concept correctly, Windows RT is meant to have iPad-like ease of use as well as excellent security. Configuring the operating system so that only code signed by Microsoft or Windows Store apps will run is a key part of the implementation. Surface RT is not as good as it should be, in part because there is too much old-style Windows, not too little.

On the other hand, the usefulness of Windows RT is limited by the absence of key apps. There are certain things missing, like the ability to play FLAC files, and until recently, an SSH terminal client (there is one now). Looking at the thread on XDA Developers, note that among the first things users are keen to port are putty (open source SSH client) and VLC (open source multimedia player).

image

That said, personally I would rather see suitable apps come to the Windows Store, rather than introduce all the problems and complexities of desktop Windows to Windows RT.

.net, google, microsoft, mobile, software development, web authoring, windows

Google the new Microsoft, goes to war on Windows Phone users (updated)

6 Comments

Google has fired a one – two – three salvo at Microsoft and Windows Phone users. Consider the following.

First, we learn that Google, under the guise of Winter cleaning, is removing Google Sync from its Mail, Calendar and Contacts online products, for consumers only. This is the Exchange ActiveSync protocol used by Windows Phone and other mobile devices:

Starting January 30, 2013, consumers won’t be able to set up new devices using Google Sync; however, existing Google Sync connections will continue to function

Next, Microsoft reveals that Google is blocking the creation of a YouTube app for Windows Phone:

Microsoft is ready to release a high quality YouTube app for Windows Phone. We just need permission to access YouTube in the way that other phones already do, permission Google has refused to provide.

Now Google is blocking Windows Phone users from accessing Google Maps in the mobile browser. Google says:

The mobile web version of Google Maps is optimized for WebKit browsers such as Chrome and Safari. However, since Internet Explorer is not a WebKit browser, Windows Phone devices are not able to access Google Maps for the mobile web.

but Microsoft observes that Google Maps works fine in IE on Windows and:

Internet Explorer in Windows Phone 8 and Windows 8 use the same rendering engine.

This last is of most concern. It is one thing to “optimize” for WebKit, another specifically to block non-WebKit browsers. If WebKit is in Google’s eyes the de facto standard for mobile devices – which are more significant than desktop browsers – then what is the function of the W3C, and what is to prevent a repetition of the IE6 effect where one company (Microsoft) in controlled what was implemented for most users?

We can conclude that Google has decided its interests are better served by inconveniencing Windows Phone users in the hope of stifling the platform, rather than trying to persuade Windows Phone users to use its services as it does on Apple’s iOS platform (with considerable success).

Sympathy for Microsoft will be limited because of its history. The company has never been a friend of cross-platform support, preferring to keep its customers on Windows. That said, it is difficult to find exact analogies for what is happening now. Nor is it clear what is and is not reasonable. Google Mail, YouTube and Maps are all Google properties. Is it reasonable to expect Google to make the extra effort required to support additional platforms? It is a matter for debate with no easy and clear cut answer.

This does not mean you have to like it. If it is Windows Phone today, what platform might it be tomorrow? Google’s willingness to lock out users of other platforms is a warning, and one that should give pause for thought to any individual, business or government entity who depends or is considering depending on the Google platform. If history tells us anything, it is that monopoly and lock-in always works out badly for users. Check the price of inkjet cartridges for a simple example, or the price of Microsoft Office for business users for another.

What will be the effect on Windows Phone of Google’s campaign? That again is hard to judge. Microsoft is better off than RIM, for example, because it does have something like a complete stack of what it takes to be a mobile platform, especially in conjunction with Nokia: search, maps, email, web-based documents, cloud storage, music streaming and so on. That said, “doesn’t work properly with YouTube, Gmail, Google Maps” is hardly a selling point.

Update: Google now says:

We periodically test Google Maps compatibility with mobile browsers to make sure we deliver the best experience for those users.

In our last test, IE mobile still did not offer a good maps experience with no ability to pan or zoom and perform basic map functionality. As a result, we chose to continue to redirect IE mobile users to Google.com where they could at least make local searches. The Firefox mobile browser did offer a somewhat better user experience and that’s why there is no redirect for those users.

Recent improvements to IE mobile and Google Maps now deliver a better experience and we are currently working to remove the redirect. We will continue to test Google Maps compatibility with other mobile browsers to ensure the best possible experience for users.

Is Google being straight with us? Why has the statement changed overnight?

One user discovered that certain URLs work for Google maps on Windows Phone and posted a video to prove it.

The video shows Google Maps working on a Lumia 800 (not the latest version of Windows Phone). I tried this URL:

ms-gl=au&ie=UTF8&t=m&source=embed&oe=UTF8&msa=0&msid=202255975001106586432.0004bb17c01b36a71a644

on my own Lumia 800 and it does indeed work. You can search for places, they show up on the map, and you can zoom with the + and – controls. However, it is not perfect. The search box is slightly corrupted and I am unable to pinch to zoom or swipe to pan. Better than nothing? Certainly.

Still, the experience is sufficiently degraded to lend some credence to Google’s statements; and there is undoubtedly extra work in supporting additional browsers as any web developer will confirm. 

Is Google at war with Windows Phone, or just not going out of its way to support a rival platform? Watch this space.