Tag Archives: windows 8

Imperfect Samsung Slate 7 tablet shows challenge facing Windows 8

I took advantage of a trip to Seattle to purchase a Samsung 7 Slate, similar to the one given to attendees at Microsoft’s BUILD conference last September, though missing some of its sensors.

image

It is a decent machine, fast and well-specified, but not one I can recommend unless, like me, you are keen to give Windows 8 Consumer Preview the best chance to impress, and cannot wait the short interval until machines that are actually designed for Windows 8 turn up on the market.

This is a Windows 7 slate, and that is the main thing that is wrong with it, since Windows 7 does not work well with touch control. Samsung’s solution is to cover all the bases:

  • A stylus is supplied so you can use pen control as with earlier Windows tablets
  • There is a matching Bluetooth keyboard
  • Samsung has created its own touch-friendly desktop with a selection of apps, so that you can avoid the classic Windows desktop

image

All these options make this an expensive device, but there are nevertheless a number of flaws and annoyances, some of which make you wonder “what were they thinking?” Here are some I have discovered in a few days of use:

1. There is an illumination sensor towards the top right of the screen bezel. This is a battery-saving measure, which adjusts the screen brightness according to the ambient light. Good thinking; except that if you are right-handed and controlling the slate with touch, your hand will often pass in front of the sensor. When that happens the screen dims, because it thinks the room is darker. The effect is that the screen constantly brightens and darkens in use, which is unpleasant. Fix: disable the feature and set the screen to a fixed brightness.

2. The on-screen keyboard is poor. This is the fault of Microsoft, not Samsung. If you have the keyboard set to float, the keys are too close together for fast typing. If you dock the keyboard, it becomes bigger, but impossible to use because it covers the bottom third of the screen. For example, it covers the search box on the Start menu when docked, so that you will be typing into it blind. Fix: Windows 8.

3. I got the matching Samsung wireless keyboard and found that the first key you press sometimes does not register. This is infuriating, especially for things like passwords. The reason, I discovered, is a setting in the Bluetooth card configuration “Allow the computer to turn off the device to save power.” When set, if you pause typing for 30 seconds, then the next key you press is in effect the on button and does not appear on the screen. Fix: uncheck this setting.

image

4. When using wifi at a meeting, I found that every two or three minutes I had to re-enter the username and password for the wifi hotspot. Nobody else had this problem. Fix: I am not sure, but updating the driver for the Intel wireless adapter plus sundry other Windows updates fixed it for me.

5. It is difficult to run without full administrator rights on the machine, as several Samsung utilities prompt for elevation.

6. There is no security button. This is the button that emulates Ctrl-Alt-Delete when you log on to Windows. Instead, you hold down the Windows key and press the power on switch – when you have discovered that this is what you have to do. It is not mentioned in the quick start leaflets. To be fair, this is only likely to be an issue if you do as I did and join the machine to a Windows domain. Samsung does include a Touch Logon application which lets you secure your machine with a simple code instead.

7. The pen sometimes stops working, or more precisely, the screen stops responding to the pen. Fix: pressing the screen rotation lock button seems to kick it back into life.

8. There is some clever coding that disables finger control when you are using the pen, which is a Wacom digitiser and not just a stylus. The idea is that you can rest your hand on the screen when using the pen. This mostly works, but I still find pen control less good on this device than on older Tablet PCs which respond only to the digitiser. The problem may be that when you lift the pen away from the screen, touch control turns back on. Whether or not this is the problem, I find it too easy to get unexpected behaviour.

9. Navigating the BIOS is difficult without a USB keyboard. It can be done. Volume up and down substitutes for the cursor keys, the Windows button is ESC and the rotation lock is Enter. The hard bit: switching between pages with volume and rotation button together. Fix: a USB keyboard.

10. The one solitary USB port has a tiny loose plastic cover which will soon get lost. For that matter, I will probably lose the expensive digitizer pen as well since it does not clip into the slate nor into the official Samsung case.

Is this a poor device then? Not at all. It is powerful and light, and works very well indeed if you pop the slate into its dock and use it with a wireless keyboard and mouse. In this guise though, it is more like a desktop PC.

When used purely as a slate though, this machine is far less usable than either an iPad or an Android tablet, both of which are also much cheaper.

Even some of the good ideas do not quite work properly. If you tap with three fingers, a floating panel appears with common actions that are otherwise tricky with touch, such as Ctrl-C for Copy. A great use of multitouch, except that if I do this in Windows Live Writer, it also registers as a zoom command which enlarges the text. Annoying.

image

All this is thought-provoking on the eve of the Windows 8 beta launch. Windows 8 in metro mode fixes the usability problems in the operating system, but will not prevent OEMs implementing half-baked ideas like Samsung’s illumination sensor. Further, people will buy Windows 8 tablets in part so that they can run desktop applications. How well will that work without docks, keyboards, pens and/or wireless mice, and high prices?

That said, Microsoft is aware of these issues which is why the Metro side of Windows 8 exists. The goal, I imagine, is that you will be able to stay in Metro all the time when using Windows 8 as a slate.

Tablets will be bigger than PCs. Are you ready?

Apple’s CEO Tim Cook spoke at the Goldman Sachs Technology Conference yesterday; Macrumors has what looks like a full transcript. Do not expect hot news; there is little or nothing in the way of announcements. It is interesting though as a recap of how Apple sees its future: iPad, iPhone, iCloud, Apple TV, maybe some future huge acquisition financed by its cash pile.

This is what stands out for me:

From the first day it shipped, we thought that the tablet market would become larger than the PC market and it was just a matter of the time it took for that to occur. I feel that stronger today than I did then.

I agree. The reasons are similar to those that caused laptops to outpace desktops. Mobility and convenience trump the better computing value you get in a desktop PC. Note: we still use desktops, and both desktops and laptops will continue to sell, but in smaller quantity.

Although you can list numerous reasons why tablets are not good enough – no keyboard, small storage capacity, underpowered for cutting-edge gaming, not really expandable, favourite apps not yet available, and more – none of these is sufficient to prevent the tablet taking over in the majority of cases.

You can have a keyboard if you want; build it into the case. Storage is increasing all the time, and we have the cloud. Graphics power is increasing all the time. Most people are happy to sacrifice expandability for the simplicity and reliability of a tablet. If your favourite app is not yet available, it soon will be; or else an equivalent will appear that replaces it.

Tablet benefits? Cost, no flappy screen, light and small, designed for ease of use, reliability of an appliance versus a computer for starters.

In itself, the move from one type of computing device to another is no big deal. The reason this one is such a deep change is because of other factors. I will list three:

  • The lock down

    Pioneered by Apple, this is the idea that users should not have full access to the operating system on their device in almost any circumstances. The lock down is a cost and a benefit. The benefit: resilience against malware, greater reliability. The cost: loss of control, loss of freedom, handing over even more power to those who do have full access, primarily the operating system vendor. Where UEFI secure boot is enabled, it is not even possible to boot to an alternative operating system.

  • The store

    Hand in hand with the lock down is the store, the notion that apps can only be installed through the operating system vendor’s store. This is not a universal tablet feature. Apple’s iPad has it, Microsoft’s forthcoming Windows 8 on ARM has it, Android devices generally let you enable “unknown sources” in order to install apps via a downloaded package, though sometimes this option is missing. Further, both Apple and Microsoft have schemes whereby corporates can install private apps. Still, the consequence of the lock down is that the ability to install apps freely is something which can be tuned either way. Since store owners take a cut of all the business, they have have a strong incentive to drive business their way.

    I have never believed Apple’s line that the iTunes store is intended as a break-even project for the convenience of its hardware customers.

  • The operating system

    I am at risk of stating the obvious, but the fact that most tablets are iPads and most non-Apple tablets are Android is a monumental shift from the Windows-dominated world of a few years back. Can Microsoft get back in this game? I am impressed with what I have seen of Windows 8 and it would probably be my tablet of choice if it were available now. The smooth transition it offers between the old PC desktop world and the new tablet world is compelling.

    That said, this cannot be taken for granted. I watched someone set up a new Android tablet recently, and was interested to see how the user was driven to sign up for a variety of services from Google and HTC (it was an HTC Flyer). Devices will be replaced, but accounts and identities are sticky. Users who switch devices may face having to move documents to a different cloud provider if they know how, re-purchase apps, figure out how to move music they have purchased, re-buy DRM content. A big ask, which is why Microsoft’s late start is so costly. At best, it will be a significant player (I think it will be) but not dominant as in the past.

    Late start? Did not Bill Gates wave a slate around and predict that it would be the future of the PC back in 2001:

    "So next year a lot of people in the audience, I hope, will be taking their notes with those Tablet PCs … it’s a PC that is virtually without limits and within five years I predict it will be the most popular form of PC sold in America."

    Right idea, wrong execution. Microsoft tried again with Origami, the ultra mobile PC, a device that was so obviously flawed that everyone knew it would fail. My belief is that Microsoft, helped by Apple’s example, has a tablet concept that works this time round, but nevertheless the history is discouraging.

    One reason for the relative failure of the Tablet PC and the complete failure of Origami was price. Microsoft’s business model depends on selling software licenses, whereas Apple mostly bundles this cost into that of the hardware, and Android is free. Price of the first Windows 8 tablets is unknown, but could again prove to be a problem.

    Interesting to debate; but however it shakes out, Windows-only is not coming back .

It follows that as tablet use continues to grow, both business and consumer computing are transforming into something different from what we have become used to. Considering this fact, it would be interesting to analyse affected businesses in terms of how ready they are for this change. It would be fascinating to see companies ordered by some kind of tablet readiness index, and my guess is that those towards the bottom of that hypothetical list are in for a nasty shock.

image

Where are the tablets for Windows 8 Consumer Preview?

Microsoft will deliver Windows 8 Consumer Preview shortly, probably on February 29th, since it has been promised by the end of this month and there is a launch event at Mobile World Congress.

The Windows Consumer Preview, the beta of Windows 8 on x86/64, will be available for download by the end of February. This next milestone of Windows 8 will be available in several languages and is open for anyone to download.

says Windows President Steven Sinofsky

The name of the preview suggests that Microsoft intends this release to be broadly downloaded and tried, in contrast to the developer preview with its more specialised role.

In preparation for the preview I looked around for a suitable tablet on which to test it – noting that it must be a Intel x86 or x64 tablet, since the ARM build (WOA) is not for general release, but only for manufacturers.

WOA will not be available as a software-only distribution, so you never have to worry about which DVD to install and if it will work on a particular PC.

Sinofsky writes.

So what is available? A quick Twitter consultation turned up a few options, such as the Acer Iconia Tab W500, the Asus Eee slate B121, and the Samsung Slate 7.

However, of these only the Samsung is really suitable, because it has a 1366 x 768 display. The others have 1280 x 800, and while this will run Windows 8 and the new Metro user interface, it will not support the Snap feature which gives you two applications on screen together:

The resolution that supports all the features of Windows 8, including multitasking with snap is 1366×768. We chose this resolution as it can fit the width of a snapped app, which is 320px (also the width designed for many phone layouts), next to a main app at 1024×768 app (a common size designed for use on the web).

Yes, it’s Sinofsky again.

Unfortunately the Samsung Slate 7 is not fully released in the UK, though I did find it on offer at ebuyer.com, for the not too unreasonable price of £973.19.

Samsung XE700T1A Series 7 Slate Tablet PC, Intel Core i5-2467 1.6GHz, 4GB RAM, 64GB SSD, 11.6" Touch, Intel HD, Webcam, Bluetooth, Wifi, Windows 7 Home Premium 64

That is still expensive, and it is hard to see it becoming a mass-market bestseller as Windows 8 fans rush to try out the new OS.

The consequence is that most users will try Windows 8 Consumer Preview on a virtual machine, or on an ordinary PC or laptop, or possibly on one of the cheaper 1280 x 800 tablets.

Since Microsoft’s main focus with Windows 8 has been on the new Metro touch user interface, this will not show the new operating system at its best.

I can personally testify to this. The Samsung slate handed out at the BUILD conference last September, which I had on loan for a few days, was delightful to use, whereas Windows 8 Developer Preview (the same build) is nothing special in a virtual machine.

All will be well, one assumes, when Windows 8 launches with both ARM and Intel-based machines available. Nevertheless, it seems to me a significant obstacle as Microsoft tries to build pre-launch enthusiasm; the risk is that users will not take into account how much better it is on a real tablet.

Update: a few other options have been suggested, like the Dell Inspiron Duo, a convertible 10.1” tablet with an Intel Atom  N570 Dual Core, 1366 x 768 display and 2GB RAM, and around one third of the cost of a Slate 7, but perhaps under-powered to show off the best of Windows 8.

Windows on ARM fixes much that is wrong with Windows, but lack of apps makes it Microsoft’s big risk

Vendors who create new platforms work hard to attract developers, because high availability of apps is seen as essential for success. This is why, for example, RIM is offering free PlayBooks to developers who submit apps to BlackBerry App World.

image

Why then would Microsoft deliberately and consciously choose to release a new family of Windows machines on which existing Windows applications cannot run, even when recompiled? This is what is happening with Windows on ARM (WOA), as Windows President Steven Sinofsky makes clear in his lengthy post on the subject:

Developers wanting to reach WOA with existing apps have two options. Many apps will be best served by building new Metro style front ends for existing data sources or applications, and communicating through a web services API … Other existing applications will be well served by reusing large amounts of engine or runtime code, and surrounding that with a Metro style experience.

This restriction means that WOA cannot benefit from what what might otherwise be its biggest advantage versus the competition: huge numbers of apps that could easily be ported.

Microsoft’s reasoning is that the existing Windows software deployment model is broken so badly that it cannot be fixed:

If we enabled the broad porting of existing code we would fail to deliver on our commitment to longer battery life, predictable performance, and especially a reliable experience over time. The conventions used by today’s Windows apps do not necessarily provide this, whether it is background processes, polling loops, timers, system hooks, startup programs, registry changes, kernel mode code, admin rights, unsigned drivers, add-ins, or a host of other common techniques. By avoiding these constructs, WOA can deliver on a new level of customer satisfaction: your WOA PC will continue to perform well over time as apps are isolated from the system and each other, and you will remain in control of what additional software is running on your behalf, all while letting the capabilities of diverse hardware shine through.

says Sinofsky. It is a view that has merit, particularly when you consider how badly Windows has been damaged by poor quality OEM software.

Note that he is even promising an end to Windows “cruft”, as memorably described by Verity Stob in State of Decay:

Cruft Force 7. Wounded. Description: No longer able to logon using original account as the system freezes, so must logon as "Verity2" or similar

and the like. “Your WOA PC will continue to perform well over time,” Sinofsky promises.

Another reason to like this approach is that the Windows Runtime (WinRT), the platform for which third-parties are allowed to develop, is in my view a great piece of work. The WinRT apps in the Windows 8 Developer Preview perform well, even though they are simple things put together quickly, many of them by students as I recall. The insistence on asynchronous calls for any system API that might be slow to return should ensure responsive applications.

At the BUILD conference last September we were told that the Windows team sat down to create a new platform that avoids the mistakes of the past and while it introduce frustrations of its own, some of which we know about and some of which developers will discover, it does appear to be well thought-through.

Microsoft Office itself is not the best performing of software, particularly Outlook which is prone to long hangs. Fortunately, Outlook is missing from the version of Office 15 which will ship for WOA, and journalist Adrian Kingsley-Hughes reports positively on a recent glimpse at the software.

The big risk

A sure-fire success then? No, because the downside of WOA is that right now there are no apps for it, beyond what we have seen in the developer preview. It is a brand new platform; and the history of personal computing is littered with good products that failed because they could not achieve sufficient momentum.

I am just back from RIM’s BlackBerry conference in Amsterdam, impressed by what I have seen of the PlayBook and forthcoming BlackBerry 10 platform and its tools for developers, but thinking, is this enough to persuade a customer to buy a BlackBerry tablet instead of the safe choices of Apple iOS or Google Android?

Microsoft has the market presence to make this work, you may think; but the Windows Phone 7 story so far shows that this is not enough. The new phone OS has only a tiny market share after a year, and if it recovers, it will be more to do with Nokia than with Microsoft.

WOA also has interesting competition in the form of Windows 8 on x86, which will also have WinRT, but without the restrictions on desktop apps. If partners focus on Intel Windows 8, as the “full” version, it could be hard for WOA to find its market.

There are problems with Windows 8 on x86 too. Most of existing Windows apps will need a keyboard and mouse to work properly, and expect to find large amounts of storage, not the 16 or 32 GB in a typical tablet. Windows 8 Intel devices may end up like the Samsung tablet given to attendees at BUILD: powerful, but heavy, expensive, with short battery life, and complete with the clutter of a separate keyboard. Such devices have their place, but they are not an answer to the iPad.

It is WOA, not Windows 8 x86, that has to win market share from Apple.

Microsoft is choosing to do WOA right, rather than opening it up to the kinds of problems which have afflicted Windows in the past. That does makes sense, because it is those problems which have made users gladly move away from Windows now that compelling alternatives are available.

I also believe that OS vendors work too hard to pump up the app numbers, and not hard enough to ensure quality, resulting in app stores full of poor to indifferent apps. This is why schemes like the BlackBerry effort mentioned above do as much harm as good, enticing developers to submit rubbish in order to win a new gadget. An app store with 10 great apps is better for users than one with a thousand poor ones.

It is nevertheless true that apps make or break a platform. BUILD attendees and those who have downloaded the Windows 8 developer preview have had the tools to make WinRT apps for a few months now, but my impression is that most are waiting to see how it progresses before investing seriously in WinRT development. Another problem is that Windows 8 developer preview works nicely on a real tablet, but not so well in a virtual machine or on a PC without a touch screen.

I still think WOA may work.

  • If Microsoft does a good job with WOA Office, giving it an unique selling point against the competition.
  • If the WOA devices are competitively priced.
  • If the battery life is good.
  • If there are at least a handful of truly worthwhile third-party apps at launch.
  • If there is not some obvious problem with stability, or an annoyance that spoils the experience, like the one I found on the PlayBook when the virtual keyboard failed to pop up when trying to author a tweet in the web browser.

That is a lot of ifs though, and the progress of WOA will be a fascinating tech story throughout 2012.

Windows on ARM: Microsoft can write Desktop apps, but you cannot

Microsoft’s Windows chief Steven Sinofsky has written a long post describing Windows on ARM (WOA), which he says is a:

new member of the Windows family, much like Windows Server, Windows Embedded, or Windows Phone

There are many point of interest in the post, but the one which stands out for me is that while the traditional Windows desktop exists in WOA, third party applications will not be allowed there:

Developers with existing code, whether in C, C++, C#, Visual Basic, or JavaScript, are free to incorporate that code into their apps, so long as it targets the WinRT API set for Windows services. The Windows Store can carry, distribute, and service both the ARM and x86/64 implementations of apps (should there be native code in the app requiring two distributions).

says Sinofsky. He writes with extreme care on this issue, since the position for which he argues is finely nuanced. Why have the Windows desktop on WOA at all?

Some have suggested we might remove the desktop from WOA in an effort to be pure, to break from the past, or to be more simplistic or expeditious in our approach. To us, giving up something useful that has little cost to customers was a compromise that we didn’t want to see in the evolution of PCs

he says, while also saying:

WOA (as with Windows 8 ) is designed so that customers focused on Metro style apps don’t need to spend time in the desktop.

From a developer perspective, the desktop is more than just a different Windows shell. Apps that run on the Windows Runtime (WinRT) are isolated from each other and can call only a limited set of “safe” Windows APIs, protecting users from malware and instability, but also constraining their capabilities. The desktop by contrast is the old Windows, an open operating system. On Windows 8 Intel, most things that run on Windows 7 today will still work. On WOA though, even recompilation to target the ARM architecture will not help you, since Microsoft will not let desktops apps install:

Consumers obtain all software, including device drivers, through the Windows Store and Microsoft Update or Windows Update.

What if you really want to use WOA, but have some essential desktop application without which you cannot do your work, and which cannot quickly and easily be ported to WinRT? Microsoft’s answer is that you must use Windows on Intel.

That said, Microsoft itself has this problem in the form of Office, its productivity suite. Microsoft’s answer to itself is to run it on the desktop:

Within the Windows desktop, WOA includes desktop versions of the new Microsoft Word, Excel, PowerPoint, and OneNote, codenamed “Office 15”.

No Outlook, which I take to imply that a new WinRT-based Exchange client and PIM (Personal Information Manager) is on the way – a good thing.

Microsoft’s aim is to give customers the security and stability of a locked-down machine, while still offering a full version of Office. If you think of this as something like an Apple iPad but with no-compromise document editing and creation, then it sounds compelling.

At the same time, some users may be annoyed that the solution Microsoft has adopted for its legacy desktop application suite is not also available to them.

The caveat: it is not clear in Sinofsky’s post whether there may be some exceptions, for example for corporate deployments, or for hardware vendors or mobile operators. It will also be intriguing to see how Office 15 on ARM handles extensibility, for example with Office add-ins or Visual Basic macros. I suspect they will not be supported, but if they are, then that would be a route to a kind of desktop programming on WOA.

It will be interesting to see how Microsoft locks down Explorer, which Sinofksy says is present:

You can use Windows Explorer, for example, to connect to external storage devices, transfer and manage files from a network share, or use multiple displays, and do all of this with or without an attached keyboard and mouse—your choice.

By the way, this is a picture of the Windows ARM desktop as it looked at the BUILD conference last September. The SoC (System on a Chip) on this machine is from NVIDIA.

Windows Phone 8 “Apollo”: Windows 8 kernel, more form factors

Microsoft’s partner ecosystem is vulnerable to leaks, as demonstrated today by reports of a video said to have been made for Nokia, which arrived in the hands of a smartphone review website. The leaked information was corroborated by Windows journalist Paul Thurrott who has received advance information independently from Microsoft, but under non-disclosure:

Thanks to a recent leak which has revealed some interesting information about the next major Windows Phone version, I can now publicly discuss Windows Phone 8 for the first time.

First, a quick recap:

  • Windows Phone 7.5 “Mango” came out in the second half of last year and was the launch OS for Nokia’s Lumia phones.
  • Windows Phone “Tango” is expected in the second quarter of 2012 and appears to be a minor update focused on low-end handsets.
  • Windows Phone “Apollo” is the subject of the new leaks. Some of the details:
  • Uses the Windows 8 kernel and other OS components, rather than Windows CE
  • Supports multicore processors
  • Supports more form factors and screen resolutions
  • Preserves compatibility with Windows Phone 7 apps
  • Adds BitLocker encryption

I presume this also means that native code development will be supported, as it is for the Windows Runtime (WinRT) in Windows 8.

Date for “Apollo”? The rumour is towards the end of this year, as a close follow-on from Windows 8 itself.

Like many leaks, this one raises as many questions as it answers. While it makes sense that Windows Phone 8 and Windows 8 should share the same kernel, it also raises the question of  how they are differentiated. Windows 8, especially on ARM, is designed for small screens and tablets. Windows Phone 8, we now learn, will support more form factors. The implication is that there may be Windows Phone 8 devices that are close in size to Windows 8 devices. Will they run the same apps from the same Marketplace, at least in some cases, in the same way that some iOS apps support both iPhone and iPad?

The Windows 8 and Windows Phone 8 era will be simplified in one sense, with a single core operating system across desktop and devices. In another sense though, it ushers in new complexity, with multiple platforms that have subtle or not so subtle differences:

  • Windows 8 desktop side, on laptop and tablet (x86)
  • Windows 8 desktop side, laptop and tablet (ARM) – rumoured to be locked down for Office and perhaps a few other favoured apps
  • Windows 8 Metro side, desktop, laptop and tablet (x86) which should be nearly the same as
  • Windows 8 Metro side, desktop, laptop and tablet (ARM) – runs WinRT
  • Windows Phone 8 – runs WinRT, plus Silverlight compatibility layer

My guess is that Microsoft will push WinRT as the single platform developers should target, but I can see scope for confusion among both developers and users.

What would you like to see in Microsoft Office 15?

Today brings the news that Microsoft Office 15 is now in Technical Preview (also known as private beta).

There is little news about what is in it other than this:

With Office 15, for the first time ever, we will simultaneously update our cloud services, servers, and mobile and PC clients for Office, Office 365, Exchange, SharePoint, Lync, Project, and Visio.

image

So what would you like to see in Office 15? Here are a few things on my wish list:

  1. Properly integrate SharePoint (and therefore Office 365) with Windows so that you can use it easily without ever opening a web browser. That might mean fixing SharePoint WorkSpace or doing something better, like Explorer integration without the various hassles associated with WebDAV.
  2. Fix Outlook, or better still replace it. I hear many complaints about Outlook, either concerning its performance, or else one of its many annoyances such as how hard it is to reply to an email while quoting sections of the original message – astonishing, when you consider the maturity of the product.
  3. Improve cross-platform support. Office on the Mac is poor compared to the Windows version, particularly in terms of performance. It is also time Microsoft came out with apps for iOS and Android for touch-friendly document editing.
  4. Update the user interface for touch control as far as possible. This will be critical for Windows 8 tablets, especially on ARM.
  5. Improve structured document editing in Word. Styles are hard to use, so are bullets and numbering. I tend not to use the paragraph numbering in Word because it is so fiddly and annoying.

The problem is that Office is a huge and intricate bag of legacy. The work Microsoft did in replacing the menus with ribbon toolbars was admirable in its way, and potentially more touch-friendly, but if you scratch the surface much is unchanged underneath. All the old commands remain.

Storage Spaces coming to Windows 8 client as well as server

Steven Sinofsky has posted on the Building Windows 8 blog, making it clear that this feature is coming to the Windows 8 client as well as to Windows Server 8.

I took a hands-on look at Storage Spaces back in October.

The feature lets you add and remove physical drives from a pool of storage, create virtual disks in that pool with RAID-like resiliency if you have more than one physical drive available. There is also “thin provisioning”, which lets you create a virtual disk bigger than the available space. It sounds daft at first, but makes sense if you think of it as a resource to which you add media as needed rather than paying for it all up-front. It

The server version includes data deduplication so that similar or identical files occupy less physical space. Another feature which is long overdue is the ability to allocate space to a virtual folder rather than to a drive letter.

I do not know if all these features will come to the Windows 8 client version, but as data deduplication is not mentioned in Sinofsky’s post, and the dialog he shows does not include a folder option, it may well be that these are server-only. This is the new Windows 8 dialog:

image

Storage Spaces occupies a kind of middle ground in that enterprises will typically have more grown-up storage systems such as a Fibre Channel or iSCSI SAN (Storage Area Network). At the other end of the scale, individual business users do not want to bother with multiple drives at all. Nevertheless, for individuals with projects like storing large amounts of video, or small businesses looking for good value but reliable storage based on cheap SATA drives, Storage Spaces look like a great feature.

Most computer professionals will recall seeing users struggling with space issues on their laptop, not realising that the vendor (Toshiba was one example) had partitioned the drive and that they had a capacious D drive that was completely empty. It really is time that Microsoft figured out how to make storage management seamless and transparent for the user, and this seems to me a big step in that direction.

Not allowed in Windows 8 Metro: porn, ads in live tiles, bugs, or opt-out data collection

Microsoft’s newly published Certification Requirements for the forthcoming Windows 8 store includes some notable points. Here are a few that caught my eye.

2.3 Your app must not use tiles or notifications for ads

No complaints about that one.

3.2 Your app must not stop responding, end unexpectedly, or contain programming errors

Hmm, this could be a tough one.

3.3 Your app must provide the same user experience on all processor types

OK, no “Intel-only” features. However you could by implication submit an “Intel-only” version of your app as long as it is called something different than than the ARM version.

3.7 Your app must not use an interaction gesture in a way that is different from how Windows uses the gesture

This is interesting as an example of enforcing application style guidelines. The intent is a consistent user experience, but is this heavy-handed?

4.1 Your app must obtain opt-in or equivalent consent to publish personal information

No stealthy personal data collection. A good thing; though if opt-in means “Hand over your data or you cannot run the app” it can still be difficult for users to avoid.

4.4 Your app must not be designed or marketed to perform, instruct, or encourage tasks that could cause physical harm to a customer or any other person

What a relief!

5.1 Your app must not contain adult content

Windows Metro a porn-free zone? This could be troublesome though. No games beyond PEGI 16? This is a preliminary document and it would not surprise me if there is some change here; maybe this is a restriction for the beta period only.

Windows Store: Microsoft explains another piece of its new platform

Microsoft’s Ted Dworkin, Partner Progam Manager, has posted details of how the forthcoming Windows Store will work. There is also detailed new information on MSDN. It is a key piece if you care about the next version of Windows, including details of how enterprises will be able to deploy apps as well as the terms of business for independent developers.

image

Here is a quick summary:

  • The store is both an app and a web site. The same content will automatically appear in both.
  • The store is for Metro-style apps, which run on the Windows Runtime. No word about desktop apps; my presumption is that they are excluded. The certification requirements refer only to Metro-style apps.
  • Apps can be offered as full-featured, limited or unlimited trial, upgradeable via in-app purchases.
  • Enterprise apps can be deployed through the store with access limited to employees.
  • Enterprise apps can also be deployed outside the store, using PowerShell scripts to domain-joined machines. Apps must be signed.
  • App vendors can use their own transaction engine and/or ad service if they choose, or use the built-in services for sale, in-app purchase and advertising. Subscriptions do not have to go through the store. My impression is that the initial sale does not have to be transacted through the store either but this is not 100% clear to me.
  • Developer registration for the store costs $49.00 for individuals or $99.00 for companies.
  • Revenue share is 70%, rising to 80% if you achieve over $25,000 revenue for an app.
  • Apps are subject to approval, but developers are given the App Certification Kit as part of the SDK. There is still scope for disagreement over the interpretation of policies.

 

There is an initial beta preview period during which all apps will be free. Microsoft has also annoyed most of the world’s developers by restricting a First Apps Contest to those who:

 are a developer – professional, hobbyist, or student – and you are a legal resident of the 50 United States and District of Columbia, France, Germany, Japan, or India