Notes on Web Weaver UX

This post is outlines some of my thoughts on the Web Weaver user experience. This post also doubles as my vision for what the newly announced Firefox Personas could and should become. Consider this the first of many iterations.

Inspirations:

Scenario:

You and your mom are in the witness protection program because you’re on the run from.. the mob. You are starting your lives from scratch. You and your mom have new identities and a new computer! It’s time to set it up.

First you install your favorite open source web browser. Once installed, you click on it and are faced with the initial run sequence.

Thx for installing Mozilla Firefox! Would you like to login with an existing Persona  or create a new one?

You click the “Create new Persona” button.

Would you like to use the Wizard? (No)

—-

Where would you like to deploy your Persona? Options:

  • Mozilla.org
  • Google App Engine
  • Windows Azure
  • Appfog
  • Rackspace
  • Amazon EC2
  • Heroku (CLICK!)

—-

Heroku requires an email address to (blah blah blah.. don’t have one yet. Let’s hit back and click on Mozilla.org. No, wait.. Appfog!)

—-

Installing…

—-

Name: (redacted)

Security: Create Password (*************)

Repeat Password (oh, alright..)

—-

Would you like to link your Persona with this web browser? (yes!)

—-

Would you like to sync your personal data with this web browser? (uhh.. sure.)

—-

Congratulations! Here is your Persona’s public facing url: http://redacted.appfog.com/

Visit from a linked web browser to access your data and modify your settings.

Would you like to install some apps from the Mozilla Marketplace? (no)

—-

(Back to home page; http://redacted.appfog.com/home)

Now it’s your mom’s turn. You log out of Firefox, and sit your mom down at the computer.

You click the “Create new Persona” button.

Would you like to use the Wizard? (She clicks yes)

Name: (Not your real name!)

Security: Create Password (*   *   *       *   *       *)

Repeat Password (*   * *        *   **        *)

Congratulations! Here is your Persona’s public facing url: http://persona.mozilla.com/redacted

Visit from a linked web browser to access your data and modify your settings.

We have taken the liberty of installing a few default applications. They are available on your app dashboard.

Would you like to install some apps from the Mozilla Marketplace? (yes!)

And.. she’s off to a fresh new (and hopefully secure) computing experience made seamless by her Mozilla hosted Web Weaver.

Some additional notes:
  • Your mom uses a Boot2Gecko based phone. You use Android. In both cases, your Web Weaver should be the only accounts you need to login to your phones in order to sync your data.
  • Your Web Weaver is your identity server. BrowserID, OpenID, WebID, etc etc.. whatever popular convention dictates is served up.
  • Because your Web Weaver serves up a public page, that page should be an installable web app. That page also represents you. Hello decentralized social network! (Thank you Mozilla!)
  • Because you are now an app, you have an API that can be extended by any app you install. Your Web Weaver manages your API URI scheme. Think http://redacted.appfog.com/home/api/facebook/post and http://persona.mozilla.com/redacted/api/pinterest/get
  • Alternatively, any and all services provided by the Web Weaver can be delegated. Best practice for app development moving forward should require applications ask for service delegation back to themselves if they want to have a ‘traditional’ web app architecture circa 2006-2011.
  • People are now first class citizens of the web.
  • By combining Mozilla Persona and Firefox Sync together into a single project with Apps conventions tying it up into a pretty bow, the Apps initiative essentially moves the web from object-orientated development toward Agent-oriented development. Web Weavers+Web Browsers=User Agent, Apps=Software Agents
  • Oh look! User Agents + Software Agents + Hardware Agents = distributed Social Graph, distributed Application Graph + distributed Internet of Things graph.
  • What is the UX around group identity creation and management?
  • What are the key services a Web Weaver needs to have by default? (Notifications, Web Intents/Activities sync, Settings management front-end.. etc)

I’ve identified the Web Weaver as the missing requisite piece to solving global scale problems within the urgent timeframes we face. It is therefore my intent to make sure that this product class is fully defined, specified (specificationified?) and in some form shipped by the end of this year.

28. March 2012 by CaptainCalliope
Categories: Uncategorized | 1 comment

  • http://captaincalliope.net/ Captain Lyre Calliope

    “It is therefore my intent to make sure that this product class is fully
    defined, specified (specificationified?) and in some form shipped by the
    end of this year.”

    So embarrassing.. and betrays a complete lack of grounding in reality. Who is this guy?