Tag Archives: microsoft

apple, microsoft, software development

Mac App Store, Windows Store, and the decline of the open platform

2 Comments

Valve Software’s Gabe Newell caused a stir recently when he said at the Casual Connect event in Seattle that Microsoft’s Window 8 is bad news gfor game vendors:

I think Windows 8 is a catastrophe for everyone in the PC space. I think we’ll lose some of the top-tier PC/OEMs, who will exit the market. I think margins will be destroyed for a bunch of people.

What did he mean exactly? He denigrates touch control, which he says is “short-term”, so I would guess he is not enthusiastic about the touch-centric Metro-style UI in Windows 8. However, he also talks about open platforms:

"Valve wouldn’t exist today without the PC, or Epic, or Zynga, or Google. They all wouldn’t have existed without the openness of the platform … We are looking at the platform and saying, ‘We’ve been a free rider, and we’ve been able to benefit from everything that went into PCs and the Internet, and we have to continue to figure out how there will be open platforms.’

The point: Valve runs its own Windows app store, called Steam, and will lose out if an increasing proportion of game downloads go through Microsoft’s Windows store instead.

image

Of course Steam will work fine on Windows 8, provided you have the x86 version. The x86 Windows 8 desktop operating system is just as open as Windows 7. The Windows Store also allows entries that link directly to a vendor’s web site, like the one for Winzip:

image

The immediate threat to Steam then is indirect. If Windows 8 fails in the market, it will not be too bad for Steam since it runs on Windows 7 and on the Mac, the most likely beneficiaries. Steam will suffer if Windows 8 users are drawn towards the Windows Store in preference, though note that the Store does not offer desktop app downloads except via links as for Winzip above. Steam will also suffer if the ARM version of Windows, Windows RT, eats into Windows x86 sales.

You have to follow the lines on the graph though, and this is where it does not look so good for Steam. Look first at Apple’s platform. The mobile variant, iOS, is entirely locked down so most users can only acquire apps from the Apple app store, unless they are developers or enterprise customers. Apps are also sandboxed so that you cannot break your iOS device by making bad install decisions. Partly as a side-effect of the sandboxing, apps are trivially easy to install and remove provided you have an internet connection. Far from limiting sales, this has encouraged users to experiment with apps they might not otherwise have found or wanted to risk installing, and users love the iOS platform overall.

On the Mac, Apple has introduced another app store. Unlike the iOS store, use of this is optional, though some apps cannot be obtained elsewhere. There is some not-so-subtle pressure to use the store though, partly because of how it is surfaced in the user interface, and partly because of the advantages for the user. Apps are easier to install and update themselves, in the same way as on iOS. They are vetted by Apple so should be safe to use. They have to conform to Apple’s application guidelines which form a kind of sandbox. Apps may not request root privileges, may not download additional code, may not use non-public APIs, cannot install code in shared locations, and so on. They also have to conform to certain ethical guidelines.

Whether this is altogether good for users is up for debate. It is a trade-off between freedom on the one hand, and convenience and safety on the other. On the whole though, users like it, which is great news for Apple which also takes a slice of any payments that go through the store.

Not all software vendors are happy. Sherman Dickman at Postbox is abandoning the Mac App Store. He gives these reasons:

    • No free trials
    • No discounted upgrades
    • No free upgrades if the prior version was purchased after a specific date
    • No way to provide license keys that could be used on Windows (many of our customers use both platforms)
    • No volume discounts or site licensing
    • No access to customer information, which prevented us from validating orders, offering discounts, running promotions, newsletter signups, etc.
    • Unclear refund policies
    • Most importantly, we had to create another version of Postbox for the Mac App Store that removed features such as iCal support, iPhoto integration, and Add-Ons in order to comply with Apple’s Application Guidelines

Postbox 3 is sold only direct from the vendor’s site. Dickman says he will reconsider if Apple loosens the restrictions on the App Store; but the real question will be whether his company can afford not to be in the official store, especially if future versions of Mac OS X further tighten the screws.

Returning to Windows 8, Microsoft is undoubtedly suffering from Apple envy. There are multiple reasons:

  • Users like the app store model, its convenience and safety
  • Apple has found a solution to a problem that plagues Windows: damage from third-party software installs
  • Microsoft would like a cut of the revenue from software transactions

Windows 8 therefore has an iOS-like store and policy for its Metro side. The net result is similar to that for iOS and Mac OS X. On the ARM Metro-only systems (ignoring for a moment the locked-down desktop which runs Office and a few utilities), apps can only be installed through the store. On the open x86 systems, use of the store is optional, except that Metro-style apps must be installed through the store unless you are a developer or an enterprise.

Microsoft has a harder job than Apple to make its store successful, because of the way it is combining the Metro-style platform and the old desktop into a single operating system. If users turn their backs on Metro, the store will fail too. Still, Microsoft is aiming for a platform that is equally as locked down as Apple’s.

Instinctively I dislike these lockdowns, yet I also see their merit. Recently I found myself helping a user clean up their Windows 8 Release Preview system, which already had unwanted software on it, put there by installers that foist unrelated software on users who forget to uncheck a box, including toolbars and security software. Vendors have abused the freedom that Windows gives them.

The evidence though is that users will happily give up some freedom in return for a secure and convenient operating system. The business model favours it too. The Windows 8 upgrade is cheaper than for earlier versions, maybe because Microsoft will earn more later if users buy lots of apps. It pays Google to sell the Nexus tablet with low margins, if it drives users to the Play Store.

The convergence of all these factors means one thing only: that open platforms are in decline. They are not gone yet, but that is the firm trend. The implications are profound and I doubt they will be fully appreciated until the line on the graph has progressed a little further. The internet is a huge mitigating factor of course, and perhaps the combination of an open internet with a locked-down client is one that we will be able to live with.

cloud computing, microsoft, visual studio, Web

Access Web App: at last a simple web database app builder from Microsoft

4 Comments

One thing hardly mentioned in the press materials for Office 2013, and therefore mostly ignored in the immediate publicity, is Microsoft Access 2013. It is included though, and its most interesting new feature is a thing called an Access Web app.

image

To make one of these, you click the big “Custom web app” button on the opening screen. The first thing you are asked is where to put it. It is looking for a SkyDrive or Office 365 team site – essentially, online SharePoint 2013 I imagine. If you are not signed in, this screen appears blank.

Advertisement

I selected Skydrive at my Office 365 preview site.

image

Hit Create and you can select an app from a template. I chose a Music Collection app. Access generated several tables and forms for me and opened the design environment.

image

The template app is a bit daft – Artists and Labels are based on a People template, so you get Labels with a Job Title field – but that does not bother me. What interests me is that Access generates a relational database that you can edit as you like. The template UI offers either a list/detail view called a List, or a Datasheet which shows rows in a grid format. There is also a Blank view which you can design from scratch.

I had a quick poke around. Access Web Apps do too good a job of hiding their innards for my taste, but what you get is a SharePoint app with data stored in SQL Server Azure. You can also use on-premise SharePoint and SQL Server 2012.

Programmability in Access Web Apps is limited, but you do get macros which let you combine multiple actions. There are two kinds of macros, UI macros and Data macros. UI macros support a range of actions including SetVariable,  if and else statements. The only loop functions I can see are in Data macros, which include a ForEachRecord action. You can call Data macros from other macros and a Data macro includes a SetReturnVar statement, so I guess with a bit of ingenuity you can do many kinds of automated operations. Macros are described here.

image

In my quick test, I put a button on a view and had it show a message. Apologies.

The application files are all stored on SharePoint, rather than locally, so I presume you could easily edit the app on any machine with Access 2013 installed.

Click Launch App and the web app opens in the browser. Everything worked, including my MessageBox.

image

I also tried it on the Google Nexus 7 Android device. Again it seems to work fine, though I did get some odd behaviour returning to the app. There are possibly some authentication issues.

image

An Access Web App is just another SharePoint app, as explained here, so you can publish it to selected groups via the built-in store.

There is no way that I can see to craft your own SQL, which to me is a disadvantage, but maybe we will discover how to bypass the UI and open a database in SQL Management Studio, or access it programmatically from other environments.

It seems to me that what Microsoft is offering here is what it tried, but failed, to offer in Visual Studio Lightswitch: database programming for the non-specialist. Access has always done this, though unfortunately it is easy to make rather a mess if you do not know what you are doing. An Access Web App gives the developer/user fewer ways to go wrong, and builds cross-browser web apps. It is not yet possible to judge whether Microsoft has got the feature set right, but fundamentally this looks useful for simple custom business database applications of the kind that many small organisations and departments find they need. It is a big advance on MDB files stuck on a file share, fits with the BYOD (Bring Your Own Device) concept by working on iPads and the like, and makes it easy to get started and experiment. Good work.

.net, cloud computing, microsoft, professional, salesforce.com, software development

Office 365 for developers: Getting started with Microsoft Napa

One key aspect of Microsoft’s forthcoming Office 2013 is its support for a new app model. The idea is that rather than building local add-ins for desktop Office, you will build web applications that live in one of four places:

  • In SharePoint
  • Within an Excel document
  • Within a Task pane in Excel or Word
  • Adjacent to an email in Outlook
Advertisement

If you have been following Office development for a while, it is hard to supress an initial reaction of “oh no, not another development model for Office.” After all, we have had Basic macros, Visual Basic for Applications, COM Add-ins, Visual Studio Tools for Office, and in the case of Exchange, other APIs such as MAPI and Exchange Client Extensions. Further, most of this stuff still works, which is a mixed blessing as the the whole thing gets more bloated and confusing.

Even so, I can see the sense of the new Apps for Office. One key advantage is that they work in Office Web Apps as well as in the desktop applications. They are also easier to deploy and secure, since they require no executable files on the client, are sandboxed, and only interact with the local document via a JavaScript library. That may not always be sufficient of course, in which case you can stick with one of the older extension models (personally I still find VBA useful), but where it is sufficient, this strikes me as a good approach.

That said, there are plenty of gaps in the list of supported app types:

Application Supported types
Excel 2013 Preview Task pane, Content
Excel Web App Preview Content
Word 2013 Preview Task Pane
Outlook 2013 Preview Mail
Outlook Web App Preview Mail
Project Professional 2013 Preview Task Pane

It would be good to see content apps supported more widely. Still, it is a start.

Office program manager Brian Jones has an excellent post on the background to apps for Office and SharePoint, which inspired me to sign up for a developer preview. Microsoft had already created an Office 365 preview account for me, but this other one is the real deal: you get to administer an entire test organization, complete with SharePoint, Exchange 2013, and all the Office 2013 preview apps.

After sign-up, it took a few minutes to provision, and then I was able to add the Napa development tools to the site. This is itself a cloud app. It is easy to get started: choose the type of app you want and you are in.

image

Napa is a cloud IDE, essentially a code editor with some syntax highlighting and code completion.

image

The real joy, if you have ever done SharePoint development, is how easy it is to deploy. Just click the Run button.

image

Once installed, you can launch the app with a click, provided you have enabled pop-ups on the site. An Excel content app works in the same way, but opens up the app running in an Excel Web App spreadsheet.

I am sure seasoned Microsoft platform developers will find Napa rather limiting, but there is also an Open in Visual Studio button, and all going well you should be able to do most of your coding in Visual Studio, upload back to Napa, and still get the benefit of easy test and deploy.

image

If you are pleased with your app you can easily offer it for sale by publishing to the Office store:

image

The implications for Office 365 are rather profound. It is evolving into a true extensible cloud platform, where businesses can add apps and deploy to their users using an app store model.

That said, you can argue that Microsoft is playing catch-up here. For example, Salesforce.com has had Force.com for years, and I know from visiting the huge vendor exhibitions at events like Dreamforce how strong that marketplace has turned out to be. Salesforce has also enabled its users to build apps in the cloud for many years now.

All true; but Microsoft’s approach does have the advantage of continuity. As I mentioned above, the old stuff still works, so customers can move at their own pace towards a cloud-based platform.

For more information, I recommend this overview.

cloud computing, microsoft, professional, software, windows

Offline web mail in new Office 365 and Exchange 2013 Outlook Web Access

2 Comments

Microsoft has posted details of the forthcoming Exchange 2013, and one of the features that intrigues me is the ability to use the browser-based email client, Outlook Web Access (OWA), offline.

Since offline use is one of the primary issues with web applications, this is a key feature. It would be particularly interesting if it worked with mobile devices such as the Apple iPad or Google Android tablets.

I asked about this and was directed to this table, which states that offline access is supported in Internet Explorer 10 or later, Safari 5.1 or later, and Chrome 18 or later. Offline is not supported on mobile browsers, nor on “Windows 8 tablet”.

image

I have not seen Microsoft use the term Windows 8 tablet in a technical sense before. I presume it means Metro-style IE and Windows RT?

Next, I went to my preview Office 365 account on a Windows 8 tablet (ha!) but in desktop IE, and noticed that OWA already has an offline option there, which I presume is essentially Exchange 2013 though perhaps with some differences.

image

I selected the option and was prompted to confirm.

image

I clicked Yes and was prompted to add to favourites.

image

Then I closed the browser, turned on Airplane mode, and restarted.

Success! I was able to return to OWA, compose and send an email. Note the Airplane mode icon in the screen grab.

image

Looking at IE settings I also had an offline cache set for outlook.com.

image

I closed the browser, re-enabled the network, and restarted.

Bad news, my first email was never sent. I tried again though, and this time confirmed that, while offline, my email was in an unsent folder.

image

However, when I went back online I could not see it in sent items. I made a third attempt. Eventually though, both my second and third attempts succeeded and I got the email.

image

That’s good, but I have a few observations (bearing in mind that this is preview software):

1. The experience in Metro-style IE is terrible. You can enable offline there (I tried) but it does not work. And where is the cache setting for Metro-style IE, is it shared with desktop IE? Does it have one? This whole relationship between the two forms of IE 10 in Windows 8 is obscure and difficult.

2. What happened to my first email? Did I not in fact click send (I am fairly sure I did)? Losing emails is bad and can be costly.

3. This offline setting would be particularly useful on mobile devices so I would like to know what plans Microsoft has to get it working.

microsoft, sharepoint

Recovering documents from SharePoint 2010

I mentioned the other day that an update broke my SharePoint installation. The timing was bad as I was just about to leave the office for a few days, so as it turned out I did not get to focus on this properly until last weekend. This virtual server is backed up nightly. I restored from before the failure but it still did not work. Perhaps there was an update pending that was not fully applied until the server restarted, so that even my “good” backup was bad.

The error was frustrating. Accessing a SharePoint site got me a 503, service unavailable. I could run either psconfig or the SharePoint Configuration Wizard without error, but it still did not work. The event log showed a bunch of errors that made little sense to me, including those annoying DCOM activation errors, and database login errors when the accounts concerned had valid logins.

It was wasting too much time so I went for plan B. Reinstall SharePoint from scratch and restore the content database.

This was actually easier than I expected. I backed up WSS_Content using SQL Server Management Studio. I then removed everything SharePoint, and deleted a couple of remnants in IIS. Reinstalled and everything worked.

After that it was simply a matter of attaching the old content database. Well, nearly that simple. My first attempt failed because SharePoint was not fully patched and had an earlier schema than the content database. I manually downloaded and applied the latest SharePoint hotfix rollup. Then I attached the old content database to a new SharePoint site, and everything came up just as before.

I find this reassuring, as keeping documents as blobs in SQL Server is just a little scary from a recovery perspective.

Even if attaching the database were to fail, it is not too bad. You can write code to write out the documents to files and recover them that way. There are some clues here.

microsoft, windows

Intranet and Mail hassles with Windows 8

Microsoft has made changes to networking in Windows 8, mainly I presume for security reasons, but there are odd side-effects, at least in the Release Preview version.

One is that if you browse to a site on your intranet in the Metro-style browser, you are likely to get a connection failure. This is what I get when trying to get to my Logitech Media Server (the Squeezebox server):

image

A bunch of useless, misleading suggestions and that is it.

The solution is to go to desktop IE, Tools, Internet options, Security, Trusted Sites, Sites and add the target URL to the list of Trusted sites. Now it works fine in Metro-style IE:

image

I got exactly the same behaviour with Outlook Web Access on the intranet. It did not work from Metro IE until I added the URL to Trusted Sites.

I am not sure if this is “expected behaviour”; I hope it is not, because it is a significant annoyance. The answer may lie in Microsoft’s Enhanced Protected Mode, described here, but although this states that Metro-style apps cannot connect by default to a server running on the same machine, it does not suggest that the entire intranet is blocked. The security benefits are also compromised if you can easily bypass them by running desktop IE.

While I am on the subject, I am still puzzled by the problems the Metro-style Mail app has with connecting to Exchange when this is configured with a self-signed certificate. I obtained a free SSL Cert from StartCom and confirmed that using a cert from a recognised issuer does fix the problem, though it is not a perfect solution for me because of the detail of my setup.

I would still like to know exactly what is stopping the self-signed approach from working. There are numerous discussions on the subject (this is one of the best) but I have not seen any definitive explanation from Microsoft. Following a suggestion from that thread, I have tried publishing the CRL (Revocation List) on the internet but that has not fixed it for me.

Security is great but we do want to get stuff done with our computers and some of this stuff just seems obstructive. Even if Microsoft is doing the right thing here, that is no excuse for false error messages. Mail, for example, reports “Unable to connect. Ensure that the information you’ve entered is correct.” How hard would it be to report a problem with the server certificate?

microsoft

Microsoft financials: still growing in the cloud era, but watch out for tablets

7 Comments

I am in the habit of putting Microsoft’s results into a simple table. Here are the latest:

Quarter ending June 30th 2012 vs quarter ending June 30th 2011, $millions

Segment Revenue Change Profit Change
Client (Windows + Live) 4145 -598 2397 -511
Server and Tools 5092 +568 2095 +409
Online 735 +55 -6672 -5927
Business (Office) 6291 +339 4100 +399
Entertainment and devices 1779 +292 -263 -276

It is easy to spot the stars: Server and Office.

It is also easy to spot the weaklings, especially Online, which reported a breathtaking loss thanks to what the accounts call a “goodwill impairment charge”. This translates to an admission that the 2007 acquisition of aQuantive was a complete waste of money.

Mixed signals from Entertainment and devices, where revenue is up but a loss is reported. Since this segment munges together Xbox and Windows Phone, it seems plausible that the phone is the main culprit here. Microsoft identifies payments made to Nokia and the addition of Skype as factors.

Windows is down, in part because Microsoft’s upgrade offer for Windows 8 means some revenue is deferred, though one would imagine that worldwide reports of stagnant PC sales are a contributory factor as well.

If you add up the figures, and allow for overheads, it comes to a wafer-thin operating income of $192 million and a $0.06 loss per share.

What do the figures tell us? Two things: Microsoft still makes a ton of money, and that it is exceedingly bad at acquisitions. I am not sure how a company can mislay $6.2bn without heads rolling somewhere, but that is not my area of expertise.

Microsoft’s Server 2012 family has impressed me so my instinct is that we will see good figures continue there.

On the Office side, it is not all Word and Excel. “Exchange, SharePoint and Lync together grew double-digits,” Microsoft said in its earnings call, adding that Lync revenue is up 45%.

That said, how many server licences can you sell in the cloud era? How can Microsoft grow Azure without cannibalising its server sales?

It is tempting to state, like James Governor at Redmonk, that this is The End of Software: Microsoft Posts a Loss for the First Time ever. Microsoft’s figures have stubbornly refused to prove this though; and a quarter where revenue has risen though poisoned by an acquisition disaster is not the moment to call it.

Microsoft has survived the cloud. The bigger question now is whether it can also survive tablets eating into its Windows sales, not helped by Google pushing out Nexus 7 at casual purchase price – see my first take here.

All eyes then on the new Windows 8 and Office 2013.

cloud computing, microsoft

Microsoft Office 2013 SkyDrive Pro in action, with offline documents

1 Comment

Microsoft Office 2013, combined with Office 365 or the new SharePoint, introduces SkyDrive Pro. This is an area where users can store documents online, similar to the public SkyDrive, but as part of an organization’s SharePoint site or Office 365 team site.

One features which I was glad to see is the ability to store documents offline in a special Explorer folder. These are kept synchronized with the online storage.

Here is how this works with my preview Office 365 account. I log in to the online portal, and click the SkyDrive option in the menu.

image

I see my SkyDrive files.

image

At top right is a SYNC hyperlink. Click that, and this sets up synchronization to a special Explorer folder, which in my case is called SkyDrive @ Office Next. This is not just a shortcut to a network location. The documents remain there if you are working offline.

image

This excellent feature seems to depend on a new client called SkyDrive Pro Preview which has an icon in the notification area and also shows up in Task Manager.

image

If the SkyDrive Pro client is not installed and you attempt to sync your online files, the bad old SharePoint Workspace shows up instead. The consumer SkyDrive client will not do. SharePoint Workspace also supports offline files, but does not integrate with Explorer and is prone to go wrong.

Now here is the puzzle. Microsoft loaned me a Samsung Slate with Office 2013 pre-installed, and this has SkyDrive Pro. However it also has SharePoint Workspace, and the associated Office Upload Center, which duly went into a sulk when trying to sync my SkyDrive Pro files.

image

Clicking Resolve and entering my login details did nothing. However, when I clicked on the SkyDrive Pro icon instead, I got the new-style Office sign-in, following which everything worked.

image

A few puzzles then. Is the SkyDrive Pro client really new, or it is just a new wrapper for the bad old SharePoint Workspace?

Further, it seems that Microsoft has not yet cracked the problem whereby users sign in, tick the “Keep me signed in” option, but still get asked to sign in repeatedly.

.net, cloud computing, microsoft, professional, software development

Microsoft opens up Office 365 and Azure single sign-on for developers

Remember Passport and Hailstorm? Well here it comes again, kind-of, but in corporate-friendly form. It is called Windows Azure Active Directory, and is currently in Developer Preview:

Windows Azure AD provides software developers with a user centric cloud service for storing and managing user identities, coupled with a world class, secure & standards based authorization and authentication system. With support for .Net, Java, & PHP it can be used on all the major devices and platforms software developers use today.

The clearest explanation I can find is in John Shewchuk’s post on Reimagining Active Directory for the Social Enterprise. He makes the point that every Office 365 user is signing on to Microsoft’s cloud-hosted Active Directory. And here is the big deal:

The Windows Azure Active Directory SSO capability can be used by any application, from Microsoft or a third party running on any technology base. So if a user is signed in to one application and moves to another, the user doesn’t have to sign in again.

Organisations with on-premise Active Directory can use federation and synchronisation (Shewchuk fudges the distinction) so that you can get a single point of management as well as single sign-on between cloud and internal network.

Is this really new? I posted about Single sign-on from Active Directory to Windows Azure back in December 2010, and in fact I even got this working using my own on-premise AD to sign into an Azure app.

It seems though that Microsoft is working on both simplifying the programming, and adding integration with social networks. Here is where it gets to sound even more Hailstorm-like:

… we will look at enhancements to Windows Azure Active Directory and the programming model that enable developers to more easily create applications that work with consumer-oriented identities, integrate with social networks, and incorporate information in the directory into new application experiences.

Hailstorm failed because few trusted Microsoft to be the identity provider for the Internet. It is curious though: I am not sure that Facebook or Google are more well-trusted today, yet they are both used as identity providers by many third parties, especially Facebook. Spotify, for example, requires Facebook sign-in to create an account (an ugly feature).

Perhaps the key lesson is this. Once people are already hooked into a service, it is relatively easy to get them to extend it to third-parties. It is harder to get people to sign up for an all-encompassing internet identity service from scratch.

This is why Azure Active Directory will work where Hailstorm failed, though within a more limited context since nobody expects Microsoft to dominate today in the way it might have done back in 2001.