The pagespeed page is neat and all, but I think that pages like
http://term.ie/oauth/example/client.php
or
https://developers.google.com/oauthplayground/
are closer to what we need to offer.

When I think "Mozilla Developer Dashboard", I'm thinking something very
different. We have a number of services that may be a tad "tweaky" to
use, and sadly tend to be more on the "It either works or it doesn't" end.

To pick on my own service rather than someone else's, Push is in theory
simple (run a bit of JS, get a URL, send stuff to URL to get an even
back on the JS), but there's an awfully big "black box" around things.
* Did I PUT/POST correctly?
* Did the message make it out of the system only to be eaten by the client?
* Did I properly encrypt the data portion? (Yeah, that's not going to be
fun for folks.)
* Have I run over quota for events?

Having a dashboard to help answer questions for folks who aren't
intimately familiar with the code and have little interest in digging
into that particular morass would be useful. It's often difficult for
creators of a service to remember, but we're providing a solution to a
much, much larger problem and the less folks have to think about our
services, the happier they'll be to use them.

On 10/9/2015 5:48 PM, William Maggs wrote:
> https://developers.google.com/speed/pagespeed/insights/?url=mozilla.com
>
> On Fri, Oct 9, 2015 at 5:42 PM, Axel Kratel <[email protected]
> <mailto:[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]
>     <mailto:[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] <mailto:[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

Reply via email to