Category Archives: mobile

CES analyst predicts flat global consumer tech sales, massive dominance of smartphones and tablets, drift towards low-end

At CES in Las Vegas yesterday, CEA Director of Industry Analysis Steve Koenig presented data and predictions on global tech spending trends. The figures come out of CEA Research and are based on sales tracking at retail outlets around the world supplemented by other data.

image

This being CES, I was expecting a certain amount of hype around how consumer technology is changing the world, but in fact Koenig’s presentation was matter-of-fact and somewhat downbeat. He said that the overall consumer tech spending trend is flat, with rising spend in emerging markets (especially China) more or less making up for declining spend in mature markets, which he says is due to market saturation. His figures show 2% growth in spending in 2013 but a 1% decline in 2014. Given the uncertainty of this kind of forecast, let’s call it flat.

The “market saturation” factor is a point to ponder. It suggests that technical devices are “good enough” for longer. It also suggests that overall the new gadgetry on show at CES is not sufficiently exciting to persuade us to spend a higher proportion of our income on consumer electronics.

Looking at his figures though, it is not just a matter of saturation. Another factor is device convergence. We are spending less on cameras and camcorders because a smartphone is good enough. We are spending less on printers because there is less need to print stuff; we can view it on a tablet. We don’t need a SatNav any more; we use a smartphone (or it is built into the car’s dashboard). In fact, we are loving our smartphones and tablets so much that spending on almost any other kind of tech is in decline. Here’s the slide showing how these mobile devices are forecast to account for 43% of consumer tech spending in 2014:

image

Spending on smartphones is forecast to increase by 9% in 2014, and on tablets 6%. Almost the only other broad category for which significant revenue growth is forecast in 2014 is video games consoles, thanks to the launch of new generation Xbox and PlayStation boxes (maybe Steam boxes too). That is a product cycle, not a long-term trend. Personally (my thoughts, not Koenig’s) I reckon games consoles will decline thanks to competition from smartphones, tablets and smart TVs. Global TV sales are expected to increase by 2% in units.

The other big picture trend identified by Koenig is the reduction in the average selling price (ASP) of smartphones and tablets. Smartphone ASP is down from $444 in 2010 to $297 in 2014.

image

This trend is partly because the quality of cheaper devices has improved, but also because the emerging markets which are spending more are also markets that want lower prices. Taken together, this translates to a significant shift towards the low end. Overall, CEA forecasts that tech spending in developing markets, primarily on low end devices, will equal tech spending in mature markets for the first time in 2014.

image

Of course this is largely an Android story. I will add though some reflections on what has happened with Windows in the light of these trends. Microsoft was right to adapt Windows for tablets, but if you look at how Windows 8 was launched there was too much focus on the high-end, trying to copy Apple rather than compete with Android. That was a mistake, and it is only recently that OEMs like Asus, with its T100 Windows 8.1 tablet, have started to come out with decent low-end devices. Nokia on the other hand has done exactly the right thing with its Lumia Windows Phones, building market share with excellent low-end smartphones. Whether that momentum will be sustained following Microsoft’s acquisition will determine the fate of the phone platform. 

Finally, note that forecasting the future is never easy and this time next year the picture may look quite different.

Update: Koenig’s slide deck is here.

Nine months with Truphone: a solution to mobile roaming?

At last year’s Mobile World Congress in Barcelona a UK company called Truphone gave out SIMs to journalists for review. The claim is that rates are better for travellers than using roaming rates on typical contracts. The company also offers extras including the ability to assign multiple international numbers to a single SIM.

It is not my only SIM, but I have been trying it out with reasonable results. The best thing about it from my point of view is that calls home from the USA are a reasonable £0.10 per minute, which means I don’t need Skype and a decent wifi connection in order to call without worrying too much about the cost.

image

Bizarrely, it is actually more expensive to call a UK number from within the UK, at £0.15 per minute, even though I have a UK number:

image

It is more expensive for both calls and data in Spain, at at £0.21 per minute for calls and at £0.36 per MB for data:

image

Data is a problem and I carelessly racked up a rather large bill in the US; £0.20 per MB does not sound too bad but a single MB does not go far with normal use.

Still, I can say in Truphone’s favour that signal quality is generally good and the rates better than most roaming deals. If you want to avoid the hassles of a local SIM in each country you visit Truphone is worth a look.

Microsoft Project Siena: another go at the spirit of Visual Basic

Remember Visual Basic? By which I mean, not the current language that is a case-insensitive alternative to C# that does much the same thing, but the original rapid app development tool that democratised Windows development back in 1991. At the time, Windows development was a sought-after skill but rather difficult. VB meant anyone could create an application; pros could build excellent ones, amateurs something ugly and unmaintainable, but nevertheless something that worked. The transition to .NET brought many benefits, but also more complexity. The latest evolution of the Windows client, the Windows Runtime, is also challenging to get right (I am currently writing a simple C# game on the platform).

Microsoft has been looking for a new “VB” for years. 2007: Popfly (now abandoned). 2011: Lightswitch. Now we have Project Siena.

image

Siena is an app for building apps. An app is a Siena document with a .siena extension. Here is what Microsoft’s Bryan Group says:

Microsoft Project Siena (code name) is the beta release of a new technology for business experts, business analysts, consultants, and other app imagineers. Now, without any programming, you can create powerful apps for the device-first and cloud-connected world, with the potential to transform today’s business processes.

Building Siena apps is as easy as editing a document. Place some visuals on a canvas. Hook them up to your data. Customize how your app looks and works. Then, if you need special logic and intelligence, write Excel-like expressions. You can use your app immediately, or share it with colleagues or the world.

This sounds great to me. I installed it and set about building an app. I decided to create the same app I have used to try out dozens of programming tools over the years: a to-do list with the ability to add and remove tasks

image

Building the user interface went OK, but how do I add and remove items from the list? I have got as far as figuring out that I need to type the right magic into the OnSelect property of a button:

image

I will let you know when I have worked out what to do next. I will observe that the environment is geared towards data binding, rather than directly updating the user interface, and remote data, such as binding to tables in Azure Mobile Services, a REST API, an RSS feed or a SharePoint list. However you can also bind to an Excel spreadsheet for local data.

Unfortunately there is no “Run” button. You can preview your Siena app by pressing F5 or tapping the Run button in the top app bar.

To deploy your Siena app, you hit Publish:

image 

This creates a package of files, including InstallApp.exe. Siena generates HTML and JavaScript so you can learn a lot about the environment by poking around in the generated files.

image

Run InstallApp.exe and the app installs into your local PC. Mine runs fine, it just does not work yet.

Siena, as is usual for this type of release, suffers from lack of documentation. There is a function reference and a few sketchy help topics. There are also some sample apps. Here is what the Personnel Manager has in the OnSelect of its Add button; perhaps this is a clue:

UpdateIf(Assoc,ID = ThisItem!ID,{AssignedTo:SelectedDepartment, Time:Now()}); RemoveIf(SelectedAssociates, ID = ThisItem!ID)

While it is great to have a genuinely easy visual interface builder, the development features of Visual Studio are greatly missed; the code editor as far as I can tell is limited to a single line in a text input field, though you do get a squiggly underline if you do it wrong, and a bit of code completion.

How is the average “business expert, business analyst, consultant, and other app imagineer” going to get on with Project Siena? That is the question; and in the current preview I’d guess they will be flummoxed and go straight back to Excel or Access, though I would love to be proved wrong.

It looks like a lot of work has gone into this though, and no doubt better documentation and enhanced features are on the way.

Making sense of Salesforce 1 (it’s all about mobile)

At its Dreamforce conference in San Francisco, Salesforce has been hyping up its newly announced Salesforce 1. The keynote left us in do doubt: it is fantastic, it does mobile, it does cloud, it does “internet of things”.

image

Co-founder Parker Harris describes Salesforce 1 at Dreamforce

But what is Salesforce 1? For those of us who like fluff-free facts, it has been difficult to discern. The APIs that make up the Salesforce 1 platform seemed on the face of it to be the same ones Salesforce has always had; yet the company says it has multiplied the number of APIs by 10 to create Salesforce 1 (a figure I still find hard to understand).

It is beginning to make sense to me. Salesforce 1 is a brand, a platform and an app.

As a brand, Salesforce 1 encompasses all the APIs that form the Salesforce platform. The best place to understand the current state of Salesforce 1 is here, where you can see links to all the APIs, including Force.com, Heroku, ExactTarget, Radian6 (social media listening), Pardot (sales automation), Desk.com (service cloud) and GoInstant (build real-time multi-user apps). Those individual APIs still exist in their own right, but Salesforce 1 is a new brand that encompasses all of them.

There is also a Salesforce 1 app for iOS and Android. This is mainly an HTML5 app, which makes it odd that it is iOS and Android only. As I understand it, you can also use a mobile browser and get a similar experience, so it might not be too bad for Windows Phone users after all.

The Salesforce 1 app is actually an evolution of the Chatter mobile app. As I understand it, it is built with the Aura framework, for creating a responsive user interface, with strong support for touch control. The Chatter app was renamed Salesforce 1 at the start of Dreamforce.

The Salesforce 1 app is built around a feed, and Salesforce describes it as a feed-first approach. Chatter has support for Publisher Actions, which now in Salesforce 1 have a more prominent role, making the feed capable of initiating tasks and being a mobile-friendly centre of operations. Some vendors I have spoken to, such as FinancialForce (wholly owned by Salesforce), see this feed-first approach as being the core of what Salesforce 1 is about. 

When Salesforce talks about creating Salesforce 1 apps, that might refer to either of two things.

One is to create custom apps for your Salesforce users, which you can do without needing much code in some cases, which will be viewed through the Salesforce 1 app.

The other is to use the Mobile SDK for iOS or Android to create a native app. This does not have to be an HTML5 app, but could be if you want the quickest route to something that works.

According to CEO Marc Benioff, speaking to the press, much of the effort behind Salesforce 1 was in making the Salesforce browser UI properly mobile-friendly. He said that this includes mobile client libraries as well as the server APIs. Salesforce has an rapid visual builder for browser apps running on its platform, called VisualForce, and apparently getting these apps working nicely on mobile took huge effort.

Benioff gave the impression that VisualForce now works perfectly on mobile, but the booklet given to developers expresses reservations:

Only VisualForce pages enabled for Salesforce Mobile Apps and attached to a tab can be added to the Salesforce 1 navigation menu. Note that you may have to optimize these pages to work and/or display correctly on a mobile device.

Nevertheless, you can see the intent here, that anything running on Salesforce will work well on a mobile device. Benioff says that he only takes a smartphone with him when travelling, no laptop or even tablet, and he expects to be able to do all his work through it.

You could therefore call Salesforce 1 the optimisation of the Salesforce platform for mobile, subject to the iOS/Android limitation.

According to Salesforce then, the new mobile-enabled platform is more productive than other app-building tools. The idea is that many corporate apps can be implemented to run in the existing Salesforce 1 app, which perhaps more correctly should be called a client, while apps that need to be deployed more broadly, such as to consumers, can be built using the Mobile SDK and deployed to the App Store or Google Play.

Developers of course are used to these kinds of claims and will be sceptical. Still, if you have adopted Salesforce to the extent that all your users are on the system, then it might make sense to build apps with Salesforce 1 and have a lot done for you, including user management and authentication.

There is talk at Dreamforce of the “app gap”, the fact that typical enterprises currently have most of their apps designed for the desktop, but are planning for most of their apps to be mobile. That gap is an opportunity for Salesforce 1.

Against that, note that apps built with Salesforce 1 are not portable to other platform, and there are the usual questions about the extent to which businesses are willing to entrust their business to a third-party cloud platform, and if so, which cloud platform is the best choice.

Is Salesforce 1 the same old stuff repackaged, or something new? It is a bit of each.

As an aside, the focus here on iOS and Android will not be helpful to Microsoft/Nokia trying to sell Windows Phone in the enterprise. You can also understand why Microsoft is partnering with Xamarin to enable its .NET, C# libraries to work on iOS/Android. If enterprises are going mobile and largely not using Windows Phone to do so, Microsoft has no choice but to give full support to those rival mobile platforms.

Salesforce 1 and the cloud platform wars

Salesforce has announced Salesforce 1, but what it is? Something new, or the same old stuff repackaged?

image

Even if it is something new, the ingredients are familiar. Salesforce 1, I have been told,  is a new brand over the Salesforce platform, though it does not replace individual components like Force.com or Heroku.

At heart, Salesforce is a multi-tenant cloud database and web services API, designed originally for CRM but easily adapted for other purposes, and easily extended by third-party partners with their own apps. If you review the components of Salesforce 1 you will find the same core platform and services as before.

If you want a quick overview of what makes up Salesforce 1, I recommend this list of platform services, including quick app development using browser-based tools, Heroku for code-centric development using Ruby, Java, Node.js or Python, web site development with site.com, a mobile SDK for iOS, Android or HTML5,  role-based user access management, private app portal, translation services, custom databases, social and collaboration services, reporting and analytics.

There is a new Salesforce 1 mobile app announced which you can customize. It only runs on iOS or Android; no support for Windows Phone.   

The Salesforce 1 proposition is that user identities are managed in the Salesforce database and that you build your cloud applications around them. Therefore the minimal Salesforce 1 product is One Enterprise App, at $25 per user/month, which gives you identity services (and a few others) and the app platform.

I would imagine that most Salesforce 1 customers will also use other Salesforce 1 products such as CRM or the Service Cloud. CRM, for example, runs from $5.00 per user/month for contact management to $300 per user/month for the Performance Edition, including the Service Cloud, workflow approval and unlimited custom apps. There is feature overlap between the various Salesforce products which may explain why the company encourages you to ask for a custom quote.

My immediate reflection on the Salesforce 1 announcement is that it is a cloud platform play. If you agree that the future of business IT is in cloud and mobile, then it follows that the future competitive landscape will be largely formed around the companies that offer cloud platforms. Large scale tends to win in the cloud, so for better or worse only a few companies will be able to compete effectively. Hence the cloud platform wars.

In this context, Amazon is strong on the app platform and cloud infrastructure side, but does not offer a complete enterprise platform, though recent announcements seem to me a move in that direction.

Google has immense scale and Android, but its strong focus on advertising and consumers perhaps hold back its enterprise offerings. If you run Android you are already hooked into Google’s identity platform.

Microsoft, perhaps oddly given its vast desktop legacy, seems to me a close competitor to Salesforce. Where Salesforce has CRM, Microsoft has Office 365, and where Salesforce has its own identity platform, Microsoft has Azure Active Directory. Apps for Office hook into SharePoint and Azure Active Directory in the same way Salesforce 1 apps hook into the Salesforce platform. There is no love between Salesforce and Microsoft, and constant sniping from Microsoft’s Dynamics CRM team. At the same time, there must be many businesses attracted to Office 365 for email and Office, and to Salesforce for CRM, which may lead to some difficult choices down the road. No wonder Salesforce is ignoring Windows Phone.

Microsoft Surface 2: still a hard sell at retail

I am a fan of Microsoft’s Surface 2; but looking at the display at Dixons in Heathrow’s Terminal 3 it is obvious that Microsoft has work to do in terms of retail presence.

There are no clues here as to why anyone might want to buy a Surface, and no indication that Surface 2 runs anything other than standard Windows 8, other than the two letters RT which you can read on the spec summary.

Windows RT is both better and worse than Windows on Intel. It is worse because you cannot install new desktop applications, but it is better because it is locked down and less likely to suffer from viruses or annoying OEM add-ons and customisations that usually result in a worse user experience.

Why did Microsoft not come up with a distinctive brand name for RT, such as AppWindows or StoreWindows or WinBook? I am open to negotiation should Microsoft wish to use one of my brand ideas 🙂

Surface 2 has excellent performance, Microsoft Office is bundled including Outlook (though without the ability to run Visual Basic macros), and it is expandable using Micro SD cards or USB 3.0 devices, all features I miss when using an Apple iPad.

I do use the desktop a lot on Surface 2. Simple applications like Paint and Notepad are useful especially since they have, you know, cool resizable and overlapping windows so you can have multiple applications on view.

The Apple iPad is better displayed and I am sure its greater prominence is more than justified by relative sales.

 

As BlackBerry stumbles, there are now three mobile platforms that matter

Today has been tumultuous for BlackBerry. Investment company Fairfax Financial, BlackBerry’s biggest shareholder, was intending to buy the company for US $4.7bn, but that deal fell through, apparently because of failure to attract other investors to what seemed a risky endeavour. Instead, Fairfax and other investors will invest US $1bn of new money into BlackBerry. CEO Thorsten Heins is to step down, and John S Chen, formerly CEO of Sybase, will take on the CEO role. Here is what Chen says:

BlackBerry is an iconic brand with enormous potential – but it’s going to take time, discipline and tough decisions to reclaim our success.  I look forward to leading BlackBerry in its turnaround and business model transformation for the benefit of all of its constituencies, including its customers, shareholders and employees.

Note the key phrase here: business model transformation. What does that mean? Presumably, that the company cannot no longer be primarily a supplier of mobile devices, but will attempt to build a new business based on mobile device management, mobile security, messaging, or who knows what.

It is relatively easy to explain why BlackBerry, whose dire financials released at the end of September triggered the crisis changes, got into trouble. Like Nokia, it found that a strong position in mobile phones had suddenly become a weak position, thanks to competition from Apple and then Android. The iPhone was not just a better mobile phone, but one that changed the computing landscape. I am not going to reiterate why, but think design, think apps, think usability, think mobile computing in place of smart phones. BlackBerry was not prepared for this, nor was Nokia, nor was Microsoft.

In October 2010 I wrote about which mobile platforms will fail. This was my list of current mobile platforms:

  • Apple iOS
  • Google Android
  • Samsung Bada
  • MeeGo
  • BlackBerry Tablet OS (QNX)
  • HP/Palm WebOS
  • Symbian
  • Windows Phone 7 and successors

Today, Samsung Bada, MeeGo, WebOS, Symbian and now BlackBerry 10 are gone or all-but gone. There are now three mobile platforms that matter:

  • Apple iOS
  • Google Android
  • Windows Phone

I realise that many have written off Windows Phone as a contender, but I include it because it is actually growing its market share, and because it is the future of Windows. Desktop and mobile versions of Windows will merge, and while Microsoft has challenges in this market, for sure it is not dead yet.

We should also at least nod to Amazon which is building its Kindle platform, based on Android but an Amazon platform, and will likely introduce a mobile phone at some point; and to Mozilla for Firefox OS; and to Samsung which is making efforts to meld Android into more of its own OS thus fracturing the platform, and to Chinese vendors like Xiaomi who are doing some of the same.

Why has BlackBerry 10 failed? Reviews have been mixed, but it is as far as I can tell a decent mobile OS, and the underling QNX embedded operating system was a good choice given that the company decided against Android.

However today you need not just a nice mobile platform but an ecosystem of huge scale. BlackBerry 10 may objectively have be better initial effort at a new mobile platform than Windows Phone 7 was, in a parallel situation, but it is even later, and lacks the backing of a deep-pocketed company content to lose money for years in the hope of eventually establishing its viability. BlackBerry also lacks the wider ecosystem that surrounds the other three platforms.

While no doubt the strategy adopted by Heins could have been improved, it was more that the task was too great, than that the execution was poor.

Asus Transformer Book Trio combines Windows and Android – but what is it for?

Microsoft has one idea about how to combine desktop Windows with a tablet OS: mash them together into a single operating system and call it Windows 8.

Asus has another idea. Put Windows in the keyboard dock, Android in the tablet, and allow the tablet to be docket to form a Windows or Android laptop.

This is the Transformer Book Trio, just launched and on sale from 11 November 2013 at £899.99.

image

All my instincts say this a terrible idea. Let Windows be Windows and Android Android, do not try to combine them.

Trying the machine though I found it was good fun. Just press the little Android button and it switches.

image 

and it becomes an Android laptop:

image

The dock mechanism is a bit ugly but looks robust:

image

There is the question still: what will you do with the keyboard when not in use? In a home context that is not a problem, but when on the road I find the most convenient place to keep a detachable keyboard is to attach it, making it more of a laptop than a tablet in practice.

Having two computers in one gives you a few options, which I did not have time to explore in detail. As I understand it, you can share storage in order to open a document prepared in Windows on Android, for example, and with two batteries there is scope for charging one from the other.

This is two separate computers though. It should really be called Duo, but Asus calls it Trio on the grounds that you can use it as a laptop or a desktop machine, with an external display.

The PC runs an Intel Core i5 4200U, and has 4GB RAM and 500GB hard drive. The display is 1920 x 1080 and supports capacitive 10-point multi-touch. Connectivity includes 802.11ac (dual-band) wi-fi, Bluetooth 4.0, 2 USB 3.0 ports, Mini DisplayPort, and Micro-HDMI 1.4.

The tablet has an Intel Atom Z2560 with 2GB RAM and 16GB storage. Connectivity includes   802.11n (2.4GHz), Bluetooth 3.0, Micro-USB 2.0, microSD card slot.

Fun then; but what is the use case for this machine? This is where I am still having difficulty. It is somewhat expensive (though with a Core i5 performance is decent), and I have a hunch that users will end up sticking with one or the other OS most of the time – probably Windows given the price.

Oddly, it would make more sense to me to have a high-end Android device with the ability to run Windows when needed. This would address the case where a user wants to migrate to Android but occasionally needs a Windows app.

Brief hands on with new Asus Windows 8.1 T100 tablet – or should that be netbook?

Asus has launched two new tablets in the UK.

This one is the 10.1″ T100 has an Intel Atom “Bay Trail” Z3740 quad-core processor. The display is 1366 x 768 and supports capacitive multi-touch.

image

You press a release button under the display to detach it from the keyboard, whereupon it becomes a tablet. This approach, it is now generally agreed, is better than a screen which twists over, since it gives you a reasonably thin and lightweight (550g) tablet rather one that is bulky and odd to hold. However, there is still the question of what you are going to do with the keyboard once detached, and I have a suspicion that these machines are likely to be almost permanently attached to the keyboard making them similar to netbooks.

image

Microsoft’s Surface overcomes this to some extent, especially with the Touch keyboard cover that folds underneath and adds little weight or bulk.

On the other hand, the T100 strikes me as good value at £349.99 (which includes the keyboard dock), especially bearing in mind that Office Home and Student is bundled (Word, Excel, PowerPoint, but no Outlook).

The T100 comes with 2GB RAM and 32GB eMMC storage. Connectivity includes Bluetooth 4.0, Micro-USB, Micro-HDMI, MicroSD slot, and a USB 3.0 port in the docking keyboard.

I tried the T100 briefly. I was impressed with the performance; Word and Excel opened quickly and overall it feels quick and responsive. I did not like the keyboard much; it felt slightly spongy, but at this price a few weaknesses can be forgiven.

The tablet Windows key is not under the screen as with most Windows 8 tablets, but a button on the side. What looks like the Windows key in the above snap is inactive, and that logo will not show on the production units.

First thoughts on Surface 2

After a day or two with Surface 2 and the Touch 2 keyboard, a few thoughts.

image

First, I am typing this on my desktop PC. I would have used the Surface 2, as I like to match the tool to the review, but no Live Writer on Surface (my favoured blog authoring tool) and no, Word is not as good for this.

That neatly demonstrates the app issue on Windows RT; but despite that I expect to use Surface 2 frequently in the coming months. It is an excellent tablet, with its chief advantages over the older Surface being performance and Windows 8.1, which includes Outlook.

Performance on Surface 2 is around 4 times faster for graphics – see previous post – and more than twice as fast in general.

The touch keyboard, now with backlighting, is also much improved.

I know I am in a minority here, but to me the Windows RT concept makes good sense. A locked-down version of Windows that is almost legacy-free, though it is still Windows and capable of throwing up mystifying dialogs and hiding settings in strange places.

It seems to me that if there is any hope for the Windows 8 app ecosystem, then it will be driven by tablets like this one, and Nokia’s new Lumia 2520 which also runs Windows RT. Desktop users are mostly ignoring the app platform. There are a few signs of life, like the new Facebook app, and things like Xbox Music are now decent. MediaMonkey, which I like for its Flac support, runs nicely on Surface 2.

Isn’t an iPad Air better? In some ways for sure. Usability, performance, size and weight, and rich app availability are all in the iPad’s favour, and price is similar. The reason you might get a Surface though is for Office, USB 3.0, HDMI out, SD card, and the clever keyboard cover. I also like having more than one app to view, whether that is Word and Excel on the desktop, or Word and Caculator, or the split view that works in the new app world.

I’ve hit a few snags with Surface 2. Sound is less good than on Surface RT, tending to be thin and reedy, unless you use headphones or external speakers. The Touch 2 keyboard sometimes stops responding, which I hope is a driver issue (perhaps the update downloaded this morning will fix it).

I also suspect that build quality on Surface 2 falls short of Surface RT. It is still “Vapor Mg” but I already have a slight dent in the bezel on mine whereas on my old RT it is still perfect and I wonder if it is thinner.

The extra price for the 64GB vs 32GB SSD is absurd. Why not make them all 64GB and increase the price by a fraction?

Is Microsoft serious about selling Surface 2? There does not seem to be much stock around, and it is not yet listed on Amazon.co.uk, although it has been on sale since yesterday.

Those that do discover it will like it, provided they understand the difference between Windows RT and Windows x86, something which – bizarrely – Microsoft still seems keen to disguise.