What's "King" These Days?

People always can reasons to debate whether "content," "distribution" or "context" is king. Perhaps nobody yet is seriously arguing that "location" or "presence" or "social connections" or "mobility" is king, but one can predict that somebody will make those arguments.

One of the debates which slowly is growing, though, is over "openness" and "curated" approaches to end user experience. It would be too easy to say Apple is the foremost proponent of curation ("closed") while Android, Chrome and Firefox are examples of openness.

It might be more accurate to say the trend to curation is growing, across all platforms. You might think of curation as a culling, optimizing or editing process, where apps and software are optimized and filtered. Apple always has done this to optimize end user experience. But app stores, both mobile and soon Web app stores, also are curated environments, to a greater or lesser extent.

In Mozilla's view, for example, the open Web is the way to create rich applications, while Apple takes the opposite approach. In Apple's case, the company plans to create a new Mac Apps Store containing software expressly optimized for Apple devices and the Mac OS X operating system.

Apple plans to curate significantly, rejecting buggy apps, betas, apps built with Java, apps with Easter eggs, apps that aggregate content, apps that duplicate Apple's own apps, apps that contain pornography, violence, promote drinking and drugs, for example.

Mozilla Foundation is taking an entirely different approach for its new "OPen Web Apps" store. Designed around a "use any browser" approach, the idea is create a store that allows creation of Web apps that work in any modern desktop or mobile browser (Firefox 3.6 and later, Firefox for mobile, Internet Explorer 8, Chrome 6, Safari 5, Opera 10 and WebKit mobile).

Consider the Mozilla initiative an example of the "write once, run many" approach to software. In Mozilla's vision, apps are designed to run independently of operating system or hardware. See http://blog.mozilla.com/blog/2010/10/19/prototype-of-an-open-web-app-ecosystem/ for more detail.

Open Web Apps will use HTML, CSS and JavaScript and will supoprt installation to a mobile or desktop Web browser, or to a native OS desktop or mobile home screen.

Open Web Apps will use existing identity systems like OpenID and support portable purchases, meaning that an app purchased for one browser works in other browsers, and across multiple desktop and mobile platforms without repurchase. Think iTunes and you have an example of the difference between the Mozilla and Apple approaches.

Open Web Apps will support access to one or more advanced or privacy-sensitive capabilities such as geolocation on a user opt-in basis.

In Mozilla's view, apps must be distributed by developers directly to users without any gatekeeper, and available through multiple stores, allowing stores to compete on customer service, price, policies, app discoverability, ratings, reviews and other attributes.

Open Web Apps will be able to receive notifications from the cloud, and support deep search across apps. In other words, apps can implement an interface that enables the app container (generally the Web browser) to provide the user with a cross-app search experience that links deeply into any app that can satisfy the search.

In essence, the debate over curated and open approaches is a preference for, or against, gatekeepers. But the emergence of new app stores, already announced by Google, Apple and Mozilla, should change the software development business in some key ways. Web apps should grow in popularity, and make more rapid development of lower-cost apps and lower-volume apps available in substantial quantity, as app store publishing will cost a lot less than traditional shrink-wrapped apps store in physical and online retail stores. See http://www.readwriteweb.com/cloud/2010/10/web-app-stores-how-they-compar.php for more detail.

About the only safe statement is that all the traditional arguments about openness and curated approaches, including the issue of gatekeepers, are going to heat up again as the web app store trend gets established.

Watch a Mozilla video about the new Web Apps Store here: http://videos-cdn.mozilla.net/labs/openwebapps/openwebapps.webm

Will Firefox Mobile Displace App Stores?

Right now mobile apps are hard to develop if what one wants is access to the widest range of browser-equipped smartphones and application stores. Basically, each application has to be re-coded for each mobile operating system.

Mozilla.org thinks it has a better solution: write apps directly for the Firefox mobile browser, using HTML5, CSS and JavaScript, and be done with it.

Firefox Mobile (known informally as "Fennec") will launch for Nokia's N900 handset "soon," with versions for Windows Mobile and Android planned for 2010. In developing its new mobile browser, Mozilla.org is trying to replicate and preserve as much of the current user experience as possible, a sore point with some users.

Firefox for mmobile phones will include "The Awesome Bar" that searches a user's history, bookmarks and tags, allowing users to go to their favorite sites instantly by auto-completing entries.

Firefox preferences, history, and bookmarks can be shared between a desktop and mobile, providing a convenient way to sync important elements of the Web experience. The mobile browser will be continually synchronised with the PC.

If a user starts typing a specific address, and the user has visited that site before, the site will pop up, Mozilla.org says.

Tabs will allow users to browse multiple sites at once and one-touch bookmarking will allow users to quickly organize and add new sites. If a user is working on a PC with multiple tabs open, and then wants to resume on a mobile, the tabs will be available on Firefox Mobile when the user opens it up.

Also, users will be able to "add on" new widgets for the browser itself, something difficult-to-impossible to do at the moment.

For developers, the ability to create apps directly for the Firefox browser will simplify the development process, if not the business model. Developers who simply want people to use an applicatons will find the browser model quite attractive.

Developers who want to create a "for fee" business model might have to stick with the application stores, though, as the billing process will be an issue.

Writing for Firefox should make easier the task of integrating geolocation, camera and calling features of the phone.

Firefox Mobile will offer the fastest Javascript engine of any mobile browser, Mozilla.org says.

"Anyone who knows JavaScript and HTML can develop a great app without having to learn a specific mobile platform," says Jay Sullivan, Mozilla.org VP.

AOL Shuts Down Netscape

In what might be seen as a successful open source transition, AOL is shutting down its support efforts for the Netscape browser and encouraging Netscape users to switch to Firefox, the Mozilla-powered browser.

AOL acquired Netscape Communications Corporation in 1999. By 2000 AOL had launched the Netscape Communicator Web suite, otherwise known as Mozilla. The Netscape 6 browser, the first Mozilla-based, Netscape-branded browser in 2003 was supported by the independent Mozilla Foundation.

AOL was a major source of support for the Mozilla Foundation and the company continued to develop versions of the Netscape browser based on the work of the foundation. Perhaps AOL has succeeded.

By most estimate Microsoft Explorer holds about 66 percent market share while Mozilla has about 25 percent. Netscape currently has one percent or so share.

Firefox Goes Cloud Computing

Firefox has taken a step towards cloud computing by releasing the first version of Weave, a way to blend of the desktop and the Web through deeper integration of the browser with online services.

Basically, Weave pushes browser metadata (bookmarks, history, customizations into the cloud so it can be retrieved and used on any machine. The metadata is transparently reflected everywhere an individual gets online. Weave also will provide a basic framework for easily sharing and delegating access to this metadata to friends, family and third-parties. And it's a Mozilla product so there will application program interfaces for developers.

Mozilla intends to provide the infrastructure and an consistent model for how a user can open up their browser metadata to friends and third-party applications.