On Nov 10, 2014, at 2:34 PM, Andres Galante <agalante(a)redhat.com&gt; wrote: Hi, I am starting to redesign auroras.org. I would like your help to understand better the product and our user.

Who is the developer that uses Aerogear? is it a hardcore developer, or someone that is looking for a ready made solution? I understand that we have 3 products, Core, Push and security. What is our main product? What is a user he looking for when he gets to Aerogear? How can Aerogear help him? At this point I would also like to build a “design persona” to have a coherent identity, voice and styles throughout our line. If aerogear was a person, who would it be? what voice does it have, color, typography, etc. With this done we will make sure our websites, demos and consoles speak the same language. Thanks _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

Ahoy my friend, answers inline. (my personal opinion) On Mon, Nov 10, 2014 at 5:34 PM, Andres Galante <agalante(a)redhat.com&gt; wrote: > Hi, I am starting to redesign auroras.org. I would like your help to > understand better the product and our user. > > Who is the developer that uses Aerogear? is it a hardcore developer, or > someone that is looking for a ready made solution? > I think both. We have JavaScript, iOS, Android, Cordova, Firefox and JavaEE developers. For example, some Java EE developers don't care about JS and they might be looking for a ready made solution (In this situation, AeroGear with Forge or JBDS is a good fit). At the same time you have JS developers for example like Lukas or Luke, which are familiar with Java EE, but they are more like a hardcore developer and they just want to make use of libraries. Some devs will stick make use of tools, others to just our libraries.

> I understand that we have 3 products, Core, Push and security. What is > our main product? > At the moment, I would say that Push is the main AeroGear focus. Although AG is more than just Push. We provide libraries willing to make developer's life easy so topics like: Push, Security (cryptography, OAuth2 libraries, 2 factor), data sync, geo-fencing, offline support...and more crazy and dirty things you could possible imagine with fancy devices — probably AG will be there.

> What is a user he looking for when he gets to Aerogear? How can Aerogear > help him? > Most of the developers (others can correct me if I'm wrong) are looking to boost their productivity. Let's think about something very complex like cryptography or OAuth2, is really hard to newcomers to grok into RFCs and implement it. Most part of the time people just want to connect their apps to Facebook, Twitter, <put your favorite social network here>. People don't have time and sometimes patience to read RFCs and start from scratch (because it's boring) I think this is where AeroGear comes into place. If you talk to Passos, he will give to you details about reducing 25% of the hard work on Android with AeroGear.

> > At this point I would also like to build a “design persona” to have a > coherent identity, voice and styles throughout our line. If aerogear was a > person, who would it be? what voice does it have, color, typography, etc. > Amazing. Not sure if AeroGear would be a person, but to me is more like Skipper ( http://img3.wikia.nocookie.net/__cb20130327234948/pixar/images/7/70/Plane... )

> With this done we will make sure our websites, demos and consoles speak > the same language. > > Thanks > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev -- -- "The measure of a man is what he does with power" - Plato - @abstractj - Volenti Nihil Difficile _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

I would also highlight importance of supporting developers coming from different platforms (Java on Android, ObjC/Swift on iOS, and plain JavaScript, JavaScript in Cordova). I know that it might be hard to combine with a concept of feature-oriented pages, but I imagine we could allow at least color- or icon-based highlights for different platforms (icon of Droid - lightblue code sample background, icon of apple - silver background, JS logo light-yellow background, Cordova logo - pink background!) + I would even consider a something like select box in top navbar that allows to filter out platform specific information. ;-) On Tue, Nov 11, 2014 at 8:05 AM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > > > On Tue, Nov 11, 2014 at 6:04 AM, Bruno Oliveira <bruno(a)abstractj.org&gt; > wrote: > >> Ahoy my friend, answers inline. (my personal opinion) >> >> On Mon, Nov 10, 2014 at 5:34 PM, Andres Galante <agalante(a)redhat.com&gt; >> wrote: >> >>> Hi, I am starting to redesign auroras.org. I would like your help to >>> understand better the product and our user. >>> >>> Who is the developer that uses Aerogear? is it a hardcore developer, or >>> someone that is looking for a ready made solution? >>> >> >> I think both. We have JavaScript, iOS, Android, Cordova, Firefox and >> JavaEE developers. For example, some Java EE developers don't care about JS >> and they might be looking for a ready made solution (In this situation, >> AeroGear with Forge or JBDS is a good fit). >> >> At the same time you have JS developers for example like Lukas or Luke, >> which are familiar with Java EE, but they are more like a hardcore >> developer and they just want to make use of libraries. Some devs will stick >> make use of tools, others to just our libraries. >> > > +1 both are 'target' > > >> >> >>> I understand that we have 3 products, Core, Push and security. What is >>> our main product? >>> >> >> At the moment, I would say that Push is the main AeroGear focus. >> Although AG is more than just Push. We provide libraries willing to make >> developer's life easy so topics like: Push, Security (cryptography, OAuth2 >> libraries, 2 factor), data sync, geo-fencing, offline support...and more >> crazy and dirty things you could possible imagine with fancy devices — >> probably AG will be there. >> > > correct. first push release is done. Work for others (e.g.OAuth2 and > data-sync/offline) is in the works. > > > >> >> >>> What is a user he looking for when he gets to Aerogear? How can >>> Aerogear help him? >>> >> >> Most of the developers (others can correct me if I'm wrong) are looking >> to boost their productivity. Let's think about something very complex like >> cryptography or OAuth2, is really hard to newcomers to grok into RFCs and >> implement it. Most part of the time people just want to connect their apps >> to Facebook, Twitter, <put your favorite social network here>. People don't >> have time and sometimes patience to read RFCs and start from scratch >> (because it's boring) >> >> I think this is where AeroGear comes into place. If you talk to Passos, >> he will give to you details about reducing 25% of the hard work on Android >> with AeroGear. >> > > Right, both are examples to make life easier. Same goes for push. our > server makes it easier to handle and manage all aspects of push. > > >> >> >>> >>> At this point I would also like to build a “design persona” to have a >>> coherent identity, voice and styles throughout our line. If aerogear was a >>> person, who would it be? what voice does it have, color, typography, etc. >>> >> >> Amazing. Not sure if AeroGear would be a person, but to me is more like >> Skipper ( >> http://img3.wikia.nocookie.net/__cb20130327234948/pixar/images/7/70/Plane... >> ) >> > > hehe :) > > >> >> >>> With this done we will make sure our websites, demos and consoles speak >>> the same language. >>> >>> Thanks >>> >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> >> >> >> >> -- >> >> -- >> "The measure of a man is what he does with power" - Plato >> - >> @abstractj >> - >> Volenti Nihil Difficile >> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev >

On 11 nov. 2014, at 18:12, Andres Galante <agalante(a)redhat.com&gt; wrote: It's a good ideas and it will be a challenge to build a UI that combines features and a context selector for each client. Lets say you are an android developer and you are looking for Aerogears Push code. What would you find more natural: 1- Going to the Push section first and then choose android or 2- First select Android and then go to Push The context selector its perfect for documentation. An android developer doesn't need to see anything thats not android. UX team is doing research on contextual selectors for Paternally, I'll talk with them and if its a good fit for us.

----- Original Message ----- From: "Matthias Wessendorf" <matzew(a)apache.org&gt; To: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org&gt; Sent: Tuesday, November 11, 2014 1:29:45 PM Subject: Re: [aerogear-dev] Aerogear Website design On Tue, Nov 11, 2014 at 5:18 PM, Lukáš Fryč < lukas.fryc(a)gmail.com > wrote: Ok, it should have been lighgreen for Droid and lightblue for Cordova off course ;-) off course! :-) On Tue, Nov 11, 2014 at 5:18 PM, Lukáš Fryč < lukas.fryc(a)gmail.com > wrote: I would also highlight importance of supporting developers coming from different platforms (Java on Android, ObjC/Swift on iOS, and plain JavaScript, JavaScript in Cordova). I know that it might be hard to combine with a concept of feature-oriented pages, but I imagine we could allow at least color- or icon-based highlights for different platforms (icon of Droid - lightblue code sample background, icon of apple - silver background, JS logo light-yellow background, Cordova logo - pink background!) + I would even consider a something like select box in top navbar that allows to filter out platform specific information. ;-) On Tue, Nov 11, 2014 at 8:05 AM, Matthias Wessendorf < matzew(a)apache.org > wrote: On Tue, Nov 11, 2014 at 6:04 AM, Bruno Oliveira < bruno(a)abstractj.org > wrote: Ahoy my friend, answers inline. (my personal opinion) On Mon, Nov 10, 2014 at 5:34 PM, Andres Galante < agalante(a)redhat.com > wrote: Hi, I am starting to redesign auroras.org . I would like your help to understand better the product and our user. Who is the developer that uses Aerogear? is it a hardcore developer, or someone that is looking for a ready made solution? I think both. We have JavaScript, iOS, Android, Cordova, Firefox and JavaEE developers. For example, some Java EE developers don't care about JS and they might be looking for a ready made solution (In this situation, AeroGear with Forge or JBDS is a good fit). At the same time you have JS developers for example like Lukas or Luke, which are familiar with Java EE, but they are more like a hardcore developer and they just want to make use of libraries. Some devs will stick make use of tools, others to just our libraries. +1 both are 'target' I understand that we have 3 products, Core, Push and security. What is our main product? At the moment, I would say that Push is the main AeroGear focus. Although AG is more than just Push. We provide libraries willing to make developer's life easy so topics like: Push, Security (cryptography, OAuth2 libraries, 2 factor), data sync, geo-fencing, offline support...and more crazy and dirty things you could possible imagine with fancy devices — probably AG will be there. correct. first push release is done. Work for others (e.g.OAuth2 and data-sync/offline) is in the works. What is a user he looking for when he gets to Aerogear? How can Aerogear help him? Most of the developers (others can correct me if I'm wrong) are looking to boost their productivity. Let's think about something very complex like cryptography or OAuth2, is really hard to newcomers to grok into RFCs and implement it. Most part of the time people just want to connect their apps to Facebook, Twitter, <put your favorite social network here>. People don't have time and sometimes patience to read RFCs and start from scratch (because it's boring) I think this is where AeroGear comes into place. If you talk to Passos, he will give to you details about reducing 25% of the hard work on Android with AeroGear. Right, both are examples to make life easier. Same goes for push. our server makes it easier to handle and manage all aspects of push. At this point I would also like to build a “design persona” to have a coherent identity, voice and styles throughout our line. If aerogear was a person, who would it be? what voice does it have, color, typography, etc. Amazing. Not sure if AeroGear would be a person, but to me is more like Skipper ( http://img3.wikia.nocookie.net/__cb20130327234948/pixar/images/7/70/Plane... ) hehe :) With this done we will make sure our websites, demos and consoles speak the same language. Thanks _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -- -- "The measure of a man is what he does with power" - Plato - @abstractj - Volenti Nihil Difficile _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

On Tue, Nov 11, 2014 at 6:12 PM, Andres Galante <agalante(a)redhat.com&gt; wrote: > It's a good ideas and it will be a challenge to build a UI that combines > features and a context selector for each client. > > Lets say you are an android developer and you are looking for Aerogears > Push code. What would you find more natural: > > 1- Going to the Push section first and then choose android or > 2- First select Android and then go to Push > Both are natural :-) It really depends where they come from, or more why the look at AeroGear. If I look for a certain feature (e.g. push, data-sync or crypto), I'd appreciate a "feature" landing page that gives me links for supported platforms (e.g. Android or iOS). If I, in "contrast", look for generic platform support (e.g. Android or iOS), I'd appreciate the "Android" page which would list all supported features, for the platform (e.g. push, data-sync or crypto). > > The context selector its perfect for documentation. An android developer > doesn't need to see anything thats not android. > > UX team is doing research on contextual selectors for Paternally, I'll > talk with them and if its a good fit for us. > > > > > > ----- Original Message ----- > From: "Matthias Wessendorf" <matzew(a)apache.org&gt; > To: "AeroGear Developer Mailing List" <aerogear-dev(a)lists.jboss.org&gt; > Sent: Tuesday, November 11, 2014 1:29:45 PM > Subject: Re: [aerogear-dev] Aerogear Website design > > > > On Tue, Nov 11, 2014 at 5:18 PM, Lukáš Fryč < lukas.fryc(a)gmail.com > > wrote: > > > > Ok, it should have been lighgreen for Droid and lightblue for Cordova off > course ;-) > > off course! :-) > > > > > > On Tue, Nov 11, 2014 at 5:18 PM, Lukáš Fryč < lukas.fryc(a)gmail.com > > wrote: > > > > I would also highlight importance of supporting developers coming from > different platforms (Java on Android, ObjC/Swift on iOS, and plain > JavaScript, JavaScript in Cordova). > > > I know that it might be hard to combine with a concept of > feature-oriented pages, > > but I imagine we could allow at least color- or icon-based highlights for > different platforms (icon of Droid - lightblue code sample background, icon > of apple - silver background, JS logo light-yellow background, Cordova logo > - pink background!) > > + I would even consider a something like select box in top navbar that > allows to filter out platform specific information. ;-) > > > On Tue, Nov 11, 2014 at 8:05 AM, Matthias Wessendorf < matzew(a)apache.org > > wrote: > > > > > > On Tue, Nov 11, 2014 at 6:04 AM, Bruno Oliveira < bruno(a)abstractj.org > > wrote: > > > > Ahoy my friend, answers inline. (my personal opinion) > > On Mon, Nov 10, 2014 at 5:34 PM, Andres Galante < agalante(a)redhat.com > > wrote: > > > Hi, I am starting to redesign auroras.org . I would like your help to > understand better the product and our user. > > Who is the developer that uses Aerogear? is it a hardcore developer, or > someone that is looking for a ready made solution? > > I think both. We have JavaScript, iOS, Android, Cordova, Firefox and > JavaEE developers. For example, some Java EE developers don't care about JS > and they might be looking for a ready made solution (In this situation, > AeroGear with Forge or JBDS is a good fit). > > At the same time you have JS developers for example like Lukas or Luke, > which are familiar with Java EE, but they are more like a hardcore > developer and they just want to make use of libraries. Some devs will stick > make use of tools, others to just our libraries. > > +1 both are 'target' > > > > > > I understand that we have 3 products, Core, Push and security. What is > our main product? > > At the moment, I would say that Push is the main AeroGear focus. Although > AG is more than just Push. We provide libraries willing to make developer's > life easy so topics like: Push, Security (cryptography, OAuth2 libraries, 2 > factor), data sync, geo-fencing, offline support...and more crazy and dirty > things you could possible imagine with fancy devices — probably AG will be > there. > > correct. first push release is done. Work for others (e.g.OAuth2 and > data-sync/offline) is in the works. > > > > > > > What is a user he looking for when he gets to Aerogear? How can Aerogear > help him? > > Most of the developers (others can correct me if I'm wrong) are looking > to boost their productivity. Let's think about something very complex like > cryptography or OAuth2, is really hard to newcomers to grok into RFCs and > implement it. Most part of the time people just want to connect their apps > to Facebook, Twitter, <put your favorite social network here>. People don't > have time and sometimes patience to read RFCs and start from scratch > (because it's boring) > > I think this is where AeroGear comes into place. If you talk to Passos, > he will give to you details about reducing 25% of the hard work on Android > with AeroGear. > > Right, both are examples to make life easier. Same goes for push. our > server makes it easier to handle and manage all aspects of push. > > > > > > > At this point I would also like to build a “design persona” to have a > coherent identity, voice and styles throughout our line. If aerogear was a > person, who would it be? what voice does it have, color, typography, etc. > > Amazing. Not sure if AeroGear would be a person, but to me is more like > Skipper ( > http://img3.wikia.nocookie.net/__cb20130327234948/pixar/images/7/70/Plane... > ) > > hehe :) > > > > > > With this done we will make sure our websites, demos and consoles speak > the same language. > > Thanks > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > > -- > "The measure of a man is what he does with power" - Plato > - > @abstractj > - > Volenti Nihil Difficile > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev