ubuntu-phone team mailing list archive

[Jamie Strandboge <jamie@xxxxxxxxxxxxx>]

On 08/30/2015 10:01 AM, Michi Henning wrote:
> Scopes, by design, are information providers, and interaction with them is
> deliberately kept to a minimum. In return, we get scopes that are stateless,
> take up minimal resources, don't need access to a display surface, and start up
> in a fraction of a second.
> 
> The way to make scopes interactive to bundle them with an app. The scope
> surfaces content and, when more sophisticated interactions are required, the
> scope can notify the app, which then takes over for the fancy stuff.
> 
I've actually found that a well-written and designed scope can be quite useful.
Those that aren't tend to not surface enough information or feel like little
more than a google search with 'site:example.com'.

The one thing I'd like to see is better use of caching. For example, I think the
Today aggregator scope is great but it sometimes goes blank to refresh
everything and then the aggregated scopes' content trickles in one at a time,
which can be jarring to the user. I think it would be better to show the
previously displayed content with a very small and tasteful indication that each
aggregated scope in the process of reloading and when the updated content is
available for the aggregated scope, reload it in place. I imagine this is
probably also useful for leaf scopes-- show the last content and then replace
the bits that are updated.

(I've been wanting to bring this up for a little while but wasn't sure if this
was a bug, intended behavior, on a todo, an implementation limitation, etc. I
figured I'd glom onto a thread that said 'Future of Scopes' for this :)

-- 
Jamie Strandboge                 http://www.ubuntu.com/

Attachment: signature.asc
Description: OpenPGP digital signature