Re: Web Widgets, Where Art Thou?

In my opinion, the current spec's complexity in relation to its feature
goal, is high. This doesn't mean it was a bad spec or deficient, it could
be due to a number of factors: different assumptions about what widgets
should do, packaging choices that existed before web apps gained steam, or
a different focus on where and how widgets would be displayed.

I'd like to step back and formulate a strategy based on the progression and
growing prevalence of widgets on native mobile platforms, as well as how we
can align widgets with the packaging and distribution of web apps. The
paradigm of declaring/packaging widgets inside app packages is a beneficial
pairing that reduces the amount of code and management developers are
forced to think about, while taking advantage of natural synergies that
result from reusing a common base. I see widgets as a web page (perhaps the
same page as a "full" app, if the dev chooses) with near-zero additional,
cognitive overhead. Declaration via the app manifest is a huge piece - I'd
argue that this alone would realize a huge increase in developer
utilization.

Let's look at current consumer perception of widgets, and how the space is
evolving:

   - Widgets are commonplace on mobile platforms
   - In the view of consumers, search, discovery, and purchase/installation
   of widgets is now distinguishable from apps
   - Widgets remain a feature used primarily by savvy users, but new
   presentations will blur the lines between what a widget is - let's get
   ahead of this!

The last point here is important for the next generation of 'widgets'.
Widgets in the "statically-present-on-a-home-screen" incarnation are
currently the most recognizable form, but this is changing. Look at Google
Now - those cards, they're just widgets IMO.

Conclusions:

   - If users no longer distinguish between apps and widgets in practice, a
   common packaging vehicle makes sense.
   - We are seeing proactive, contextual presentation of data in
   widget-esque forms on Android and iOS (Moto X looks like it will introduce
   more of this). Under the proposed direction of widgets, developers need
   only know what context their widget is being evoked in, and how best to
   layout a UI for the intended display. (media queries for something like
   "blocks" - just an example, you get the idea)
   - I believe we should retool efforts in this area to focus on sharing
   the app packaging vehicle and reducing complexity to near-zero (besides
   things like widget-specific media queries)
   - If we want to make a splash, actively encourage implementers to add
   features based on widgets or widgets + apps (this is a feature we've
   discussed for future enhancement of the Firefox desktop experience)

I'd like to hear any additional feedback, and your thoughts on next steps.