devicemap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Werner Keil <werner.k...@gmail.com>
Subject Re: Promoting devicemap strengths
Date Mon, 22 Dec 2014 13:54:53 GMT
Yep, at the moment only "data" is out there;-)

On Mon, Dec 22, 2014 at 2:29 PM, Volkan YAZICI <volkan.yazici@gmail.com>
wrote:

> One more note: Without devicemap-client artifact available, the entire
> project would make no sense from the point of view of a Java developer,
> FYI. We need to get that released ASAP.
>
> On Fri, Dec 19, 2014 at 10:34 PM, Reza Naghibi <
> reza.naghibi@yahoo.com.invalid> wrote:
>
> > So now that our project is picking up, I would like to better market the
> > strengths of this project. For now, im thinking of a blurb on the
> homepage.
> > Here is what I have so far:
> >
> > -We are the only truly open source DDR out there. Our data and API are
> > completely free and open. We have the backing of the Apache Software
> > Foundation.
> > -We have a state of the art classification API. Unlike other APIs which
> > classify and detect devices using a mix of code, parsing, and regex, we
> are
> > purely pattern driven. Our classification API is domain independent.
> > -With our upcoming 2.0 release, we will be the the only DDR which allows
> > devices to be classified using 3 independent and unrelated aspects:
> device,
> > operating system, and browser.
> > -We are a great choice for HTTP log analysis. DeviceMap can easily
> > classify your traffic logs to better understand your user device
> > composition.
> >
> > Thoughts? Additions? Better wording? Also, what about browsermap? What
> can
> > we say about that aspect of this project?
> >
> > Also, I just want to add that I think realtime HTTP device classification
> > is just as relevant as ever. Companies are always asking for it. Also,
> from
> > first hand experience, I am still seeing large complex webapps fail when
> > trying to be 100% css responsive. These projects would have greatly
> > benefited from simple backend device templating and/or user choice of
> > templating. Ex: Do you want to view our Lite or Desktop site?
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message