Notifications and lock screen seem like really fertile ground for great improvements. They and statusbar share the issue that there is quickly too much stuff to show and we have to prioritize somehow. Perhaps we could expose a simple api with a means of weighting. Weighting probably needs to be contextual as priorities change with use.
I think targeting another form factor is a great exercise for informing the roles the system UI has so we can start to refine and formalize. Are there learnings from the tv codebase? I imagine we'll want to start decoupling and moving towards a more a la cart arrangement where we can pick and mix and build on what we have without starting from scratch with each different device type. /Sam On Tue, Nov 24, 2015 at 9:58 AM, Sam Foster <[email protected]> wrote: > As we get started on 2.6, it would be good to hear more about how the UI > facilities the system app provides are meeting requirements. If you have > pet peeves, long standing issues, future thoughts - lets get them > captured. I know we have many bugs already in bugzilla (and we'll try to > winnow them down) but some are old enough its hard to know if they are > still relevant. Also we have ideas being generated by the Alopex > initiative. But as developers writing apps on this platform - and > dogfooders - what do you think needs improving? > > Potential topics: > * Lock screen > * Utility tray, > * Toasters and notifications > * Edge swipe > * Task Manager > * App transitions > * Window management > * Status bar > * Dialogs > * App chrome > > > Does the way the apps/content interact with the system make sense and meet > all your present needs? > > thanks, > /Sam > > >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
