While a renewed search deal between Google and Mozilla is welcome news to millions of Firefox users, Mozilla has three big ideas for 2012 and beyond that will see it competing much more with Google, Facebook and Apple. Here’s why you should be cheering Mozilla on.

Biting the hand that feeds it?
As InfoWorld’s Woody Leonhard writes, it was in Google’s best interests to prevent Microsoft’s Bing from becoming the default search provider in Firefox. As much as Mozilla relies on Google for 80 percent plus of its revenue, so too does Google rely on the search traffic from millions of Firefox users. While Mozilla’s blog post about the recently signed deal espouses a mutually beneficial agreement, its difficult to believe that the relationship is anything but strained between Google and Mozilla.

However, that relationship is going to get a lot more tenuous if Mozilla is able to make progress on three key areas laid out by Mozilla’s David Aacher.

Mozilla and Firefox became household names through the browser wars, particularly against Microsoft’s Internet Explorer, but mainly as a proponent of open standards and user rights on the web. Ascher writes: “In the case of the browser wars, the outcome has been pretty good for society, if slower than we’d have liked: standards have evolved, browsers got better and faster, and websites got more interesting.”

But now, Mozilla feels it’s time to look beyond the browser as the main front in it’s mission to safeguard the future of web for the people. Mozilla is also investing in an open stack for hardware OEMs, user-centric identity on the web and tools for building and running apps. These initiatives add to the value of Firefox from a user standpoint, but are being developed in parallel. Additionally, the latter two initiatives are applicable to other browsers also.

A truly open alternative to Android
The first initiative, named Boot to Gecko aims use open web technologies to deliver a runtime and underlying operating system for desktop and mobile applications. If this sounds like Android or Chrome OS, it should. Boot to Gecko is using some of the same lower level building blocks that Android uses, such as the Linux kernel and libusb. The team explains this choice was made to reduce the burden on device makers and OEMs who will be faced with certifying Boot to Gecko on new hardware. While some building blocks are shared, Boot to Gecko is not based on Android and will not run Android applications.

If Mozilla can successfully execute on initiative number 3 below, Boot to Gecko will be difficult for OEMs to ignore. There is a lot more work for Mozilla to do before Boot to Gecko can attract the attention of Android device manufacturers. However, OEMs and users will benefit from serious open source competition to Android.

User controlled identity
The second initiative, currently named BrowserID, although Mozilla is looking for a different name, addresses the need for users to regain control over their identity and sharing of personal information on the web.

BrowserID aims to become the open alternative to Facebook Connect and Google username on Google’s far reaching web properties. With BrowserID, Mozilla has built a user centric identity system that works in all modern browsers and will make the protocol available for other browser vendors to use. Ascher explains:

“For Mozilla devs, this is a bit shocking, as we’re not starting by putting a feature in Firefox first (although we sure hope that Firefox will implement BrowserID before the others!). While I love Firefox, this makes me happy, because in my mind, Mozilla is about making the internet work better for everyone, not just Firefox users, and in this case being browser-neutral is the right strategic play.”

The notion of making the web better for everyone, not just Firefox users, is one I’ve not picked up on until now. But I completely agree with Ascher. Few can argue that even Internet Explorer users are benefiting from Firefox’s efforts and Microsoft’s response.

If Mozilla is successful with BroswerID, which is certainly possible as developers increasingly grow weary of their reliance on Facebook or Google, users will get back control over their identity and information without having to sacrifice a personalized web experience.

Apps, if you can’t beat them, join them
Finally, Mozilla is addressing the “app-ifcation” of the web, not by fighting the trend it as may seem reasonable for a browser vendor, but by guiding how these apps are built, found, paid for and installed.

Mozilla’s Apps initiative aims to make web technologies the basis of building applications that can run across devices. Mozilla also wants to introduce a standard for application purchasing and installation that would allow users to consume applications from multiple app stores without restrictions. This initiative undoubtedly goes after the Apple App Store and Android Marketplace.

It would be interesting if Mozilla were to partner with Microsoft on this initiative as Microsoft builds out its app store.

Success isn’t guaranteed, but Mozilla knows about tough fights
Whether Mozilla can execute against all three of these initiatives while maintaining its efforts in the still important browser war is an open question. As a user, even if one of these three initiatives are successful, we’ll all be better off.

While Mozilla will face a lot of resistance on this front from the likes of Google, Facebook and Apple, fighting an uphill battle isn’t new territory for Mozilla.

should state: “The postings on this site are my own and don’t necessarily represent IBM’s positions, strategies, or opinions.

It is funny how Matt and I can read the same article and come up with different conclusions.

I read this article and thought that Adobe’s entry into the Office applications market has little to do with OSS or Open Standards, so no need to blog about it here.

Matt says:

“The only thing better would be if Adobe, Apple, and OpenOffice could get together….In fact, don’t you think that it makes a lot of sense for Apple to acquire Adobe, given the similar corporate mentalities/competencies? Me, too.)”

Apple, likely the most closed vendor on the planet is supposed to be the “last great hope against Microsoft’s Office franchise”? Maybe Matt is down to half a glass of OSS Kool-aid daily and doesn’t care if he’s supporting a Traditional or OSS vendor in the “good fight against Microsoft’s hegemony”.

All kidding aside, I can’t wait to see what Adobe has in this market. I am a MS Office user. I tried OpenOffice and even Google Docs, but neither seemed to fit my needs vs. the tradeoffs to switch. I wonder if the problem is that OpenOffice and Google Docs feel like they were designed by developers. On the other hand, Adobe products feel like they were designed by designers. Watching an Adobe AIR demo or app created with AIR most of us think “ooh, ahh” (Note: I hate reading text on most Flash websites – I just needed to say that).

As Cote says in the Wired article:

“It’s not a technical question, it’s a cultural question,…All the geeks and everyone like myself would love to play around with an Office competitor from Adobe to see what that would be like. But when I talk to normal office workers who use Microsoft Office, they don’t get all warm and tingly like I do with the prospect of different office software….People who use Microsoft Office are into using Microsoft Office.”

How true.

It’ll be interesting to see what Adobe does here. Putting on my strategy hat: Entering the Office Apps market is only a step towards their broader goal to drive extensive adoption of Flex and AIR. So, look for an open API that allows designers/developers/ISVs/customers to extend the Adobe Office suite. By expanding the reach of Flex & AIR, Adobe can sell tools (not just IDEs) to designers & developers that want to create AIR apps. In essence, AIR (and Flash before it) is a runtime environment just like the Java JDK and MS CLR. It just so happens that AIR is for client-side apps (vs. predominately server-side for JDK) that look sweet and deliver ease of use vs. traditional client-side apps (i.e. predominately MS CLR). As this occurs, I suspect that customers and vendors will start looking for a standards body around the AIR runtime technologies. So, maybe there is a Standards tie to this story after all :-)