Task Launcher - mockups
Marco Martin
notmart at gmail.com
Thu Jan 31 12:03:39 UTC 2013
Aaanyways, to expose a bit how i tought things to be (and wrote stuff
accordingly):
* applications may be basically of 3 categories: "browsers", "viewers/editors
of a single thing" and what doesn't really fall in those categories (that is
pretty much 99% of mobile apps, not only games but the typical half toy half
utility of the typical mobile app)
* in the top menu there would be just links to "browsers", like web, files,
music, books.. and one single "creator" application that would allow to create
files/stuff (or could be confined as a function in the corresponding browser,
note the pim applications pretty much match 1:1 this), and it must be quite
strict for an application to "qualify" for being elected in the top menu
* simple applications to view just one kind of thing wouldn't be in the menu,
but only invoked by opening the proper type of thing (like okular active,
calligra stuff, the image viewer, probably videos needs one as well)
* the "rest" would have a browser of its own, an application browser that has
categories, tags, search and all that, that makes finding an application easy
no matter how many are installed... probably not super fast to start when you
already know what to start, but that's what linking it to an activity is for.
in general, applications to fit in the workflow would be "recommended" to be
as small tools as possible to make one and only one thing, otherwise they go
in the big catalog, the top area stays an icon grid, nice, simple and
symmetric but with even less icons than now.
Cheers,
Marco Martin
More information about the Active
mailing list