This is a topic that I’m interested in, having done some work on developer-facing services like Marketplace DevHub, Reviewer Tools and Payments Dashboard.
It would be good to provide a common design language that all of our developer services could draw from. Not necessarily in terms of visual look, but more in terms of interaction: how do you switch between services, where do you access metrics, can you add a new service in one click, does FxA sign in persist across services? Ideally, the same sort of items should be accessed from the same place, so developers don’t have to relearn the interface over and over again. But then there’s a question of audience. How many Mozilla services do our developers typically use? The more services you use, the more useful a common design language will be. There are other interesting questions to explore here. On Sat, Oct 10, 2015 at 1:48 PM, William Maggs <[email protected]> wrote: > https://developers.google.com/speed/pagespeed/insights/?url=mozilla.com > > On Fri, Oct 9, 2015 at 5:42 PM, Axel Kratel <[email protected]> wrote: > >> This is one of the most popular Google developer service: >> https://developers.google.com/speed/pagespeed/insights/ >> >> You might want to check what looks like a really extensive offering from >> Google. Some of it is server side, but at the very least we should have >> similar services for web pages. >> >> On Fri, Oct 9, 2015 at 4:00 PM, William Maggs <[email protected]> wrote: >> >>> Andy, >>> >>> Perhaps on top of these near-term needs we can also bring into the >>> discussion developer services you and Laura have discussed at various >>> times, including: >>> >>> compatibility >>> crash tests >>> security >>> >>> Bill >>> >>> On Fri, Oct 9, 2015 at 3:37 PM, Christopher Karlof <[email protected]> >>> wrote: >>> >>>> Hi Andy, >>>> >>>> One topic that has started to come up more frequently is the notion of >>>> a developer dashboard for Firefox developer services. We now have at least >>>> a few current and future use cases: >>>> >>>> 1) Add-on management and metrics >>>> 2) Push notification management and metrics >>>> 3) FxA Oauth relier management and metrics >>>> >>>> I think we’re going to need to start figuring this out. I don’t feel >>>> we’re adequately staffed for this ATM, and I feel it would be useful to >>>> start thinking about this soon in advance of our 2016 planning. Please look >>>> for a meeting invite for us to have some initial discussions. >>>> >>>> thanks, >>>> -chris >>>> >>>> >>> >> > > _______________________________________________ > Dev-fxacct mailing list > [email protected] > https://mail.mozilla.org/listinfo/dev-fxacct > >
_______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
