Is the MS Ribbon/Office UI License worth worrying

Question

Imagine I want to create an application which is very similar to MS Word 2007, using C++ in VS2008 and the MFC Feature Pack. For the ribbon, there are 3 options available to me:

1. Use the ribbon from MFC Feature Pack without acquiring a license.
   Probably dodgy in the long run. You're all right until your product becomes a global success, at which point MS Legal send the heavies round. But could they really do anything about it?

2. Use the ribbon from MFC Feature Pack, but try to acquire a license.
   I believe that if I should try to register an Office UI License, the chances are that I would be turned down because it is a competing product:

   The license is available for applications on any platform, except for applications that compete directly with the five Office applications that currently have the new UI (Microsoft Word, Excel, PowerPoint, Outlook, and Access).

3. Use a 3rd party ribbon control.
   If I were to buy a license of the BCGControlBar Library for about £500 from BCGSoft -- whose ribbon bar is used by MS in the MFC Feature Pack -- then I could use the ribbon in my app with no problem.

I don't want to spend any money unless absolutely necessary. How about if I use option #1 until I get hassled about it, at which point I could ditch it and go for #3? Would it be too late?

Of course all the above is hypothetical... ;)

---

Note: I don't care about any patents or copyrights relating to the similarity between my product and Word, that's just an example. This question is only concerned with the ribbon licensing aspect.

Answer 1

If you're interested in exploring the third party component route, the article on CodeProject that I link below features a ribbon that looks a lot like Microsoft's and is freely available (though you'd have to credit the author).

A Professional Ribbon you will use (Now with orb!)

I haven't tried it but the article is highly rated (FWTW).

Answer 2

Even if you are using a Ribbon from a 3rd party control, isn't it the case that you still have to acquire the license to use it in your application?

Answer 3

Or don't use the Ribbon.

Knowing Microsoft it may not even make an appearance in the next version of Office...

Save your money (and reputation!)

Be creative, but also come up with stuff that your users want. The Ribbon is a design nightmare. Don't make the same mistake!

Answer 4

IMO, if you're saying that you probably would be specifically denied a license due to the product similarity, proceeding anyway without a license probably isn't going to turn out well for you if Microsoft ever catches wind of it.

I would go with Option 3 to be safe.

Answer 5

I realize you say that you don't care about the patents issue, but that's really the only issue. Even if you were to aquire a 3rd party ribbon control, Microsoft has the patents on it and can come after you for violating them. They've explicitly come out and said that people can use it for non-competing products.

The Office UI license restrictions are for the concept of the ribbon, not just MFC's specific implementation of it. See this page for more information.

Answer 6

I suppose what it really comes down to is whether I'm a direct competitor to MS. Any product can use the ribbon as long as it's not a "competing product", whatever that means.

In the context of my theoretical question, I would certainly be a competitor, and so I'd say it's too risky to use any kind of ribbon.

Of course in real life, whether or not you're a competitor isn't quite so black and white. I'd probably go with Option #2 for any product apart from OpenOffice.

---

EDIT
I watched this video and here's a quote from the MS lawyer in it:

"The license is not available for applications that have the same primary functionality as the 5 applications that currently have the ribbon in office. That's Word, Excel, Powerpoint, Outlook and Access."

The word primary gives the impression that a product containing a rich-text editor could have a ribbon bar on it, as long as the product's main purpose is different to Word. e.g. a version control system which allowed rich-text comments on checkin, would probably be OK. (I guess)