← Back to team overview

unity-design team mailing list archive

Re: webapps and the sound menu


A bit late, but I would like to add my own thoughts to this: I absolutely
agree with Mr. Bicha about web-apps in 12.10 (having finally downloaded it
to test the new toolkit). They are a bit of a mess. And I, as a seasoned
user, find their launcher behavior almost indecipherable given the context.
Am I just visiting a fancy browser window or am I actually using something
that is supposed to be its own thing? And getting them to install was a
hassle and no feedback for when it didn't work... Tried to install GMail
three times before it worked with no feedback as to why it failed the
previous times. And plus one to the completely chromeless argument.

Pandora just suddenly showed in my sound menu unexpectedly as well. I guess
I'm mostly trying to say what Jeremy said: a good start but far from

On Thu, Dec 13, 2012 at 10:43 AM, Jeremy Bicha <jbicha@xxxxxxxxxx> wrote:

> On 13 December 2012 09:57, Alex Launi <alex.launi@xxxxxxxxxxxxx> wrote:
> > Like any software, webapps will always be incomplete. The implementation
> > of the integration was not poor (at least I don't like to think so), but
> > there were features that got de-scoped for 12.10. Chromeless browsing in
> > Firefox was one item. There is a chromeless mode for Chromium, it exists
> > in 12.10. Chromeless mode does not, however, prevent you from having
> > multiple tabs. You could have 10 instances of Facebook, or YouTube in
> > one of these chromeless browser windows. Chromeless mode is accessed
> > when you have a launcher icon and launch a new instance of a webapp from
> > it. Integration should always work from the browser though, how else
> > would you find that a webapp exists?
> I think that Firefox or Chromium should prompt for installing webapps
> like it does.
> Without chromeless mode, I (as a user) see webapps as being just fancy
> bookmarks that may also have notification or indicator support. I
> think chromeless mode *should* prevent you from opening multiple tabs
> because a standalone webapp is not a full-featured web browser (that's
> just the backend, an implementation detail). Links to external domains
> (not white-listed in the particular webapp config) should open in your
> regular web browser because a webapp should act like a native app as
> much as possible.
> For me, proper chromeless mode is an essential part of webapps so
> that's why I was disappointed with 12.10's implementation (I don't
> mean to hurt the feelings of those who spent months working on the
> feature; I expected that that feature would instead land in 13.04).
> Jeremy
> --
> Mailing list: https://launchpad.net/~unity-design
> Post to     : unity-design@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~unity-design
> More help   : https://help.launchpad.net/ListHelp

Follow ups