Category Archives: microsoft

Windows Phone puzzles: strategy, what strategy?

Today Microsoft CEO Satya Nadella announced that 7,800 employees will be removed “primarily in our phone business” and that the company is taking a $7.6 billion “impairment charge … related to assets associated with the acquisition of the Nokia Devices and Services business.”

Time for a quick resume of the company’s troubled mobile efforts since the introduction of Windows Phone in October 2010:

October 2010: botched launch of Windows Phone. Despite much good work in the OS and user interface, Microsoft had lacklustre support from hardware partners, and focused on the consumer when its potential strength was in business integration with Office, Exchange etc. In addition, availability was poor; after the UK launch I went down to my local town centre and not one of the 4 or 5 mobile phone shops had it on sale.

February 2011: Nokia announces that Windows Phone will be its primary smartphone OS.

October 2011: First Nokia Windows Phones appeared. Lumia 800 was a nicely designed phone in some respects, but suffered from poor battery life and some quality issues.

Nevertheless, the Nokia Windows Phones were the first ones where the manufacturer made an effort to get the best from the OS and to tailor the hardware for it. In addition, Nokia brought excellent mapping and photography expertise, so that Windows Phones began to get some standout features.

11 July 2013: Launch of Nokia Lumia 1020 with an amazing 41MP camera.

September 2013: Microsoft announces that it will acquire Nokia.

An awkward period follows before the acquisition completes. It is meant to be business as usual at Nokia but of course it is not.

February 2014: Despite some progress, Windows Phone is not getting the market share Nokia needs, so CEO Stephen Elop announces the Nokia X range, Android smartphones with Google removed and replaced by Microsoft services. A curious announcement, since why would anyone buy Nokia X? It was not because Android works better than Windows Phone on low-end hardware; vendors have told me that the reverse is true. Nor does it make sense bearing in mind the Microsoft acquisition – though it will have been in the planning stage before that was decided.

April 2014: Microsoft’s Nokia acquisition completes. Elop joins Microsoft to head up devices. As soon as July, it is obvious that Microsoft will not be continuing with Nokia X.

September 2014: Microsoft announces Windows 10. “we are delivering one application platform for our developers … Windows 10 will deliver the right experience on the right device at the right time. It will be our most comprehensive platform ever,” says Windows VP Terry Myerson.

The new universal app platform is all very well, but it means that Windows Phone is now in stasis, waiting for Windows 10 before anything much can happen to it. There is a notable lack of new high-end phones. No phone since the Lumia 1020 has had a camera of equal resolution.

At the same time, part of the point of Windows 10 is to revive the application platform across phone and PC. If you remove the phone, the Universal Windows Platform is what, PC, Xbox (mainly a games console) and HoloLens? With a few Raspberry Pis and IoT devices thrown in?

17 June 2015: Elop leaves Microsoft following an executive re-shuffle.

8 July 2015: Suspicions that Microsoft is wavering in its commitment to Windows Phone (or Windows 10 Mobile) are confirmed by the announcement of major cuts to the phone business.

A few observations

Microsoft has given Nokia little chance of success following the acquisition. It is not quite a repeat of the Kin disaster (acquisition of Danger in February 2008, a strong company wrecked by its acquirers), but there are echoes. It is only a year and three months since the acquisition completed, and the phone range is in an uncomfortable “waiting for Windows 10” phase. What did the company expect, that a Microsoft halo effect would suddenly lift sales, even without distinctive new models?

Nokia did a much better job with Windows Phone than either Microsoft or its other hardware partners. Nokia’s retail presence, operator partnerships, and marketing, were all far superior.

The main reason for the failure of Windows Phone is the lack of apps and ecosystem, and the reason for that is that Microsoft was too late to launch; iOS and, more to the point, Android, were already well entrenched. The Windows Phone OS is pretty good, and superior to the competition in some respects; apps are easier to find, for example.

Another problem is that Windows Phone has been more successful in Europe than in the USA. This means that US-centric vendors perceive that Windows Phone has an even smaller market than in fact it has.

Bearing in mind that the app story is the biggest single problem for Windows Phone vendors, and that Windows 10 is intended to address that, it is puzzling that Microsoft is now writing off the phone division before Windows 10 has launched.

Nadella writes:

I am committed to our first-party devices including phones. However, we need to focus our phone efforts in the near term while driving reinvention. We are moving from a strategy to grow a standalone phone business to a strategy to grow and create a vibrant Windows ecosystem that includes our first-party device family.

The problem is that frail market confidence in Windows Phone will be further shaken by today’s announcement. Further, if Nadella thinks that Microsoft’s trusty hardware partners will step up their game if Lumia is given less investment, than he has forgotten their dismal performance first time around.

Does Microsoft need Windows Phone?

Microsoft has been investing in Android and iOS apps since Nadella’s appointment, and it may not have a choice about whether or not it needs a mobile OS, if it cannot find a market for it.

There some strategic issues though. Microsoft itself succeeded first with Windows on the desktop, and exploited its desktop presence to drive server products that integrated with Windows and shared its user interface and operating system.

Mobile operating systems are now ascendant, and if Microsoft has little or no presence in that market, it is vulnerable to its competitors exploiting their control of the client to drive users to their own services, rather than those run by Microsoft.

Therefore it seems to me that ceding the mobile market to Apple and Google is a strategic risk.

How to overcome “A required drive partition is missing” in Windows 8.1 reset

Here is the scenario: an HP all-in-one PC gets a virus and as a precaution the owner wishes to reinstall Windows.

The recovery drive on the PC is intact, but attempting to use the Windows 8.1 troubleshooting tools to “Reset your PC” (in effect reinstalling Windows) raises the error “A required drive partition is missing”.

This seems to be a common scenario in cases where the PC was supplied with Windows 8 and upgraded to Windows 8.1. The problem seems to be that Windows 8.1 makes some changes to the drive partitions that make it incompatible with the Windows 8.0 recovery partition.

Here is the workaround I used:

1. In Windows 8.1, make a recovery drive. To do this, first connect a USB drive that you are happy to have wiped. It will need a capacity of around 16GB or more. Then run Control Panel, search for “recovery”, and choose Create a recovery drive.

image

2. When creating the recovery drive, make sure the option to include the recovery partition is checked. This will copy the recovery partition from the PC to the USB drive.

3. When you are done, you will be able to boot from the USB drive. You could choose the Reset option from there, however you will still get the error. First, go to Troubleshooting and Advanced and select the command prompt. When the command prompt opens, type:

diskpart

Now type:

list disk

You will see two disks (or more) listed, one for the USB boot device, and the others the disk(s) in the PC. Select the internal boot drive. It is normally obvious from the sizes which is which. Select it by typing:

select disk n

where n is the number of the drive as shown by list disk.

WARNING: the next step will delete all data on the selected drive. If in doubt, back out and make a backup of the drive before proceeding. If something goes wrong, your PC will no longer be bootable and you will need recovery media from the manufacturer, or to buy a new copy of Windows.

Once you are happy that it is safe to delete everything from the drive, type:

clean

or

clean all

The first command does a quick removal of the partition table from the drive but does not zero the data; it will be invisible but possibly recoverable using data recovery tools. The second command zeroes all the data and takes much longer (several hours), but it is more secure, if for example you want to sell or transfer the PC.

Once this is done,reboot the PC using the USB recovery drive. Select troubleshooting, then Reset your PC. This time it will work and you will be back in Windows 8.0.

Note: This scenario is common enough that it seems to be a flaw in the Windows 8.x recovery tools. I do not understand why Microsoft has so little regard for its users attempting to recover Windows (and usually highly stressed) that it has not fixed this problem.

Note 2: What if you cannot boot into Windows 8.1 to make the recovery drive? I have not tried it, but in theory it should be possible to create a recovery drive on another PC and copy the recovery drive to it.

Installing Windows 10 on Surface 3 with Windows To Go

I am working on a review of Surface 3, Microsoft’s recently released Atom-based tablet, and wanted to try Windows 10 on the device. How to do this though without endangering the correct functioning of my loan unit?

The ideal answer seemed to be Windows To Go (WTG), which les you run Windows from a USB drive without touching what is already installed – well, apart from a setting in control panel that enables boot from Windows to Go.

image

Luckily I have an approved Windows to Go USB drive, a 32GB Kingston DataTraveler Workspace. I downloaded the Windows 10 iso (64-bit, build 10074) and used the Control Panel applet on my Windows 8 desktop (which runs the Enterprise edition) to create a WTG installation.

(There are unofficial ways to get around both the requirement for Enterprise edition, and the need for an approved USB device, but I did not have to go there).

Next, I plugged the drive into the Surface 3 and restarted. Windows 10 came up immediately. An interesting feature was that I was prompted to sign into Office 365, rather than with a Microsoft account. It all seemed to work, though Device Manager showed many missing drivers.

image

The wifi driver must have been one of them, since I had no network.

I had anticipated this problem by downloaded the surface 3 drivers from here. These were inaccessible though, since a WTG installation by default has no access to the hard drive on the host PC. I could not plug in a second USB device with the drivers on it either, since there is only one USB port on the Surface 3.

No matter, you can mount the local drives using the Windows Disk Management utility. I did that, and ran the Surface 3 Platform Installer which I had downloaded earlier. It seemed to install lots of drivers, and I was then prompted to restart.

Bad news. When trying to restart, boot failed with an “inaccessible boot device” error.

Fool that I am, I tried this operation again with a small variation. I rebuilt the WTG drive, and instead of mounting the drives on the host, I used it first on another PC, where the wifi worked straight away. I copied the Surface 3 files to the WTG drive C, then booted it on the Surface 3. Ran the Surface 3 Platform Installer, restarted, same problem “Inaccessible boot device”.

The third time, I did not run the Surface 3 Platform Installer. Instead, I installed the drivers one by one by right-clicking on the Unknown Devices in Device Manager and navigating to the Surface 3 drivers files I had downloaded using another PC. That looks better.

image

I restarted, and everything still worked. I have wifi, Bluetooth, audio, cameras and everything. So something the Platform Installer tries to do breaks WTG on my device.

The next question is whether the system will update OK when set to Fast for the Windows 10 bleeding edge. So far though, so good.

Note: there is an issue with power management. If the Surface 3 sleeps, then it seems to wake up back in Windows 8 if you leave it long enough. Not too much harm done though; restart and you are back in Windows 10.

Note 2: new builds will not install on WTG, they complain about an unsupported UEFI layout

Running ASP.NET 5.0 on Nano Server preview

I have been trying out Microsoft’s Nano Server Preview and wrote up initial experiences for the Register. One of the things I mentioned is that I could not get an ASP.NET app successfully deployed. After a bit more effort, and help from a member of the team, I am glad to say that I have been successful.

image

What was the problem? First, a bit of background. Nano Server does not run the .NET Framework, presumably because it has too many dependencies on pieces of Windows which Microsoft wanted to omit from this cut-down deployment. Nano Server does support .NET Core, also known as Core CLR, which is the open source fork of the .NET Framework. This enables it to run PowerShell, although with a limited range of cmdlets, and my main two ways of interacting with Nano Server are with PowerShell remoting, and Windows file sharing for copying files across.

On your development machine, you need several pieces in order to code for ASP.NET 5.0. Just installing Visual Studio 2015 RC will do, except that there is currently an incompatibility between the version of the ASP.NET 5.0 .NET Core runtime shipped with Visual Studio, and what works on Nano Server. This meant that my first effort, which was to build an empty ASP.NET 5.0 template app and publish it to the file system, failed on Nano Server with a NativeCommandError.

This meant I had to dig a bit more deeply into ASP.NET 5.0 running on .NET Core. Note that when you deploy one of these apps, you can include all the dependencies in the app directory. In other words, apps are self-hosting. The binary that enables this bit of magic is called DNX (.NET Execution Environment); it was formerly known as the K runtime.

Developers need to install the DNX SDK on their machines (Windows, Mac or Linux). There is currently a getting started guide here, though note that many of the topics in this promising documentation are as yet unwritten.

image

However, after installation you will be able to use several handy commands:

dnvm This is the .NET Version manager. You can have several versions of the DNX runtime installed and this utility lets you list them, set aliases to save typing full paths, and manage defaults.

image

dnu This is the .NET Development Utility (formerly kpm) that builds and publishes .NET Core projects. The two commands I found myself using regularly are dnu restore which downloads Nuget (.NET repository) packages and dnu publish which packages an app for deployment. Once published, you will find .cmd files in the output which you use to start the app.

dnx This is the binary which you call to run an app. On the development machine, you can use dnx . run to run the console app in the current directory and dnx . web to run the web app in the current directory.

Now, back to my deployment issues. The Visual Studio templates are all hooked to DNX beta 4, and I was informed that I needed DNX beta 5 for Nano Server. I played around with trying to get Visual Studio to target the updated DNX but ran into problems so decided to ignore Visual Studio and do everything from the command line. This should mean that it would all work on Mac and Linux as well.

I had a bit of trouble persuading DNX to update itself to the latest unstable builds; the main issue I recall is targeting the correct repository. You NuGet sources must include (currently) https://www.myget.org/F/aspnetvnext/api/v2.

Since I was not using Visual Studio, I based my samples on these, Hello World Console, MVC and Web apps that you can use for testing that everything works. My technique was to test on the development machine using dnx . web, then to use dnu publish and copy the output to Nano Server where I could run ./web.cmd in a remote PowerShell session.

Note that I found it necessary to specify the CoreClr 64-bit runtime in order to get dnu to publish the correct files. I tried to make this the default but for some reason* it reverted itself to x86:

dnu publish –runtime "c:\users\[USERNAME]\.dnx\runtime\dnx-coreclr-win-x64.1.0.0-beta5-11701"

Of course the exact runtime version to use will change soon.

If you run this command and look in the /bin/output folder you will find web.cmd, and running this should start the app. The port on which the app listens is set in project.json in the top level directory of the project source. I set this to 5001, opened that port in the Windows Firewall on the Nano Server, and got a started message on the command line. However I still could not browse to the app running on Nano Server; I got a 400 error. Even on the development machine it did not work; the browser just timed out.

It turned out that there were several issues here. On the development machine, which is running Windows 10 build 10074, I discovered to my annoyance that the web app worked fine with Internet Explorer, but not in Project Spartan, sorry Edge. I do not know why.

Support also gave me some tips to get this working on Nano Server. In order for the app to work across the network, you have to edit project.json so that localhost is replaced either with the IP number of the server, or with a *. I was also advised to add dnx.exe to the allowed apps in the firewall, but I do not think this is necessary if the port is open (it is a nuisance, since the location of dnx.exe changes for every app).

Finally I was successful.

Final observations

It seems to me that ASP.NET vNext running on .NET Core has the characteristic of many open source projects, a few dedicated people who have little time for documentation and are so close to the project that their public communications assume a fair amount of pre-knowledge. The site I referenced above does have helpful documentation though, for the few topics that are complete. Some other posts I found helpful are this series by Steve Perkins, and the troubleshooting suggestions here especially David Fowler’s post.

I like The .NET Core initiative overall since I like C# and ASP.NET MVC and now it is becoming a true cross-platform framework. That said, the code does seem to be in rapid flux and I doubt it will really be ready when Visual Studio 2015 ships. The danger I suppose is that developers will try it in the first release, find lots of problems, and never go back.

I also like the idea of running apps in Nano Server, a low-maintenance environment where you can get the isolation of a dedicated server for your app at low cost in terms of resources.

No doubt though, the lack of pieces that you expect to find on Windows Server will be an issue and I am not sure that the mainstream Microsoft developer ecosystem will take to it. Aidan Finn is not convinced, for example:

Am I really expected to deploy a headless OS onto hardware where the HCL certification has the value of a bucket with a hole in it? If I was to deploy Nano, even in cloud-scale installations, then I would need a super-HCL that stress tests all of the hardware enhancements. And I would want ALL of those hardware offloads turned OFF by default so that I can verify functionality for myself, because clearly, neither Microsoft’s HCL testers nor the OEMs are capable of even the most basic test right now.

Finn’s point is that if your headless server is having networking issues it is hard to troubleshoot, since of course remote tools will not work reliably. That said, I have personally run Hyper-V Server (which is essentially Server Core with just the Hyper-V role) with great success for several years; I started keeping notes on how to troubleshoot from the command line and found solutions to common problems. If networking fails with Nano Server then yes, you have a problem, but there is always something you can do, even if it means mounting the Nano Server VHD or VHDX on another VM. Windows Server admins have become accustomed to a local GUI though and adjusting even to Server Core has not been easy.

*the reason was that I did not use the –p argument with dnvm use which would have made it persistent

Windows 10: Moving Windows into the mobile and app era take 2, and why Windows 8 is not so bad

I attended Microsoft’s Build conference last week where there was a big focus on Windows 10. I spent some time with the latest Build 10074 which came out last week as well attending various sessions on developing for the upcoming OS. I also spoke to Corporate VP Joe Belfiore and I recommend this interview on the Reg which says a lot about Microsoft’s approach. Note that the company is determined to appeal to Windows 7 users who largely rejected Windows 8; Windows 10 is meant to feel more familiar to them.

image

That said, Microsoft is not backtracking on the core new feature in Windows 8, which is its new app platform, called the Windows Runtime (WinRT). In fact, in its latest guise as the Universal App Platform (UAP) it is more than ever at the forefront of Microsoft’s marketing effort.

Why is this? In essence, Microsoft needs a strong app ecosystem for Windows if it is to escape legacy status. That means apps which are store-delivered, run in a secure sandbox, install and uninstall easily, update automatically, and work on tablets as well as with keyboard and mouse. Interaction and data transfer between apps is managed through OS-controlled channels, called Contracts. Another advantage is that you do not need setup CDs or downloads when you get a new PC; your apps flow down automatically. When you think of it like this, the advantages are huge; but nevertheless the Windows 8 app platform largely failed. It is easy to enumerate some of the reasons:

  • Most users live in the Windows desktop and rarely transition to the “Metro” or “Modern” environment
  • Lack of Windows 7 compatibility makes the Windows 8 app platform unattractive to developers who want to target the majority of Windows users
  • Many users simply avoided upgrading to Windows 8, especially in business environments where they have more choice, reducing the size of the Windows 8 app market
  • Microsoft made a number of mistakes in its Windows 8 launch, including an uncompromising approach that put off new users (who felt, rightly, that “Metro” was forced upon them), lack of compelling first-party apps, and encouraging a flood of abysmal apps into the Store by prioritising quantity over quality

History will judge Windows 8 harshly, but I have some admiration for what Microsoft achieved. It is in my experience the most stable and best performing version of Windows, and despite what detractors tell you it works fine with keyboard and mouse. You have to learn a new way of doing a few things, such as finding apps in the Start screen, following which it works well.

The designers of Windows 8 took the view that the desktop and app environments should be separate. This has the advantage that apps appear in the environment they are designed for. Modern apps open up full-screen, desktop apps in a window (unless they are games that are designed to run full-screen). The disadvantage is that integration between the two environments is poor, and you lose one of the key benefits of Windows (from which it got its name), the ability to run multiple apps in resizable and overlapping windows.

Windows 10 takes the opposite approach. Modern apps run in a window just like desktop apps. The user might not realise that they are modern apps at all; they simply get the benefits of store delivery, isolation and so on, without having to think about it.

image

This sounds good and following the failure of the first approach, it is probably the right thing for Microsoft to do. However there are a couple of problems. One is the risk of what has been called the “uncanny valley” in an app context, where apps nearly but not quite work in the way you expect, leading to a feeling of unease or confusion. Modern apps look a little bit different from true desktop apps in Windows 10, and behave a little bit different as well. Modern apps have a different lifecycle, for example, can enter a suspended state when they do not have the focus or even be terminated by the OS if the memory is needed. A minimized desktop app keeps running, but a minimized modern app is suspended, and the developer has to take special steps if you want a task to keep running in the background.

Another issue with Windows 10 is that its attempt to recreate a Windows 8 like tablet experience is currently rather odd. Windows 10 “Tablet Mode” makes all apps run full screen, even desktop apps for which this is wholly inappropriate. Here is the Snipping Tool in Tablet Mode:

image

and here is the desktop Remote Desktop Connection:

image

Personally I find that Tablet Mode trips me up and adds little value, even when I am using a tablet without a keyboard, so I tend not to use it at all. I would prefer the Windows 8 behaviour, where Modern apps run full screen (or in a split view), but desktop apps open in a window on the desktop. Still, it illustrates the point, which is that integrating the modern and desktop environments has a downside; it is just a different set of compromises than those made for Windows 8.

Now, I do think that Microsoft is putting a more wholehearted effort into its UAP than it did for Windows 8 modern apps (even though both run on WinRT). This time around, the Store is better, the first-party apps are better (not least because we have Office), and the merging of the Windows Phone and Xbox platforms with the PC platform gives developers more incentive to come up with apps. Windows 10 is also a free upgrade for many users which must help with adoption. Even with all this, though, Microsoft has an uphill task creating a strong modern app ecosystem for Windows, and a lot of developers will take a wait and see approach.

The other huge question is how well users will take to Windows 10. Any OS upgrade has a problem to contend with, which is that users dislike change – perhaps especially what has become the Windows demographic, with business users who are by nature cautious, and many conservative consumer users. Users are contradictory of course; they dislike change, but they like things to be made better. It will take more than a Cortana demo to persuade a contented Windows 7 user that Windows 10 is something for them.

Note that I say that in full knowledge of how much potential the modern app model has to improve the Windows experience – see my third paragraph above.

Microsoft told me in San Francisco that things including Tablet Mode are still being worked on so a little time remains. It was clear at Build that there is a lot of energy and determination behind Windows 10 and the UAP so there is still room for optimism, even though it is also obvious that Windows 10 has to improve substantially on the current preview to have a chance of meeting the company’s goals.

HoloLens: a developer hands-on

I attended the “Holographic Academy” during Microsoft’s Build conference in San Francisco. It was aimed at developers, and we got a hands-on experience of coding a simple HoloLens app and viewing the results. We were forbidden from taking pictures so you will have to make do with my words; this also means I do not have to show myself wearing a bulky headset and staring at things you cannot see.

image

First, a word about HoloLens itself. The gadget is a headset that augments the real world with a 3D “projected” image. It is not really a hologram, otherwise everyone would see it, but it is a virtual hologram created by combining what you see with digital images.

The effect is uncanny, since the image you see appears to stay in one place. You can walk around it, seeing it from different angles, close up or far away, just as you could with a real image.

That said, there were a couple of issues with the experience. One is that if you went too close to a projected image, it disappeared. From memory, the minimum distance was about 18 inches. Second, the viewport where you see the augmented reality was fairly small and you could easily see around it. This is detrimental to the illusion, and sometimes made it a struggle to see as much of your hologram as you might want.

I asked about both issues and got the same response, essentially “no comment’’. This is prototype hardware, so anything could change. However, according to another journalist who attended a hands-on demo in January, the viewport has gotten smaller, suggesting that Microsoft is compromising in its effort to make the technology into a commercially viable product.

Another odd thing about the demo was that after every step, we were encouraged to whoop and cheer. There was a Microsoft “mentor” for every pair of journalists, and it seemed to me that the mentors were doing most of the whooping and cheering. It is obvious that this is a big investment for the company and I am guessing that this kind of forced enthusiasm is an effort to ensure a positive iimpression.

Lest you think I am too sceptical, let me add that the technology is genuinely amazing, with obvious potential both for gaming and business use.

The developer story

The development process involves Unity, Visual Studio, and of course the HoloLens device itself. The workflow is like this. You create an interactive 3D scene in Unity and build it, whereupon it becomes a Visual Studio project. You open the project in Visual Studio, and deploy it to HoloLens (connected over USB), just as you would to a smartphone. Once deployed, you disconnect the HoloLens and wear it in order to experience the scene you have created. Unity supports scripting in C#, running on Mono, which makes the development platform easy and familiar for Windows developers.

Our first “Holo World” project displayed a hologram at a fixed position determined by where you are when the app first runs. Next, we added the ability to move the hologram, selecting it with a wagging finger gesture, shifting our gaze to some other spot, and placing it with another wagging finger gesture. Note that for this to work, HoloLens needs to map the real world, and we tried turning on wire framing so you could see the triangles which show where HoloLens is detecting objects.

We also added a selection cursor, an image that looks like a red bagel (you can design your own cursor and import it into Unity). Other embellishments were the ability to select a sphere and make it fall to the floor and roll around, voice control to drop a sphere and then reset it back to the starting point, and then “spatial audio” that appears to emit from the hologram.

All of this was accomplished with a few lines of C# imported as scripts into Unity. The development was all guided so we did not have to think for ourselves, though I did add a custom voice command so I could say “abracadabra” instead of “reset scene”; this worked perfectly first time.

For the last experiment, we added a virtual underworld. When the sphere dropped, it exploded making a virtual pit in the floor, through which you could see a virtual world with red birds flapping around. It was also possible to enter this world, by positioning the hologram above your head and dropping a sphere from there.

HoloLens has three core inputs: gaze (where you are looking), gesture (like the finger wag) and voice. Of these, gaze and voice worked really well in our hands on, but gesture was more difficult and sometimes took several tries to get right.

At the end of the session, I had no doubt about the value of the technology. The development process looks easily accessible to developers who have the right 3D design skills, and Unity seems ideally suited for the project.

The main doubts are about how close HoloLens is to being a viable commercial product, at least in the mass market. The headset is bulky, the viewport too small, and there were some other little issues like lag between the HoloLens detection of physical objects and their actual position, if they were moving, as with a person walking around.

Watch this space though; it is going to be most interesting.

Compile Android Java, iOS Objective C apps for Windows 10 with Visual Studio: a game changer?

Microsoft has announced the ability to compile Windows 10 apps written in Java or C++ for Android, or in Objective C for iOS, at its Build developer conference here in San Francisco.

image
Objective C code in Visual Studio

The Android compatibility had been widely rumoured, but the Objective C support not so much.

This is big news, but oddly the Build attendees were more excited by the HoloLens section of the keynote (3D virtual reality) than by the iOS/Android compatibility. That is partly because this is the wrong crown; these are the Windows faithful who would rather code in C#.

Another factor is that those who want Microsoft’s platform to succeed will have mixed feelings. Is the company now removing any incentive to code dedicated Windows apps that will make the most of the platform?

Details of the new capabilities are scant though we will no doubt get more details as the event progresses. A few observations though.

Microsoft is trying to fix the “app gap”, the fact that both Windows Store and Windows Phone Store (which are merging) have a poor selection of apps compared to iOS or Android. Worse, many simply ignore the platforms as too small to bother with. Lack of apps make the platforms less attractive so the situation does not improve.

The goal then is to make it easier for developers to port their code, and also perhaps to raise the quality of Windows mobile apps by enabling code sharing with the more important platforms.

There are apparently ways to add Windows-specific features if you want your ported app to work properly with the platform.

Will it work? The Amazon Fire and the Blackberry 10 precedents are not encouraging. Both platforms make it easy to port Android apps (Amazon Fire is actually a version of Android), yet the apps available in the respective app stores are still far short of what you can get for Google Android.

The reasons are various, but I would guess part of the problem is that ease of porting code does not make an unimportant platform important. Another factor is that supporting an additional platform never comes for free; there is admin and support to consider.

The strategy could help though, if Microsoft through other means makes the platform an attractive target. The primary way to do this of course is to have lots of users. VP Terry Myerson told us that Microsoft is aiming for 1 billion devices running Windows 10 within 2-3 years. If it gets there, the platform will form a strong app market and that in turn will attract developers, some of whom will be glad to be able to port their existing code.

The announcement though is not transformative on its own. Microsoft still has to drive lots of Windows 10 upgrades and sell more phones.

Visual Studio Code: an official Microsoft IDE for Mac, Windows, Linux

Microsoft has announced Visual Studio Code, a cross-platform, code-oriented IDE for Windows, Mac and Linux, at its Build developer conference here in San Francisco.

image

Visual Studio Code is partly based on the open source projects Omnisharp. It supports Intellisense code completion, GIT source code management, and debugging with break points and call stack.

I have been in San Francisco for the last few days and the dominance of the Mac is obvious. Sitting in a cafe in the Mission district I could see 10 Macs and no PCs other than my own Surface Pro. Some folk were coding too.

It follows that if Microsoft wants to make a go of cross-platform C#, and development of ASP.NET MVC web applications beyond the Windows developer community, then tooling for the Mac is important.

image

Visual Studio Code is free and is available for download here.

The IDE will lack the rich features and templates of the full Visual Studio, but if it is fast and clean, some Visual Studio developers may be keen to give it a try as well.

Microsoft financials Jan-March 2015

Microsoft has released figures for its third quarter, ending March 31st 2015. Here is my simple summary of the figures showing the segment breakdown:

Quarter ending  March 31st 2015 vs quarter ending March 31st 2014, $millions

Segment Revenue Change Gross margin Change
Devices and Consumer Licensing 3476 -1121 3210 -807
Computing and Gaming Hardware 1800 -72 414 +156
Phone Hardware 1397 N/A -4 N/A
Devices and Consumer Other 2280 +456 566 +175
Commercial Licensing 10036 -299 9975 -157
Commercial Other 2760 +858 1144 +669

The figures form a familiar pattern: Windows and shrink-wrap (non-subscription) Office is down, reflecting weak PC sales and the advent of free Windows at the low end, but subscription sales are up and cloud is booming. See the foot of this post for an explanation of Microsoft’s confusing segment breakdown.

Microsoft says that Surface Pro 3 is doing well (revenue of $713 million) and this is reflected in the Devices figures. Commercial cloud (Office 365, Azure and Dynamics) is up 106% year on year.

Cloud aside, it is impressive that server products reported a 12% year on year increase in revenue. This is the kind of business that you would expect to be hit by cloud migration, though I am not sure how Microsoft accounts for things like SQL Server licenses deployed on Azure.

Xbox One is disappointing, bearing in mind the success of the Xbox 360. Microsoft managed to lose out to Sony’s PlayStation 4 with its botched launch and market share will be hard to claw back.

Microsoft reports 8.6 million Lumias sold, the majority being low-end devices. Not too bad for a platform many dismiss, but still treading water and miles behind iOS and Android.

The company remains a huge money-making machine though, and Office 365 is doing well. A few years ago it looked as if cloud and mobile could destroy Microsoft, but so far that is not the case at all, though its business is changing.

Microsoft’s segments summarised

Devices and Consumer Licensing: non-volume and non-subscription licensing of Windows, Office, Windows Phone, and “ related patent licensing; and certain other patent licensing revenue” – all those Android royalties?

Computing and Gaming Hardware: the Xbox One and 360, Xbox Live subscriptions, Surface, and Microsoft PC accessories.

Devices and Consumer Other: Resale, including Windows Store, Xbox Live transactions (other than subscriptions), Windows Phone Marketplace; search advertising; display advertising; Office 365 Home Premium subscriptions; Microsoft Studios (games), retail stores.

Commercial Licensing: server products, including Windows Server, Microsoft SQL Server, Visual Studio, System Center, and Windows Embedded; volume licensing of Windows, Office, Exchange, SharePoint, and Lync; Microsoft Dynamics business solutions, excluding Dynamics CRM Online; Skype.

Commercial Other: Enterprise Services, including support and consulting; Office 365 (excluding Office 365 Home Premium), other Microsoft Office online offerings, and Dynamics CRM Online; Windows Azure.

Inside Microsoft: Ex design lead gives perspective on Metro, Office, iOS and Android battles

Here is a must-read for Microsoft watchers. Two days ago a former design lead on the Office on Windows Phone team turned up on Reddit and said I designed the new version of Office for Windows Phone. Ask me anything.

image

The overall theme is that Microsoft did not get the design of Windows Phone quite right and is changing it; that Windows 8 was even worse; and that Windows 10 just might begin to pull it all together at last, though the company is also consciously moving away from a Windows-centric view. The Windows, Windows Phone and Office teams are now working together for the first time, we are told:

Windows didn’t believe in working well with others, certainly not that dumb upstart Windows Phone team.

Office believed it was the greatest software on earth, and didn’t get along with Windows.

Windows Phone was pretty proud of itself despite its middling marketshare. Too proud.

So now when these three teams got together to do something for the good of Microsoft, and the good of customers, there was a ton of ego in the way. Windows believed in the Windows way. Windows Phone believed their way. Office was like "fuck all y’all, we’re Office."

The new situation at the company is way better. People actually do care about working together in a way I hadn’t historically seen in my short time there. (or read about in many MS history books)

So I wouldn’t say Windows Phone caused the shift. You know what did? Sinofsky leaving, Windows 8 being a failure, Windows Phone failing to gain significant traction, and then Ballmer leaving.

They basically had to start working together. And it’s cool to see.

Here are a few more things that caught my eye. There are long discussions about the “hamburger” menu, three lines appearing at top left of many new apps where it is hard to reach if you are using the phone with one hand:

Don’t get me wrong, this is clearly a tradeoff. Frequently used things have to be reachable, even one-handed. But hamburgers are not frequently used, and one-handed use is not ironclad. Combine those two factors together and you see why the industry has settled on this standard. It wasn’t random.

From a developer perspective, the key insight here is that hamburgers are not frequently used. In other words, do not design your app so that users will have to reach constantly for the hamburger menu. Reserve it for stuff that is only needed occasionally.

Why is Microsoft appearing to prioritise iOS and Android over Windows, for example with Office?

When Ballmer saw the iPad version of Office, he reportedly said something like "you’re killing me." It was so fucking good. Way better than anything on any other platform. It leveraged a bunch of iOS stuff in a really good way, but it was still "unmistakably Office," as they say.

Ballmer knew it was good. And he knew the company’s other efforts were years and years out. And he iced it. Because his mentality, and what I’d call dogma, was that Windows had to be first. At all costs.

Good riddance. It was an outdated philosophy.

… The way Microsoft wins the long term war is to remind people where they’re strong. And no, it’s not through withholding Office on iOS. Not anymore. The ship sailed on Ballmer’s watch

I would love to know the date when Ballmer “iced” Office for iPad.

What was wrong with the design of Window Phone?

When Steve Jobs came back to Apple, he said he was going to save the company by reminding people of Apple’s sex appeal. He described colored plastics and technology as fashion. And the board thought "uh-oh, this guy is going to drive us into a ditch."

But from "Bondi Blue iMacs" and "OS X has an interface you just want to lick" you’ll notice their design went more and more subdued over the last 15-20 years. It’s because you need to shock people at first, then you get back to being more practical.

Metro had to shock people. It had to look like its own thing. And it did that really well. Pivots, panos, big text, black everywhere, it looked like art. And more than that it looked different. Something to witness. Steve Jobs even gave kudos to the Windows Phone design team! He said something like "I mean, it’s still clearly a v1, but it’s really beautiful." And he was right.

So what would I change?

Well. The interaction models, honestly. The pivots and the panoramas are a nightmare in day to day use. They’re as distinct as a Flower Power iMac, but it painted the interaction models into a corner.

In another post, there is a discussion of the difficulty with the back button. “when back is good, it’s good. But when it’s bad (from a user experience standpoint) it’s really bad.”

Here is another insight:

The stark look of Windows Phone seemed to turn off more people than fell in love with it. I know here in this forum we’re all fans but in the mainstream marketing was only one problem. Apps was another. But the biggest one was lack of relevance. People didn’t understand why they should care. A lot of people said it looked like a nice phone, but it wasn’t for them.

Despite the criticisms, the ex-Microsoft designer (who now works for Twitter) is optimistic, saying “I do have a lot of hope for Universal apps. It’s not a magic bullet, but given enough time for the system to mature, and the business support, and new initiatives, I see rosy days ahead.”

Microsoft may be well positioned for “the next big shift”:

Look beyond just Windows. Just make amazing software. Get back some relevance that was lost. 2) Of course keep competitive with hardware, and keep improving WP. 3) Then, a few years out, when the market experiences another big shift (it’s not a matter of if but when) I suspect MS’s strength as a multi-OS developer + cloud leader will help Windows regain a ton of relevance

Fascinating stuff, though note the disclaimer:

I have no idea what I’m talking about. I’m one designer and I don’t work at MS anymore.