DareBoost

[Luke Crouch]

mdn-services,

David Walsh showed me this dareboost service which has, IMO, the kind of
report consolidation UI we could aspire to with our various MDN services'
reports.

https://www.dareboost.com/en/report/54fef22ee4b0c0149cc17e60

I.e., a single report covering things ranging from accessibility,
standards, compatibility, to security, etc.

And a similar daily/weekly scan, analyze, and report cycle.

-L

[John Karahalis]

Keeping this intentionally brief to start some discussion...

Does this mean there are more red oceans than we initially thought? Do our
plans still offer services that users can't already get elsewhere?

> _______________________________________________
> mdn-services mailing list
> mdn-se...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/mdn-services
>



--
John Karahalis
Mozilla
openjck.com

[Justin Crawford]

I think so.

Our survey results (which I would call "market validation of a problem to
be solved") indicate that professional web developers are motivated (for
example, by their professional integrity) to make websites that are
compatible, secure and accessible. But, for example, with compatibility,
developers who don't currently use a service say they manually test across
browsers or just use a library and hope it works across browsers. They say
testing across browsers is hard. They say they don't use existing services
for this because existing services don't fit into their workflows or are
hard to learn. [0]

So there is an opportunity, particularly if we make tools that are easier
to integrate into a developer workflow (which to me means experimenting
with new form factors that go beyond, "paste a URL into this website and
get a report back!").

There are tons of services out there and we'll see more. Our potential
customers are pretty good at scratching their own itches. But we have some
unfair advantages -- scale and authority are high on the list.

We are very much in experiment mode -- startup mode -- which means we're
searching for a successful model that really resonates with a market we
think exists. We have to be OK with the idea that even after experimenting,
we won't find that model, and we have to help our colleagues understand why
failing to find it is OK. Good for us, even. [1]

[0]
http://qsurvey.mozilla.com/Reportsview?key=28049-3800329-d4947bf1c72e37b4d1d06674e482106e&mode=html
[1]
http://steveblank.com/2015/03/11/fear-of-failure-and-lack-of-speed-in-a-large-corporation/


Justin Crawford
Product Manager, MDN
hoos...@mozilla.com

On Wed, Mar 11, 2015 at 9:01 AM, John Karahalis <jkara...@mozilla.com>
wrote:

[Luke Crouch]

+1 everything Justin said.

The great thing about being MDN is that we want to help web developers'
write secure, compatible, accessible code. Period. I.e., we're not some
"Damn, they stole our idea!" startup out to make a name for ourselves (we
already have one), nor are we looking for a lucrative exit.

When we find other developer tools & services, we evaluate if they help web
developers. If so, we can partner with them to add some of our scale and
authority to make their offerings more accessible to more developers.

And we focus our own work to more specific areas and models that others may
not be trying.

-L

On Wed, Mar 11, 2015 at 10:55 AM, Justin Crawford <hoos...@mozilla.com>
wrote: