I like the "Sales Agent" case. I also like the "query criterias", inside of the "business app" for status/location. This will show HOW EASY a business app can send to "n" devices, once it figured out it's own "business rules". Also, have in mind this needs to be simple and quick, and not end-up becoming an "ERP system". Therefore I like this simple demo concept. The apps (iOS/Android) should have a simple UI, displaying a bit of data, from the "business app" (list of leads) + receives Push Messages. Let's do it! On Tue, Jun 11, 2013 at 4:45 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt;wrote: > Hey ! > We would like to provide, in a quite short delay (coming 2 weeks) a demo > showing all the different bits of the "push" world , meaning : > client | push server | JEE Backend App > > We already have the push server (aerogear-unified-push-server) : so we > need a client (iOS and maybe also Android) and a simple JEE backend > application. The backend app will mostly be scaffolded and will use the > aerogear-unified-push-java-client to send messages to the Push Server. > > Then of course, we need to think about an idea of the application itself. > It needs to stay really simple, show how we can send selectively and > should be a bit "business" related. > > So, I came up with an idea this morning that we can discuss here, of > course if you have any other idea don't hesitate to share it. > > Push Demo <https://gist.github.com/sebastienblanc/5755548#introduction> > Introduction > > Prodoctor is a company in the health care industry, selling a > revolutionary tensiometer. Their clients are doctors. Prodoctor has several > sales agents all over the United States. At the headquarters, they have > their "first line" sales department doing cold calls all along the day. > As soon they have a concrete lead, they use their Prodoctor Admin app to > filter out available sales Agents available in the lead area. They can then > send them a push notification. > > The sales agent receives the notification on their mobile device that a > new lead is available. The agent will handle the lead by "accepting" the > notification informing the other agents that the lead has been > processed. > <https://gist.github.com/sebastienblanc/5755548#the-client-app>The > client app > > 1. The client consist of a list of leads : a lead can be "open" or > "in process", leads "in process" of other sales are not visible. > > > - optional : when the client tap a lead it appears on a map > > > 1. The client has a status that he can set: STANDBY | WITH_CLIENT |PTO > 2. The client has a location > 3. The client has an alias > > <https://gist.github.com/sebastienblanc/5755548#prodoctor-admin-client>... > Admin client > > 1. The admin client can create a new lead : > > > - A lead consist of a name and a location > > > 1. The admin client can query for Sales Agents based on : > > > - Status > - Location > > > 1. > > The admin client can assign a lead to a selection (1..n) of sales > agents, this will send out the notifications. > 2. > > The admin client manage the Sales Agents DB. > > > _______________________________________________ > 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

Hey ! We would like to provide, in a quite short delay (coming 2 weeks) a demo showing all the different bits of the "push" world , meaning : client | push server | JEE Backend App We already have the push server (aerogear-unified-push-server) : so we need a client (iOS and maybe also Android) and a simple JEE backend application. The backend app will mostly be scaffolded and will use the aerogear-unified-push-java-client to send messages to the Push Server. Then of course, we need to think about an idea of the application itself. It needs to stay really simple, show how we can send selectively and should be a bit "business" related. So, I came up with an idea this morning that we can discuss here, of course if you have any other idea don't hesitate to share it. Push Demo Introduction Prodoctor is a company in the health care industry, selling a revolutionary tensiometer. Their clients are doctors. Prodoctor has several sales agents all over the United States. At the headquarters, they have their "first line" sales department doing cold calls all along the day. As soon they have a concrete lead, they use their Prodoctor Admin app to filter out available sales Agents available in the lead area. They can then send them a push notification. The sales agent receives the notification on their mobile device that a new lead is available. The agent will handle the lead by "accepting" the notification informing the other agents that the lead has been processed. The client app The client consist of a list of leads : a lead can be "open" or "in process", leads "in process" of other sales are not visible. optional : when the client tap a lead it appears on a map The client has a status that he can set: STANDBY | WITH_CLIENT |PTO The client has a location The client has an alias Prodoctor Admin client The admin client can create a new lead : A lead consist of a name and a location The admin client can query for Sales Agents based on : Status Location The admin client can assign a lead to a selection (1..n) of sales agents, this will send out the notifications. The admin client manage the Sales Agents DB. _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

Ok, there seems to be some agreement on the idea, Nice ! Let's focus a bit on the Mobile App. As said before, it must stay really simple, so basically that's what the apps does : - Sale Agent log in - Sale Agent can set his status (PTO, STANDBY, WITH_CLIENT) - Sale Agent can browse Leads - Sale Agent can accept a Lead - New Leads are pushed to the device : * As Alert/Pop-up if the app is running in background * Dialog apperaing on the main screen if the user is in the app I've tried to sum this up in these (very) basic mockups that you can find attached. Seb [image: Inline image 1] On Wed, Jun 12, 2013 at 9:17 AM, Christos Vasilakis <cvasilak(a)gmail.com&gt;wrote: > +1 > > On Jun 11, 2013, at 5:45 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: > > Hey ! > We would like to provide, in a quite short delay (coming 2 weeks) a demo > showing all the different bits of the "push" world , meaning : > client | push server | JEE Backend App > > We already have the push server (aerogear-unified-push-server) : so we > need a client (iOS and maybe also Android) and a simple JEE backend > application. The backend app will mostly be scaffolded and will use the > aerogear-unified-push-java-client to send messages to the Push Server. > > Then of course, we need to think about an idea of the application itself. > It needs to stay really simple, show how we can send selectively and > should be a bit "business" related. > > So, I came up with an idea this morning that we can discuss here, of > course if you have any other idea don't hesitate to share it. > > Push Demo <https://gist.github.com/sebastienblanc/5755548#introduction> > Introduction > > Prodoctor is a company in the health care industry, selling a > revolutionary tensiometer. Their clients are doctors. Prodoctor has several > sales agents all over the United States. At the headquarters, they have > their "first line" sales department doing cold calls all along the day. > As soon they have a concrete lead, they use their Prodoctor Admin app to > filter out available sales Agents available in the lead area. They can then > send them a push notification. > > The sales agent receives the notification on their mobile device that a > new lead is available. The agent will handle the lead by "accepting" the > notification informing the other agents that the lead has been > processed. > <https://gist.github.com/sebastienblanc/5755548#the-client-app>The > client app > > 1. The client consist of a list of leads : a lead can be "open" or > "in process", leads "in process" of other sales are not visible. > > > - optional : when the client tap a lead it appears on a map > > > 1. The client has a status that he can set: STANDBY | WITH_CLIENT |PTO > 2. The client has a location > 3. The client has an alias > > <https://gist.github.com/sebastienblanc/5755548#prodoctor-admin-client>... > Admin client > > 1. The admin client can create a new lead : > > > - A lead consist of a name and a location > > > 1. The admin client can query for Sales Agents based on : > > > - Status > - Location > > > 1. > > The admin client can assign a lead to a selection (1..n) of sales > agents, this will send out the notifications. > 2. > > The admin client manage the Sales Agents DB. > > _______________________________________________ > > 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 > _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

Ok, there seems to be some agreement on the idea, Nice ! Let's focus a bit on the Mobile App. As said before, it must stay really simple, so basically that's what the apps does : - Sale Agent log in - Sale Agent can set his status (PTO, STANDBY, WITH_CLIENT) - Sale Agent can browse Leads - Sale Agent can accept a Lead - New Leads are pushed to the device : * As Alert/Pop-up if the app is running in background * Dialog apperaing on the main screen if the user is in the app I've tried to sum this up in these (very) basic mockups that you can find attached. Seb Inline image 1 On Wed, Jun 12, 2013 at 9:17 AM, Christos Vasilakis <cvasilak(a)gmail.com <mailto:cvasilak@gmail.com>> wrote: +1 On Jun 11, 2013, at 5:45 PM, Sebastien Blanc <scm.blanc(a)gmail.com <mailto:scm.blanc@gmail.com>> wrote: > Hey ! > We would like to provide, in a quite short delay (coming 2 weeks) > a demo showing all the different bits of the "push" world , meaning : > client | push server | JEE Backend App > > We already have the push server (aerogear-unified-push-server) : > so we need a client (iOS and maybe also Android) and a simple JEE > backend application. The backend app will mostly be scaffolded > and will use the aerogear-unified-push-java-client to send > messages to the Push Server. > > Then of course, we need to think about an idea of the application > itself. It needs to stay really simple, show how we can > send selectively and should be a bit "business" related. > > So, I came up with an idea this morning that we can discuss here, > of course if you have any other idea don't hesitate to share it. > > > Push Demo > > > <https://gist.github.com/sebastienblanc/5755548#introduction>Introduction > > Prodoctor is a company in the health care industry, selling a > revolutionary tensiometer. Their clients are doctors. Prodoctor > has several sales agents all over the United States. At the > headquarters, they have their "first line" sales departmentdoing > cold calls all along the day. As soon they have a concrete lead, > they use their Prodoctor Admin app to filter out available sales > Agents available in the lead area. They can then send them a push > notification. > > The sales agent receives the notification on their mobile device > that a new lead is available. The agent will handle the lead by > "accepting" the notificationinforming the other agents that the > lead has been processed. > > > <https://gist.github.com/sebastienblanc/5755548#the-client-app>The > client app > > 1. The client consist of a list of leads : a lead can be "open" > or "in process", leads "in process" of other sales are not > visible. > > * optional : when the client tap a lead it appears on a map > > 1. The client has a status that he can set: STANDBY | > WITH_CLIENT |PTO > 2. The client has a location > 3. The client has an alias > > > <https://gist.github.com/sebastienblanc/5755548#prodoctor-admin-client>... > Admin client > > 1. The admin client can create a new lead : > > * A lead consist of a name and a location > > 1. The admin client can query for Sales Agents based on : > > * Status > * Location > > 1. > > The admin client can assign a lead to a selection (1..n) of > sales agents, this will send out the notifications. > > 2. > > The admin client manage the Sales Agents DB. > > _______________________________________________ > > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@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

I like summers idea of replacing the popup when app is open with leads list. If you are in the leads list, the list could be updated but we still need some visual effect to say "new lead" maybe bold font with new icon.

On 12 June 2013 15:20, Summers Pittman <supittma(a)redhat.com <mailto:supittma@redhat.com>> wrote: In Android land you wouldn't do a popup. If the app is in the background you would put a notification in the drawer which the user may dismiss or interact with. If you are in the application it would probably be better to update the leads data store and send an update event. If the Leads are being browsed they can be updated. If they aren't then a badge could appear on the leads action. On 06/12/2013 04:52 AM, Sebastien Blanc wrote: > Ok, there seems to be some agreement on the idea, Nice ! > Let's focus a bit on the Mobile App. As said before, it must stay > really simple, so basically that's what the apps does : > > - Sale Agent log in > - Sale Agent can set his status (PTO, STANDBY, WITH_CLIENT) > - Sale Agent can browse Leads > - Sale Agent can accept a Lead > - New Leads are pushed to the device : > * As Alert/Pop-up if the app is running in background > * Dialog apperaing on the main screen if the user is in the app > > I've tried to sum this up in these (very) basic mockups that you > can find attached. > > Seb > Inline image 1 > > > > > On Wed, Jun 12, 2013 at 9:17 AM, Christos Vasilakis > <cvasilak(a)gmail.com <mailto:cvasilak@gmail.com>> wrote: > > +1 > > On Jun 11, 2013, at 5:45 PM, Sebastien Blanc > <scm.blanc(a)gmail.com <mailto:scm.blanc@gmail.com>> wrote: > >> Hey ! >> We would like to provide, in a quite short delay (coming 2 >> weeks) a demo showing all the different bits of the "push" >> world , meaning : >> client | push server | JEE Backend App >> >> We already have the push server >> (aerogear-unified-push-server) : so we need a client (iOS >> and maybe also Android) and a simple JEE backend >> application. The backend app will mostly be scaffolded and >> will use the aerogear-unified-push-java-client to send >> messages to the Push Server. >> >> Then of course, we need to think about an idea of the >> application itself. It needs to stay really simple, show >> how we can send selectively and should be a bit "business" >> related. >> >> So, I came up with an idea this morning that we can discuss >> here, of course if you have any other idea don't hesitate to >> share it. >> >> >> Push Demo >> >> >> <https://gist.github.com/sebastienblanc/5755548#introduction>Introduction >> >> Prodoctor is a company in the health care industry, selling >> a revolutionary tensiometer. Their clients are doctors. >> Prodoctor has several sales agents all over the United >> States. At the headquarters, they have their "first line" >> sales departmentdoing cold calls all along the day. As soon >> they have a concrete lead, they use their Prodoctor Admin >> app to filter out available sales Agents available in the >> lead area. They can then send them a push notification. >> >> The sales agent receives the notification on their mobile >> device that a new lead is available. The agent will handle >> the lead by "accepting" the notificationinforming the other >> agents that the lead has been processed. >> >> >> <https://gist.github.com/sebastienblanc/5755548#the-client-app>The >> client app >> >> 1. The client consist of a list of leads : a lead can be >> "open" or "in process", leads "in process" of other >> sales are not visible. >> >> * optional : when the client tap a lead it appears on a map >> >> 1. The client has a status that he can set: STANDBY | >> WITH_CLIENT |PTO >> 2. The client has a location >> 3. The client has an alias >> >> >> <https://gist.github.com/sebastienblanc/5755548#prodoctor-admin-client>... >> Admin client >> >> 1. The admin client can create a new lead : >> >> * A lead consist of a name and a location >> >> 1. The admin client can query for Sales Agents based on : >> >> * Status >> * Location >> >> 1. >> >> The admin client can assign a lead to a selection (1..n) >> of sales agents, this will send out the notifications. >> >> 2. >> >> The admin client manage the Sales Agents DB. >> >> _______________________________________________ >> >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> <mailto:aerogear-dev@lists.jboss.org> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > <mailto:aerogear-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@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 06/12/2013 09:26 AM, Corinne Krych wrote: I like summers idea of replacing the popup when app is open with leads list. If you are in the leads list, the list could be updated but we still need some visual effect to say "new lead" maybe bold font with new icon. In the Google Plus application the refresh button becomes highlighted if there is new data. (As a suggestion).

Or we could add the entry and have a special style applied. On 12 June 2013 15:20, Summers Pittman <supittma(a)redhat.com&gt; wrote: > In Android land you wouldn't do a popup. If the app is in the > background you would put a notification in the drawer which the user may > dismiss or interact with. > > If you are in the application it would probably be better to update the > leads data store and send an update event. If the Leads are being browsed > they can be updated. If they aren't then a badge could appear on the leads > action. > > > On 06/12/2013 04:52 AM, Sebastien Blanc wrote: > > Ok, there seems to be some agreement on the idea, Nice ! > Let's focus a bit on the Mobile App. As said before, it must stay really > simple, so basically that's what the apps does : > > - Sale Agent log in > - Sale Agent can set his status (PTO, STANDBY, WITH_CLIENT) > - Sale Agent can browse Leads > - Sale Agent can accept a Lead > - New Leads are pushed to the device : > * As Alert/Pop-up if the app is running in background > * Dialog apperaing on the main screen if the user is in the app > > I've tried to sum this up in these (very) basic mockups that you can > find attached. > > Seb > [image: Inline image 1] > > > > > On Wed, Jun 12, 2013 at 9:17 AM, Christos Vasilakis <cvasilak(a)gmail.com&gt;wrote: > >> +1 >> >> On Jun 11, 2013, at 5:45 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt; >> wrote: >> >> Hey ! >> We would like to provide, in a quite short delay (coming 2 weeks) a demo >> showing all the different bits of the "push" world , meaning : >> client | push server | JEE Backend App >> >> We already have the push server (aerogear-unified-push-server) : so we >> need a client (iOS and maybe also Android) and a simple JEE backend >> application. The backend app will mostly be scaffolded and will use the >> aerogear-unified-push-java-client to send messages to the Push Server. >> >> >> Then of course, we need to think about an idea of the application >> itself. It needs to stay really simple, show how we can >> send selectively and should be a bit "business" related. >> >> So, I came up with an idea this morning that we can discuss here, of >> course if you have any other idea don't hesitate to share it. >> >> Push Demo <https://gist.github.com/sebastienblanc/5755548#introduction> >> Introduction >> >> Prodoctor is a company in the health care industry, selling a >> revolutionary tensiometer. Their clients are doctors. Prodoctor has several >> sales agents all over the United States. At the headquarters, they have >> their "first line" sales department doing cold calls all along the >> day. As soon they have a concrete lead, they use their Prodoctor Admin app >> to filter out available sales Agents available in the lead area. They can >> then send them a push notification. >> >> The sales agent receives the notification on their mobile device that a >> new lead is available. The agent will handle the lead by "accepting" the >> notification informing the other agents that the lead has been >> processed. >> <https://gist.github.com/sebastienblanc/5755548#the-client-app>The >> client app >> >> 1. The client consist of a list of leads : a lead can be "open" or >> "in process", leads "in process" of other sales are not visible. >> >> >> - optional : when the client tap a lead it appears on a map >> >> >> 1. The client has a status that he can set: STANDBY | WITH_CLIENT >> |PTO >> 2. The client has a location >> 3. The client has an alias >> >> <https://gist.github.com/sebastienblanc/5755548#prodoctor-admin-client>... >> Admin client >> >> 1. The admin client can create a new lead : >> >> >> - A lead consist of a name and a location >> >> >> 1. The admin client can query for Sales Agents based on : >> >> >> - Status >> - Location >> >> >> 1. >> >> The admin client can assign a lead to a selection (1..n) of sales >> agents, this will send out the notifications. >> 2. >> >> The admin client manage the Sales Agents DB. >> >> _______________________________________________ >> >> 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 >> > > > > _______________________________________________ > aerogear-dev mailing listaerogear-dev@lists.jboss.orghttps://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 > _______________________________________________ aerogear-dev mailing listaerogear-dev@lists.jboss.orghttps://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

Repo suggestions: - aerogear-push-quickstart-android - aerogear-push-quickstart-backend - aerogear-push-quickstart-ios JIRA => https://issues.jboss.org/browse/AEROGEAR-1261 On Wed, Jun 12, 2013 at 3:34 PM, Matthias Wessendorf <matzew(a)apache.org&gt;wrote: > > > > On Wed, Jun 12, 2013 at 3:29 PM, Summers Pittman <supittma(a)redhat.com&gt;wrote: > >> On 06/12/2013 09:26 AM, Corinne Krych wrote: >> >> I like summers idea of replacing the popup when app is open with leads >> list. >> If you are in the leads list, the list could be updated but we still >> need some visual effect to say "new lead" maybe bold font with new icon. >> >> In the Google Plus application the refresh button becomes highlighted if >> there is new data. (As a suggestion). >> > > Or... confirm the "popup" and have the list refresh. A color (on the new > lead) is fading out :) > > > >> >> Or we could add the entry and have a special style applied. >> >> >> >> >> On 12 June 2013 15:20, Summers Pittman <supittma(a)redhat.com&gt; wrote: >> >>> In Android land you wouldn't do a popup. If the app is in the >>> background you would put a notification in the drawer which the user may >>> dismiss or interact with. >>> >>> If you are in the application it would probably be better to update the >>> leads data store and send an update event. If the Leads are being browsed >>> they can be updated. If they aren't then a badge could appear on the leads >>> action. >>> >>> >>> On 06/12/2013 04:52 AM, Sebastien Blanc wrote: >>> >>> Ok, there seems to be some agreement on the idea, Nice ! >>> Let's focus a bit on the Mobile App. As said before, it must stay >>> really simple, so basically that's what the apps does : >>> >>> - Sale Agent log in >>> - Sale Agent can set his status (PTO, STANDBY, WITH_CLIENT) >>> - Sale Agent can browse Leads >>> - Sale Agent can accept a Lead >>> - New Leads are pushed to the device : >>> * As Alert/Pop-up if the app is running in background >>> * Dialog apperaing on the main screen if the user is in the app >>> >>> I've tried to sum this up in these (very) basic mockups that you can >>> find attached. >>> >>> Seb >>> [image: Inline image 1] >>> >>> >>> >>> >>> On Wed, Jun 12, 2013 at 9:17 AM, Christos Vasilakis <cvasilak(a)gmail.com >>> > wrote: >>> >>>> +1 >>>> >>>> On Jun 11, 2013, at 5:45 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt; >>>> wrote: >>>> >>>> Hey ! >>>> We would like to provide, in a quite short delay (coming 2 weeks) a >>>> demo showing all the different bits of the "push" world , meaning : >>>> client | push server | JEE Backend App >>>> >>>> We already have the push server (aerogear-unified-push-server) : so >>>> we need a client (iOS and maybe also Android) and a simple JEE backend >>>> application. The backend app will mostly be scaffolded and will use the >>>> aerogear-unified-push-java-client to send messages to the Push >>>> Server. >>>> >>>> Then of course, we need to think about an idea of the application >>>> itself. It needs to stay really simple, show how we can >>>> send selectively and should be a bit "business" related. >>>> >>>> So, I came up with an idea this morning that we can discuss here, of >>>> course if you have any other idea don't hesitate to share it. >>>> >>>> Push Demo <https://gist.github.com/sebastienblanc/5755548#introduction> >>>> Introduction >>>> >>>> Prodoctor is a company in the health care industry, selling a >>>> revolutionary tensiometer. Their clients are doctors. Prodoctor has several >>>> sales agents all over the United States. At the headquarters, they have >>>> their "first line" sales department doing cold calls all along the >>>> day. As soon they have a concrete lead, they use their Prodoctor Admin app >>>> to filter out available sales Agents available in the lead area. They can >>>> then send them a push notification. >>>> >>>> The sales agent receives the notification on their mobile device that >>>> a new lead is available. The agent will handle the lead by "accepting" the >>>> notification informing the other agents that the lead has been >>>> processed. >>>> <https://gist.github.com/sebastienblanc/5755548#the-client-app>The >>>> client app >>>> >>>> 1. The client consist of a list of leads : a lead can be "open" or >>>> "in process", leads "in process" of other sales are not visible. >>>> >>>> >>>> - optional : when the client tap a lead it appears on a map >>>> >>>> >>>> 1. The client has a status that he can set: STANDBY | WITH_CLIENT >>>> |PTO >>>> 2. The client has a location >>>> 3. The client has an alias >>>> >>>> >>>> <https://gist.github.com/sebastienblanc/5755548#prodoctor-admin-client>... >>>> Admin client >>>> >>>> 1. The admin client can create a new lead : >>>> >>>> >>>> - A lead consist of a name and a location >>>> >>>> >>>> 1. The admin client can query for Sales Agents based on : >>>> >>>> >>>> - Status >>>> - Location >>>> >>>> >>>> 1. >>>> >>>> The admin client can assign a lead to a selection (1..n) of sales >>>> agents, this will send out the notifications. >>>> 2. >>>> >>>> The admin client manage the Sales Agents DB. >>>> >>>> _______________________________________________ >>>> >>>> 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 >>>> >>> >>> >>> >>> _______________________________________________ >>> aerogear-dev mailing listaerogear-dev@lists.jboss.orghttps://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 >>> >> >> >> >> _______________________________________________ >> aerogear-dev mailing listaerogear-dev@lists.jboss.orghttps://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 > -- 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

w00t!!!! On Friday, June 14, 2013, Sebastien Blanc wrote: > A quick update : > > A first version of the backend application has been created and be found > here https://github.com/sebastienblanc/aerogear-push-quickstart-backend/ > You can create Leads, then query for Sale Agents and send them a push > notification containing the lead information. > > The readme contains all the intructions. We made some tests with Matzew > yesterday and we were able to send notification from the backend app to an > Android Device, using of course, the Push Server : this means we have the > complete loop working , yeah ! > > I will now work on the API of the Prodoctor app that will be used by the > Native Clients. > > Seb > > > > On Thu, Jun 13, 2013 at 11:33 AM, Matthias Wessendorf <matzew(a)apache.org&gt;wrote: > > Repo suggestions: > > > - aerogear-push-quickstart-android > - aerogear-push-quickstart-backend > - aerogear-push-quickstart-ios > > > > JIRA => https://issues.jboss.org/browse/AEROGEAR-1261 > > > > On Wed, Jun 12, 2013 at 3:34 PM, Matthias Wessendorf <matzew(a)apache.org&gt;wrote: > > > > > On Wed, Jun 12, 2013 at 3:29 PM, Summers Pittman <supittma(a)redhat.com&gt;wrote: > > On 06/12/2013 09:26 AM, Corinne Krych wrote: > > I like summers idea of replacing the popup when app is open with leads > list. > If you are in the leads list, the list could be updated but we still need > some visual effect to say "new lead" maybe bold font with new icon. > > In the Google Plus application the refresh button becomes highlighted if > there is new data. (As a suggestion). > > > Or... confirm the "popup" and have the list refresh. A color (on the new > lead) is fading out :) > > > > > Or we could add the entry and have a special style applied. > > > > > On 12 June 2013 15:20, Summers Pittman <supittma(a)redhat.com&gt; wrote: > > In Android land you wouldn't do a popup. If the app is in the > background you would put a notification in the drawer which the user may > dismiss or interact with. > > If you are in the application it would probably be better to update the > leads data store and send an update event. If the Leads are being browsed > they can be updated. If they aren't then a badge could appear on the leads > action. > > > On 06/12/2013 04:52 AM, Sebastien Blanc wrote: > > Ok, there seems to be some agreement on the idea, Nice ! > Let's focus a bit on the Mobile App. As said before, it must stay really > simple, so basically that's what the apps does : > > -- 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

nice! that should be enough for the mobile clients, right ? On Fri, Jun 14, 2013 at 3:21 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt;wrote: > Ok, > We got here a first set of services which should be enough for the demo > purposes : > > POST /login > > Login service, mandatory for all further request. > > curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" > -X POST -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/login > > It will return the user : > > {"id":"cb3c05aa-3fdd-4b4e-9b90-386fc7e5671a","enabled":true,"createdDate":1371215851063,"expirationDate":null,"partition":null,"loginName":"john","firstName":null,"lastName":null,"email":null,"status":"PTO","password":"123","location":"New York"} > > POST /logout > > Logout service. > > curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" > -X POST -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/logout > > returns no data > GET /leads > > Obtain a list of leads. > > curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" > -X GET -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/leads > > You will get a list of leads : > > [{"id":39,"version":0,"name":"Doctor No","location":"New York","phoneNumber":"0612412121"}] > > PUT /saleagents/{id} > > update a SaleAgent, the service will only update the status and the > location for now. > > curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" -X PUT -d '{"id":"13bbaea3-9271-43f7-80aa-fb21360ff684","enabled":true,"createdDate":1371213256827,"expirationDate":null,"partition":null,"loginName":"john","firstName":null,"lastName":null,"email":null,"version":0,"status":"CHANGED","password":"123","location":"New York"}' http://localhost:8080/prodoctor/saleagents/13bbaea3-9271-43f7-80aa-fb2136... > > returns no data > > > On Fri, Jun 14, 2013 at 10:21 AM, Matthias Wessendorf <matzew(a)apache.org&gt;wrote: > >> w00t!!!! >> >> >> On Friday, June 14, 2013, Sebastien Blanc wrote: >> >>> A quick update : >>> >>> A first version of the backend application has been created and be >>> found here >>> https://github.com/sebastienblanc/aerogear-push-quickstart-backend/ >>> You can create Leads, then query for Sale Agents and send them a push >>> notification containing the lead information. >>> >>> The readme contains all the intructions. We made some tests with Matzew >>> yesterday and we were able to send notification from the backend app to an >>> Android Device, using of course, the Push Server : this means we have the >>> complete loop working , yeah ! >>> >>> I will now work on the API of the Prodoctor app that will be used by >>> the Native Clients. >>> >>> Seb >>> >>> >>> >>> On Thu, Jun 13, 2013 at 11:33 AM, Matthias Wessendorf < >>> matzew(a)apache.org&gt; wrote: >>> >>> Repo suggestions: >>> >>> >>> - aerogear-push-quickstart-android >>> - aerogear-push-quickstart-backend >>> - aerogear-push-quickstart-ios >>> >>> >>> >>> JIRA => https://issues.jboss.org/browse/AEROGEAR-1261 >>> >>> >>> >>> On Wed, Jun 12, 2013 at 3:34 PM, Matthias Wessendorf <matzew(a)apache.org >>> > wrote: >>> >>> >>> >>> >>> On Wed, Jun 12, 2013 at 3:29 PM, Summers Pittman <supittma(a)redhat.com&gt;wrote: >>> >>> On 06/12/2013 09:26 AM, Corinne Krych wrote: >>> >>> I like summers idea of replacing the popup when app is open with leads >>> list. >>> If you are in the leads list, the list could be updated but we still >>> need some visual effect to say "new lead" maybe bold font with new icon. >>> >>> In the Google Plus application the refresh button becomes highlighted >>> if there is new data. (As a suggestion). >>> >>> >>> Or... confirm the "popup" and have the list refresh. A color (on the >>> new lead) is fading out :) >>> >>> >>> >>> >>> Or we could add the entry and have a special style applied. >>> >>> >>> >>> >>> On 12 June 2013 15:20, Summers Pittman <supittma(a)redhat.com&gt; wrote: >>> >>> In Android land you wouldn't do a popup. If the app is in the >>> background you would put a notification in the drawer which the user may >>> dismiss or interact with. >>> >>> If you are in the application it would probably be better to update the >>> leads data store and send an update event. If the Leads are being browsed >>> they can be updated. If they aren't then a badge could appear on the leads >>> action. >>> >>> >>> On 06/12/2013 04:52 AM, Sebastien Blanc wrote: >>> >>> Ok, there seems to be some agreement on the idea, Nice ! >>> Let's focus a bit on the Mobile App. As said before, it must stay >>> really simple, so basically that's what the apps does : >>> >>> >> >> -- >> 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

Service has been added : PUT /leads/{id} Update a Lead, typically used if a Sale Agent wants to assign a lead to him. curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" -X PUT -d '{"id":39,"version":0,"name":"Doctor No","location":"New York","phoneNumber":"121212121","saleAgent":"13bbaea3-9271-43f7-80aa-fb21360ff684"}' http://localhost:8080/prodoctor/leads/39 returns no data On Fri, Jun 14, 2013 at 3:30 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: > Exactly ! That is the "public" set needed by the client : login/logout , get leads, update location/status > > Oh ! I miss one "assign lead to user" , I will update the doc > Seb > > > > On Fri, Jun 14, 2013 at 3:25 PM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >> nice! >> >> that should be enough for the mobile clients, right ? >> >> >> On Fri, Jun 14, 2013 at 3:21 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: >>> Ok, >>> We got here a first set of services which should be enough for the demo purposes : >>> >>> POST /login >>> >>> Login service, mandatory for all further request. >>> >>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" >>> -X POST -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/login >>> It will return the user : >>> >>> {"id":"cb3c05aa-3fdd-4b4e-9b90-386fc7e5671a","enabled":true,"createdDate":1371215851063,"expirationDate":null,"partition":null,"loginName":"john","firstName":null,"lastName":null,"email":null,"status":"PTO","password":"123","location":"New York"} >>> POST /logout >>> >>> Logout service. >>> >>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" >>> -X POST -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/logout >>> returns no data >>> >>> GET /leads >>> >>> Obtain a list of leads. >>> >>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" >>> -X GET -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/leads >>> You will get a list of leads : >>> >>> [{"id":39,"version":0,"name":"Doctor No","location":"New York","phoneNumber":"0612412121"}] >>> PUT /saleagents/{id} >>> >>> update a SaleAgent, the service will only update the status and the location for now. >>> >>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" -X PUT -d '{"id":"13bbaea3-9271-43f7-80aa-fb21360ff684","enabled":true,"createdDate":1371213256827,"expirationDate":null,"partition":null,"loginName":"john","firstName":null,"lastName":null,"email":null,"version":0,"status":"CHANGED","password":"123","location":"New York"}' http://localhost:8080/prodoctor/saleagents/13bbaea3-9271-43f7-80aa-fb2136... >>> returns no data >>> >>> >>> >>> On Fri, Jun 14, 2013 at 10:21 AM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >>>> w00t!!!! >>>> >>>> >>>> On Friday, June 14, 2013, Sebastien Blanc wrote: >>>>> A quick update : >>>>> >>>>> A first version of the backend application has been created and be found here https://github.com/sebastienblanc/aerogear-push-quickstart-backend/ >>>>> You can create Leads, then query for Sale Agents and send them a push notification containing the lead information. >>>>> >>>>> The readme contains all the intructions. We made some tests with Matzew yesterday and we were able to send notification from the backend app to an Android Device, using of course, the Push Server : this means we have the complete loop working , yeah ! >>>>> >>>>> I will now work on the API of the Prodoctor app that will be used by the Native Clients. >>>>> >>>>> Seb >>>>> >>>>> >>>>> >>>>> On Thu, Jun 13, 2013 at 11:33 AM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >>>>> Repo suggestions: >>>>> >>>>> aerogear-push-quickstart-android >>>>> aerogear-push-quickstart-backend >>>>> aerogear-push-quickstart-ios >>>>> >>>>> >>>>> JIRA => https://issues.jboss.org/browse/AEROGEAR-1261 >>>>> >>>>> >>>>> >>>>> On Wed, Jun 12, 2013 at 3:34 PM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >>>>> >>>>> >>>>> >>>>> On Wed, Jun 12, 2013 at 3:29 PM, Summers Pittman <supittma(a)redhat.com&gt; wrote: >>>>> On 06/12/2013 09:26 AM, Corinne Krych wrote: >>>>>> I like summers idea of replacing the popup when app is open with leads list. >>>>>> If you are in the leads list, the list could be updated but we still need some visual effect to say "new lead" maybe bold font with new icon. >>>>> In the Google Plus application the refresh button becomes highlighted if there is new data. (As a suggestion). >>>>> >>>>> Or... confirm the "popup" and have the list refresh. A color (on the new lead) is fading out :) >>>>> >>>>> >>>>> >>>>> Or we could add the entry and have a special style applied. >>>>> >>>>> >>>>>> >>>>>> >>>>>> On 12 June 2013 15:20, Summers Pittman <supittma(a)redhat.com&gt; wrote: >>>>>> In Android land you wouldn't do a popup. If the app is in the background you would put a notification in the drawer which the user may dismiss or interact with. >>>>>> >>>>>> If you are in the application it would probably be better to update the leads data store and send an update event. If the Leads are being browsed they can be updated. If they aren't then a badge could appear on the leads action. >>>>>> >>>>>> >>>>>> On 06/12/2013 04:52 AM, Sebastien Blanc wrote: >>>>>>> Ok, there seems to be some agreement on the idea, Nice ! >>>>>>> Let's focus a bit on the Mobile App. As said before, it must stay really simple, so basically that's what the apps does : >>>> >>>> >>>> -- >>>> 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

It will come for sure, we just have to discuss "the planning" ;) Seb

On Sat, Jun 15, 2013 at 3:45 PM, Kris Borchers <kborcher(a)redhat.com&gt; wrote: > Maybe I missed off list discussions but is there any reason an "all inclusive" push demo doesn't include JS (SimplePush) in any of this discussion? > > On Jun 14, 2013, at 8:53, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: > >> Service has been added : >> >> PUT /leads/{id} >> >> Update a Lead, typically used if a Sale Agent wants to assign a lead to him. >> >> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" -X PUT -d '{"id":39,"version":0,"name":"Doctor No","location":"New York","phoneNumber":"121212121","saleAgent":"13bbaea3-9271-43f7-80aa-fb21360ff684"}' http://localhost:8080/prodoctor/leads/39 >> returns no data >> >> >> >> On Fri, Jun 14, 2013 at 3:30 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: >>> Exactly ! That is the "public" set needed by the client : login/logout , get leads, update location/status >>> >>> Oh ! I miss one "assign lead to user" , I will update the doc >>> Seb >>> >>> >>> >>> On Fri, Jun 14, 2013 at 3:25 PM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >>>> nice! >>>> >>>> that should be enough for the mobile clients, right ? >>>> >>>> >>>> On Fri, Jun 14, 2013 at 3:21 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: >>>>> Ok, >>>>> We got here a first set of services which should be enough for the demo purposes : >>>>> >>>>> POST /login >>>>> >>>>> Login service, mandatory for all further request. >>>>> >>>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" >>>>> -X POST -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/login >>>>> It will return the user : >>>>> >>>>> {"id":"cb3c05aa-3fdd-4b4e-9b90-386fc7e5671a","enabled":true,"createdDate":1371215851063,"expirationDate":null,"partition":null,"loginName":"john","firstName":null,"lastName":null,"email":null,"status":"PTO","password":"123","location":"New York"} >>>>> POST /logout >>>>> >>>>> Logout service. >>>>> >>>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" >>>>> -X POST -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/logout >>>>> returns no data >>>>> >>>>> GET /leads >>>>> >>>>> Obtain a list of leads. >>>>> >>>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" >>>>> -X GET -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/leads >>>>> You will get a list of leads : >>>>> >>>>> [{"id":39,"version":0,"name":"Doctor No","location":"New York","phoneNumber":"0612412121"}] >>>>> PUT /saleagents/{id} >>>>> >>>>> update a SaleAgent, the service will only update the status and the location for now. >>>>> >>>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" -X PUT -d '{"id":"13bbaea3-9271-43f7-80aa-fb21360ff684","enabled":true,"createdDate":1371213256827,"expirationDate":null,"partition":null,"loginName":"john","firstName":null,"lastName":null,"email":null,"version":0,"status":"CHANGED","password":"123","location":"New York"}' http://localhost:8080/prodoctor/saleagents/13bbaea3-9271-43f7-80aa-fb2136... >>>>> returns no data >>>>> >>>>> >>>>> >>>>> On Fri, Jun 14, 2013 at 10:21 AM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >>>>>> w00t!!!! >>>>>> >>>>>> >>>>>> On Friday, June 14, 2013, Sebastien Blanc wrote: >>>>>>> A quick update : >>>>>>> >>>>>>> A first version of the backend application has been created and be found here https://github.com/sebastienblanc/aerogear-push-quickstart-backend/ >>>>>>> You can create Leads, then query for Sale Agents and send them a push notification containing the lead information. >>>>>>> >>>>>>> The readme contains all the intructions. We made some tests with Matzew yesterday and we were able to send notification from the backend app to an Android Device, using of course, the Push Server : this means we have the complete loop working , yeah ! >>>>>>> >>>>>>> I will now work on the API of the Prodoctor app that will be used by the Native Clients. >>>>>>> >>>>>>> Seb >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Thu, Jun 13, 2013 at 11:33 AM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >>>>>>> Repo suggestions: >>>>>>> >>>>>>> aerogear-push-quickstart-android >>>>>>> aerogear-push-quickstart-backend >>>>>>> aerogear-push-quickstart-ios >>>>>>> >>>>>>> >>>>>>> JIRA => https://issues.jboss.org/browse/AEROGEAR-1261 >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Jun 12, 2013 at 3:34 PM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Jun 12, 2013 at 3:29 PM, Summers Pittman <supittma(a)redhat.com&gt; wrote: >>>>>>> On 06/12/2013 09:26 AM, Corinne Krych wrote: >>>>>>>> I like summers idea of replacing the popup when app is open with leads list. >>>>>>>> If you are in the leads list, the list could be updated but we still need some visual effect to say "new lead" maybe bold font with new icon. >>>>>>> In the Google Plus application the refresh button becomes highlighted if there is new data. (As a suggestion). >>>>>>> >>>>>>> Or... confirm the "popup" and have the list refresh. A color (on the new lead) is fading out :) >>>>>>> >>>>>>> >>>>>>> >>>>>>> Or we could add the entry and have a special style applied. >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On 12 June 2013 15:20, Summers Pittman <supittma(a)redhat.com&gt; wrote: >>>>>>>> In Android land you wouldn't do a popup. If the app is in the background you would put a notification in the drawer which the user may dismiss or interact with. >>>>>>>> >>>>>>>> If you are in the application it would probably be better to update the leads data store and send an update event. If the Leads are being browsed they can be updated. If they aren't then a badge could appear on the leads action. >>>>>>>> >>>>>>>> >>>>>>>> On 06/12/2013 04:52 AM, Sebastien Blanc wrote: >>>>>>>>> Ok, there seems to be some agreement on the idea, Nice ! >>>>>>>>> Let's focus a bit on the Mobile App. As said before, it must stay really simple, so basically that's what the apps does : >>>>>> >>>>>> >>>>>> -- >>>>>> 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 > > _______________________________________________ > 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 Sat, Jun 15, 2013 at 5:09 PM, Kris Borchers <kborcher(a)redhat.com&gt;wrote: > > > On Jun 15, 2013, at 10:02, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: > > It will come for sure, we just have to discuss "the planning" ;) > Seb > > > But isn't that what this discussion is? If the goal is not to have > similar functionality between the native and web demos then I guess it's > not a big deal but I assume we do want that similar functionality so all > demos should be included from the beginning to avoid wasted time by having > duplicate conversations. > again, right now there is just the demo. Zero lines are written for the clients.

> > > > > On Sat, Jun 15, 2013 at 3:45 PM, Kris Borchers <kborcher(a)redhat.com&gt;wrote: > >> Maybe I missed off list discussions but is there any reason an "all >> inclusive" push demo doesn't include JS (SimplePush) in any of this >> discussion? >> >> On Jun 14, 2013, at 8:53, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: >> >> Service has been added : >> >> PUT /leads/{id} >> >> Update a Lead, typically used if a Sale Agent wants to assign a lead to >> him. >> >> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" -X PUT -d '{"id":39,"version":0,"name":"Doctor No","location":"New York","phoneNumber":"121212121","saleAgent":"13bbaea3-9271-43f7-80aa-fb21360ff684"}' http://localhost:8080/prodoctor/leads/39 >> >> returns no data >> >> >> On Fri, Jun 14, 2013 at 3:30 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt;wrote: >> >>> Exactly ! That is the "public" set needed by the client : login/logout >>> , get leads, update location/status >>> >>> Oh ! I miss one "assign lead to user" , I will update the doc >>> Seb >>> >>> >>> >>> On Fri, Jun 14, 2013 at 3:25 PM, Matthias Wessendorf <matzew(a)apache.org >>> > wrote: >>> >>>> nice! >>>> >>>> that should be enough for the mobile clients, right ? >>>> >>>> >>>> On Fri, Jun 14, 2013 at 3:21 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt;wrote: >>>> >>>>> Ok, >>>>> We got here a first set of services which should be enough for the >>>>> demo purposes : >>>>> >>>>> POST /login >>>>> >>>>> Login service, mandatory for all further request. >>>>> >>>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" >>>>> -X POST -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/login >>>>> >>>>> It will return the user : >>>>> >>>>> {"id":"cb3c05aa-3fdd-4b4e-9b90-386fc7e5671a","enabled":true,"createdDate":1371215851063,"expirationDate":null,"partition":null,"loginName":"john","firstName":null,"lastName":null,"email":null,"status":"PTO","password":"123","location":"New York"} >>>>> >>>>> POST /logout >>>>> >>>>> Logout service. >>>>> >>>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" >>>>> -X POST -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/logout >>>>> >>>>> returns no data >>>>> GET /leads >>>>> >>>>> Obtain a list of leads. >>>>> >>>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" >>>>> -X GET -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/leads >>>>> >>>>> You will get a list of leads : >>>>> >>>>> [{"id":39,"version":0,"name":"Doctor No","location":"New York","phoneNumber":"0612412121"}] >>>>> >>>>> PUT /saleagents/{id} >>>>> >>>>> update a SaleAgent, the service will only update the status and the >>>>> location for now. >>>>> >>>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" -X PUT -d '{"id":"13bbaea3-9271-43f7-80aa-fb21360ff684","enabled":true,"createdDate":1371213256827,"expirationDate":null,"partition":null,"loginName":"john","firstName":null,"lastName":null,"email":null,"version":0,"status":"CHANGED","password":"123","location":"New York"}' http://localhost:8080/prodoctor/saleagents/13bbaea3-9271-43f7-80aa-fb2136... >>>>> >>>>> returns no data >>>>> >>>>> >>>>> On Fri, Jun 14, 2013 at 10:21 AM, Matthias Wessendorf < >>>>> matzew(a)apache.org&gt; wrote: >>>>> >>>>>> w00t!!!! >>>>>> >>>>>> >>>>>> On Friday, June 14, 2013, Sebastien Blanc wrote: >>>>>> >>>>>>> A quick update : >>>>>>> >>>>>>> A first version of the backend application has been created and be >>>>>>> found here >>>>>>> https://github.com/sebastienblanc/aerogear-push-quickstart-backend/ >>>>>>> >>>>>>> You can create Leads, then query for Sale Agents and send them a >>>>>>> push notification containing the lead information. >>>>>>> >>>>>>> The readme contains all the intructions. We made some tests with >>>>>>> Matzew yesterday and we were able to send notification from the backend app >>>>>>> to an Android Device, using of course, the Push Server : this means we have >>>>>>> the complete loop working , yeah ! >>>>>>> >>>>>>> I will now work on the API of the Prodoctor app that will be used >>>>>>> by the Native Clients. >>>>>>> >>>>>>> Seb >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Thu, Jun 13, 2013 at 11:33 AM, Matthias Wessendorf < >>>>>>> matzew(a)apache.org&gt; wrote: >>>>>>> >>>>>>> Repo suggestions: >>>>>>> >>>>>>> >>>>>>> - aerogear-push-quickstart-android >>>>>>> - aerogear-push-quickstart-backend >>>>>>> - aerogear-push-quickstart-ios >>>>>>> >>>>>>> >>>>>>> >>>>>>> JIRA => https://issues.jboss.org/browse/AEROGEAR-1261 >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Jun 12, 2013 at 3:34 PM, Matthias Wessendorf < >>>>>>> matzew(a)apache.org&gt; wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Jun 12, 2013 at 3:29 PM, Summers Pittman < >>>>>>> supittma(a)redhat.com&gt; wrote: >>>>>>> >>>>>>> On 06/12/2013 09:26 AM, Corinne Krych wrote: >>>>>>> >>>>>>> I like summers idea of replacing the popup when app is open with >>>>>>> leads list. >>>>>>> If you are in the leads list, the list could be updated but we >>>>>>> still need some visual effect to say "new lead" maybe bold font with new >>>>>>> icon. >>>>>>> >>>>>>> In the Google Plus application the refresh button becomes >>>>>>> highlighted if there is new data. (As a suggestion). >>>>>>> >>>>>>> >>>>>>> Or... confirm the "popup" and have the list refresh. A color (on >>>>>>> the new lead) is fading out :) >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Or we could add the entry and have a special style applied. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 12 June 2013 15:20, Summers Pittman <supittma(a)redhat.com&gt; wrote: >>>>>>> >>>>>>> In Android land you wouldn't do a popup. If the app is in the >>>>>>> background you would put a notification in the drawer which the user may >>>>>>> dismiss or interact with. >>>>>>> >>>>>>> If you are in the application it would probably be better to update >>>>>>> the leads data store and send an update event. If the Leads are being >>>>>>> browsed they can be updated. If they aren't then a badge could appear on >>>>>>> the leads action. >>>>>>> >>>>>>> >>>>>>> On 06/12/2013 04:52 AM, Sebastien Blanc wrote: >>>>>>> >>>>>>> Ok, there seems to be some agreement on the idea, Nice ! >>>>>>> Let's focus a bit on the Mobile App. As said before, it must stay >>>>>>> really simple, so basically that's what the apps does : >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> 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 >> >> >> _______________________________________________ >> 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 > > > _______________________________________________ > 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

On Jun 15, 2013, at 10:17, Matthias Wessendorf <matzew@apache.org<javascript:_e({}, 'cvml', &#39;matzew(a)apache.org&#39;);&gt;&gt; wrote: On Sat, Jun 15, 2013 at 5:13 PM, Matthias Wessendorf <matzew@apache.org<javascript:_e({}, 'cvml', &#39;matzew(a)apache.org&#39;);&gt; > wrote: > > > > On Sat, Jun 15, 2013 at 5:09 PM, Kris Borchers <kborcher@redhat.com<javascript:_e({}, 'cvml', &#39;kborcher(a)redhat.com&#39;);&gt; > > wrote: > >> >> >> On Jun 15, 2013, at 10:02, Sebastien Blanc <scm.blanc@gmail.com<javascript:_e({}, 'cvml', &#39;scm.blanc(a)gmail.com&#39;);&gt;&gt; >> wrote: >> >> It will come for sure, we just have to discuss "the planning" ;) >> Seb >> >> >> But isn't that what this discussion is? If the goal is not to have >> similar functionality between the native and web demos then I guess it's >> not a big deal but I assume we do want that similar functionality so all >> demos should be included from the beginning to avoid wasted time by having >> duplicate conversations. >> > > again, right now there is just the demo. Zero lines are written for the > clients. > s/demo/backend-demo Understood. I just wanted to make sure we weren't planning without JS in mind since iOS and Android were specifically called out in the original email rather than just saying clients. The overall story works on all the different platforms. On Sat, Jun 15, 2013 at 3:45 PM, Kris Borchers <kborcher(a)redhat.com&gt;wrote: Maybe I missed off list discussions but is there any reason an "all inclusive" push demo doesn't include JS (SimplePush) in any of this discussion? On Jun 14, 2013, at 8:53, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: Service has been added : PUT /leads/{id} Update a Lead, typically used if a Sale Agent wants to assign a lead to him. curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" -X PUT -d '{"id":39,"version":0,"name":"Doctor No","location":"New York","phoneNumber":"121212121","saleAgent":"13bbaea3-9271-43f7-80aa-fb21360ff684"}' http://localhost:8080/prodoctor/leads/39 returns no data On Fri, Jun 14, 2013 at 3:30 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt;wrote: Exactly ! That is the "public" set needed by the client : login/logout , get leads, update location/status Oh ! I miss one "assign lead to user" , I will update the doc Seb On Fri, Jun 14, 2013 at 3:25 PM, Matthias Wessendorf <matzew(a)apache.org&gt;wrote: nice! that should be enough for the mobile clients, right ? On Fri, Jun 14, 2013 at 3:21 PM, Sebastien Blanc

And as a side note, the "admin" client used for the backend-app is also using areogear-js under the cover ;) . So it would be easy to write a web client, 70% of the code is already available :)

On Sat, Jun 15, 2013 at 5:13 PM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > > > > On Sat, Jun 15, 2013 at 5:09 PM, Kris Borchers <kborcher(a)redhat.com&gt; wrote: >> >> >> On Jun 15, 2013, at 10:02, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: >> >>> It will come for sure, we just have to discuss "the planning" ;) >>> Seb >> >> But isn't that what this discussion is? If the goal is not to have similar functionality between the native and web demos then I guess it's not a big deal but I assume we do want that similar functionality so all demos should be included from the beginning to avoid wasted time by having duplicate conversations. > > again, right now there is just the demo. Zero lines are written for the clients. > The overall story works on all the different platforms. > >> >>> >>> >>> >>> On Sat, Jun 15, 2013 at 3:45 PM, Kris Borchers <kborcher(a)redhat.com&gt; wrote: >>>> Maybe I missed off list discussions but is there any reason an "all inclusive" push demo doesn't include JS (SimplePush) in any of this discussion? >>>> >>>> On Jun 14, 2013, at 8:53, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: >>>> >>>>> Service has been added : >>>>> >>>>> PUT /leads/{id} >>>>> >>>>> Update a Lead, typically used if a Sale Agent wants to assign a lead to him. >>>>> >>>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" -X PUT -d '{"id":39,"version":0,"name":"Doctor No","location":"New York","phoneNumber":"121212121","saleAgent":"13bbaea3-9271-43f7-80aa-fb21360ff684"}' http://localhost:8080/prodoctor/leads/39 >>>>> returns no data >>>>> >>>>> >>>>> >>>>> On Fri, Jun 14, 2013 at 3:30 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: >>>>>> Exactly ! That is the "public" set needed by the client : login/logout , get leads, update location/status >>>>>> >>>>>> Oh ! I miss one "assign lead to user" , I will update the doc >>>>>> Seb >>>>>> >>>>>> >>>>>> >>>>>> On Fri, Jun 14, 2013 at 3:25 PM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >>>>>>> nice! >>>>>>> >>>>>>> that should be enough for the mobile clients, right ? >>>>>>> >>>>>>> >>>>>>> On Fri, Jun 14, 2013 at 3:21 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: >>>>>>>> Ok, >>>>>>>> We got here a first set of services which should be enough for the demo purposes : >>>>>>>> >>>>>>>> POST /login >>>>>>>> >>>>>>>> Login service, mandatory for all further request. >>>>>>>> >>>>>>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" >>>>>>>> -X POST -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/login >>>>>>>> It will return the user : >>>>>>>> >>>>>>>> {"id":"cb3c05aa-3fdd-4b4e-9b90-386fc7e5671a","enabled":true,"createdDate":1371215851063,"expirationDate":null,"partition":null,"loginName":"john","firstName":null,"lastName":null,"email":null,"status":"PTO","password":"123","location":"New York"} >>>>>>>> POST /logout >>>>>>>> >>>>>>>> Logout service. >>>>>>>> >>>>>>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" >>>>>>>> -X POST -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/logout >>>>>>>> returns no data >>>>>>>> >>>>>>>> GET /leads >>>>>>>> >>>>>>>> Obtain a list of leads. >>>>>>>> >>>>>>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" >>>>>>>> -X GET -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/leads >>>>>>>> You will get a list of leads : >>>>>>>> >>>>>>>> [{"id":39,"version":0,"name":"Doctor No","location":"New York","phoneNumber":"0612412121"}] >>>>>>>> PUT /saleagents/{id} >>>>>>>> >>>>>>>> update a SaleAgent, the service will only update the status and the location for now. >>>>>>>> >>>>>>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" -X PUT -d '{"id":"13bbaea3-9271-43f7-80aa-fb21360ff684","enabled":true,"createdDate":1371213256827,"expirationDate":null,"partition":null,"loginName":"john","firstName":null,"lastName":null,"email":null,"version":0,"status":"CHANGED","password":"123","location":"New York"}' http://localhost:8080/prodoctor/saleagents/13bbaea3-9271-43f7-80aa-fb2136... >>>>>>>> returns no data >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Jun 14, 2013 at 10:21 AM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >>>>>>>>> w00t!!!! >>>>>>>>> >>>>>>>>> >>>>>>>>> On Friday, June 14, 2013, Sebastien Blanc wrote: >>>>>>>>>> A quick update : >>>>>>>>>> >>>>>>>>>> A first version of the backend application has been created and be found here https://github.com/sebastienblanc/aerogear-push-quickstart-backend/ >>>>>>>>>> You can create Leads, then query for Sale Agents and send them a push notification containing the lead information. >>>>>>>>>> >>>>>>>>>> The readme contains all the intructions. We made some tests with Matzew yesterday and we were able to send notification from the backend app to an Android Device, using of course, the Push Server : this means we have the complete loop working , yeah ! >>>>>>>>>> >>>>>>>>>> I will now work on the API of the Prodoctor app that will be used by the Native Clients. >>>>>>>>>> >>>>>>>>>> Seb >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Thu, Jun 13, 2013 at 11:33 AM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >>>>>>>>>> Repo suggestions: >>>>>>>>>> >>>>>>>>>> aerogear-push-quickstart-android >>>>>>>>>> aerogear-push-quickstart-backend >>>>>>>>>> aerogear-push-quickstart-ios >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> JIRA => https://issues.jboss.org/browse/AEROGEAR-1261 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Jun 12, 2013 at 3:34 PM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Jun 12, 2013 at 3:29 PM, Summers Pittman <supittma(a)redhat.com&gt; wrote: >>>>>>>>>> On 06/12/2013 09:26 AM, Corinne Krych wrote: >>>>>>>>>>> I like summers idea of replacing the popup when app is open with leads list. >>>>>>>>>>> If you are in the leads list, the list could be updated but we still need some visual effect to say "new lead" maybe bold font with new icon. >>>>>>>>>> In the Google Plus application the refresh button becomes highlighted if there is new data. (As a suggestion). >>>>>>>>>> >>>>>>>>>> Or... confirm the "popup" and have the list refresh. A color (on the new lead) is fading out :) >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Or we could add the entry and have a special style applied. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 12 June 2013 15:20, Summers Pittman <supittma(a)redhat.com&gt; wrote: >>>>>>>>>>> In Android land you wouldn't do a popup. If the app is in the background you would put a notification in the drawer which the user may dismiss or interact with. >>>>>>>>>>> >>>>>>>>>>> If you are in the application it would probably be better to update the leads data store and send an update event. If the Leads are being browsed they can be updated. If they aren't then a badge could appear on the leads action. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 06/12/2013 04:52 AM, Sebastien Blanc wrote: >>>>>>>>>>>> Ok, there seems to be some agreement on the idea, Nice ! >>>>>>>>>>>> Let's focus a bit on the Mobile App. As said before, it must stay really simple, so basically that's what the apps does : >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> 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 >>>> >>>> _______________________________________________ >>>> 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 >> >> _______________________________________________ >> 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 Jun 15, 2013, at 10:17, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: And as a side note, the "admin" client used for the backend-app is also using areogear-js under the cover ;) . So it would be easy to write a web client, 70% of the code is already available :) I don't think I agree with that since a demo client will not interact with the interfaces an admin client would and vice versa.

On Sat, Jun 15, 2013 at 5:13 PM, Matthias Wessendorf <matzew(a)apache.org&gt;wrote: > > > > On Sat, Jun 15, 2013 at 5:09 PM, Kris Borchers <kborcher(a)redhat.com&gt;wrote: > >> >> >> On Jun 15, 2013, at 10:02, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: >> >> It will come for sure, we just have to discuss "the planning" ;) >> Seb >> >> >> But isn't that what this discussion is? If the goal is not to have >> similar functionality between the native and web demos then I guess it's >> not a big deal but I assume we do want that similar functionality so all >> demos should be included from the beginning to avoid wasted time by having >> duplicate conversations. >> > > again, right now there is just the demo. Zero lines are written for the > clients. > The overall story works on all the different platforms. > > >> >> >> >> >> On Sat, Jun 15, 2013 at 3:45 PM, Kris Borchers <kborcher(a)redhat.com&gt;wrote: >> >>> Maybe I missed off list discussions but is there any reason an "all >>> inclusive" push demo doesn't include JS (SimplePush) in any of this >>> discussion? >>> >>> On Jun 14, 2013, at 8:53, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: >>> >>> Service has been added : >>> >>> PUT /leads/{id} >>> >>> Update a Lead, typically used if a Sale Agent wants to assign a lead to >>> him. >>> >>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" -X PUT -d '{"id":39,"version":0,"name":"Doctor No","location":"New York","phoneNumber":"121212121","saleAgent":"13bbaea3-9271-43f7-80aa-fb21360ff684"}' http://localhost:8080/prodoctor/leads/39 >>> >>> returns no data >>> >>> >>> On Fri, Jun 14, 2013 at 3:30 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt;wrote: >>> >>>> Exactly ! That is the "public" set needed by the client : login/logout >>>> , get leads, update location/status >>>> >>>> Oh ! I miss one "assign lead to user" , I will update the doc >>>> Seb >>>> >>>> >>>> >>>> On Fri, Jun 14, 2013 at 3:25 PM, Matthias Wessendorf < >>>> matzew(a)apache.org&gt; wrote: >>>> >>>>> nice! >>>>> >>>>> that should be enough for the mobile clients, right ? >>>>> >>>>> >>>>> On Fri, Jun 14, 2013 at 3:21 PM, Sebastien Blanc <scm.blanc(a)gmail.com >>>>> > wrote: >>>>> >>>>>> Ok, >>>>>> We got here a first set of services which should be enough for the >>>>>> demo purposes : >>>>>> >>>>>> POST /login >>>>>> >>>>>> Login service, mandatory for all further request. >>>>>> >>>>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" >>>>>> -X POST -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/login >>>>>> >>>>>> It will return the user : >>>>>> >>>>>> {"id":"cb3c05aa-3fdd-4b4e-9b90-386fc7e5671a","enabled":true,"createdDate":1371215851063,"expirationDate":null,"partition":null,"loginName":"john","firstName":null,"lastName":null,"email":null,"status":"PTO","password":"123","location":"New York"} >>>>>> >>>>>> POST /logout >>>>>> >>>>>> Logout service. >>>>>> >>>>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" >>>>>> -X POST -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/logout >>>>>> >>>>>> returns no data >>>>>> GET /leads >>>>>> >>>>>> Obtain a list of leads. >>>>>> >>>>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" >>>>>> -X GET -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/leads >>>>>> >>>>>> You will get a list of leads : >>>>>> >>>>>> [{"id":39,"version":0,"name":"Doctor No","location":"New York","phoneNumber":"0612412121"}] >>>>>> >>>>>> PUT /saleagents/{id} >>>>>> >>>>>> update a SaleAgent, the service will only update the status and the >>>>>> location for now. >>>>>> >>>>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" -X PUT -d '{"id":"13bbaea3-9271-43f7-80aa-fb21360ff684","enabled":true,"createdDate":1371213256827,"expirationDate":null,"partition":null,"loginName":"john","firstName":null,"lastName":null,"email":null,"version":0,"status":"CHANGED","password":"123","location":"New York"}' http://localhost:8080/prodoctor/saleagents/13bbaea3-9271-43f7-80aa-fb2136... >>>>>> >>>>>> returns no data >>>>>> >>>>>> >>>>>> On Fri, Jun 14, 2013 at 10:21 AM, Matthias Wessendorf < >>>>>> matzew(a)apache.org&gt; wrote: >>>>>> >>>>>>> w00t!!!! >>>>>>> >>>>>>> >>>>>>> On Friday, June 14, 2013, Sebastien Blanc wrote: >>>>>>> >>>>>>>> A quick update : >>>>>>>> >>>>>>>> A first version of the backend application has been created and be >>>>>>>> found here >>>>>>>> https://github.com/sebastienblanc/aerogear-push-quickstart-backend/ >>>>>>>> >>>>>>>> You can create Leads, then query for Sale Agents and send them a >>>>>>>> push notification containing the lead information. >>>>>>>> >>>>>>>> The readme contains all the intructions. We made some tests with >>>>>>>> Matzew yesterday and we were able to send notification from the backend app >>>>>>>> to an Android Device, using of course, the Push Server : this means we have >>>>>>>> the complete loop working , yeah ! >>>>>>>> >>>>>>>> I will now work on the API of the Prodoctor app that will be used >>>>>>>> by the Native Clients. >>>>>>>> >>>>>>>> Seb >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Thu, Jun 13, 2013 at 11:33 AM, Matthias Wessendorf < >>>>>>>> matzew(a)apache.org&gt; wrote: >>>>>>>> >>>>>>>> Repo suggestions: >>>>>>>> >>>>>>>> >>>>>>>> - aerogear-push-quickstart-android >>>>>>>> - aerogear-push-quickstart-backend >>>>>>>> - aerogear-push-quickstart-ios >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> JIRA => https://issues.jboss.org/browse/AEROGEAR-1261 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Jun 12, 2013 at 3:34 PM, Matthias Wessendorf < >>>>>>>> matzew(a)apache.org&gt; wrote: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Jun 12, 2013 at 3:29 PM, Summers Pittman < >>>>>>>> supittma(a)redhat.com&gt; wrote: >>>>>>>> >>>>>>>> On 06/12/2013 09:26 AM, Corinne Krych wrote: >>>>>>>> >>>>>>>> I like summers idea of replacing the popup when app is open with >>>>>>>> leads list. >>>>>>>> If you are in the leads list, the list could be updated but we >>>>>>>> still need some visual effect to say "new lead" maybe bold font with new >>>>>>>> icon. >>>>>>>> >>>>>>>> In the Google Plus application the refresh button becomes >>>>>>>> highlighted if there is new data. (As a suggestion). >>>>>>>> >>>>>>>> >>>>>>>> Or... confirm the "popup" and have the list refresh. A color (on >>>>>>>> the new lead) is fading out :) >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Or we could add the entry and have a special style applied. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On 12 June 2013 15:20, Summers Pittman <supittma(a)redhat.com&gt;wrote: >>>>>>>> >>>>>>>> In Android land you wouldn't do a popup. If the app is in the >>>>>>>> background you would put a notification in the drawer which the user may >>>>>>>> dismiss or interact with. >>>>>>>> >>>>>>>> If you are in the application it would probably be better to >>>>>>>> update the leads data store and send an update event. If the Leads are >>>>>>>> being browsed they can be updated. If they aren't then a badge could >>>>>>>> appear on the leads action. >>>>>>>> >>>>>>>> >>>>>>>> On 06/12/2013 04:52 AM, Sebastien Blanc wrote: >>>>>>>> >>>>>>>> Ok, there seems to be some agreement on the idea, Nice ! >>>>>>>> Let's focus a bit on the Mobile App. As said before, it must stay >>>>>>>> really simple, so basically that's what the apps does : >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> 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 >>> >>> >>> _______________________________________________ >>> 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 >> >> >> _______________________________________________ >> 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 _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

It will come for sure, we just have to discuss "the planning" ;) Seb On Sat, Jun 15, 2013 at 3:45 PM, Kris Borchers <kborcher(a)redhat.com&gt;wrote: > Maybe I missed off list discussions but is there any reason an "all > inclusive" push demo doesn't include JS (SimplePush) in any of this > discussion? > > On Jun 14, 2013, at 8:53, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: > > Service has been added : > > PUT /leads/{id} > > Update a Lead, typically used if a Sale Agent wants to assign a lead to > him. > > curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" -X PUT -d '{"id":39,"version":0,"name":"Doctor No","location":"New York","phoneNumber":"121212121","saleAgent":"13bbaea3-9271-43f7-80aa-fb21360ff684"}' http://localhost:8080/prodoctor/leads/39 > > returns no data > > > On Fri, Jun 14, 2013 at 3:30 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt;wrote: > >> Exactly ! That is the "public" set needed by the client : login/logout , >> get leads, update location/status >> >> Oh ! I miss one "assign lead to user" , I will update the doc >> Seb >> >> >> >> On Fri, Jun 14, 2013 at 3:25 PM, Matthias Wessendorf <matzew(a)apache.org&gt;wrote: >> >>> nice! >>> >>> that should be enough for the mobile clients, right ? >>> >>> >>> On Fri, Jun 14, 2013 at 3:21 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt;wrote: >>> >>>> Ok, >>>> We got here a first set of services which should be enough for the >>>> demo purposes : >>>> >>>> POST /login >>>> >>>> Login service, mandatory for all further request. >>>> >>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" >>>> -X POST -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/login >>>> >>>> It will return the user : >>>> >>>> {"id":"cb3c05aa-3fdd-4b4e-9b90-386fc7e5671a","enabled":true,"createdDate":1371215851063,"expirationDate":null,"partition":null,"loginName":"john","firstName":null,"lastName":null,"email":null,"status":"PTO","password":"123","location":"New York"} >>>> >>>> POST /logout >>>> >>>> Logout service. >>>> >>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" >>>> -X POST -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/logout >>>> >>>> returns no data >>>> GET /leads >>>> >>>> Obtain a list of leads. >>>> >>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" >>>> -X GET -d '{"loginName": "john", "password":"123"}' http://localhost:8080/prodoctor/leads >>>> >>>> You will get a list of leads : >>>> >>>> [{"id":39,"version":0,"name":"Doctor No","location":"New York","phoneNumber":"0612412121"}] >>>> >>>> PUT /saleagents/{id} >>>> >>>> update a SaleAgent, the service will only update the status and the >>>> location for now. >>>> >>>> curl -v -b cookies.txt -c cookies.txt -H "Accept: application/json" -H "Content-type: application/json" -X PUT -d '{"id":"13bbaea3-9271-43f7-80aa-fb21360ff684","enabled":true,"createdDate":1371213256827,"expirationDate":null,"partition":null,"loginName":"john","firstName":null,"lastName":null,"email":null,"version":0,"status":"CHANGED","password":"123","location":"New York"}' http://localhost:8080/prodoctor/saleagents/13bbaea3-9271-43f7-80aa-fb2136... >>>> >>>> returns no data >>>> >>>> >>>> On Fri, Jun 14, 2013 at 10:21 AM, Matthias Wessendorf < >>>> matzew(a)apache.org&gt; wrote: >>>> >>>>> w00t!!!! >>>>> >>>>> >>>>> On Friday, June 14, 2013, Sebastien Blanc wrote: >>>>> >>>>>> A quick update : >>>>>> >>>>>> A first version of the backend application has been created and be >>>>>> found here >>>>>> https://github.com/sebastienblanc/aerogear-push-quickstart-backend/ >>>>>> You can create Leads, then query for Sale Agents and send them a >>>>>> push notification containing the lead information. >>>>>> >>>>>> The readme contains all the intructions. We made some tests with >>>>>> Matzew yesterday and we were able to send notification from the backend app >>>>>> to an Android Device, using of course, the Push Server : this means we have >>>>>> the complete loop working , yeah ! >>>>>> >>>>>> I will now work on the API of the Prodoctor app that will be used by >>>>>> the Native Clients. >>>>>> >>>>>> Seb >>>>>> >>>>>> >>>>>> >>>>>> On Thu, Jun 13, 2013 at 11:33 AM, Matthias Wessendorf < >>>>>> matzew(a)apache.org&gt; wrote: >>>>>> >>>>>> Repo suggestions: >>>>>> >>>>>> >>>>>> - aerogear-push-quickstart-android >>>>>> - aerogear-push-quickstart-backend >>>>>> - aerogear-push-quickstart-ios >>>>>> >>>>>> >>>>>> >>>>>> JIRA => https://issues.jboss.org/browse/AEROGEAR-1261 >>>>>> >>>>>> >>>>>> >>>>>> On Wed, Jun 12, 2013 at 3:34 PM, Matthias Wessendorf < >>>>>> matzew(a)apache.org&gt; wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Wed, Jun 12, 2013 at 3:29 PM, Summers Pittman < >>>>>> supittma(a)redhat.com&gt; wrote: >>>>>> >>>>>> On 06/12/2013 09:26 AM, Corinne Krych wrote: >>>>>> >>>>>> I like summers idea of replacing the popup when app is open with >>>>>> leads list. >>>>>> If you are in the leads list, the list could be updated but we still >>>>>> need some visual effect to say "new lead" maybe bold font with new icon. >>>>>> >>>>>> In the Google Plus application the refresh button becomes >>>>>> highlighted if there is new data. (As a suggestion). >>>>>> >>>>>> >>>>>> Or... confirm the "popup" and have the list refresh. A color (on the >>>>>> new lead) is fading out :) >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Or we could add the entry and have a special style applied. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On 12 June 2013 15:20, Summers Pittman <supittma(a)redhat.com&gt; wrote: >>>>>> >>>>>> In Android land you wouldn't do a popup. If the app is in the >>>>>> background you would put a notification in the drawer which the user may >>>>>> dismiss or interact with. >>>>>> >>>>>> If you are in the application it would probably be better to update >>>>>> the leads data store and send an update event. If the Leads are being >>>>>> browsed they can be updated. If they aren't then a badge could appear on >>>>>> the leads action. >>>>>> >>>>>> >>>>>> On 06/12/2013 04:52 AM, Sebastien Blanc wrote: >>>>>> >>>>>> Ok, there seems to be some agreement on the idea, Nice ! >>>>>> Let's focus a bit on the Mobile App. As said before, it must stay >>>>>> really simple, so basically that's what the apps does : >>>>>> >>>>>> >>>>> >>>>> -- >>>>> 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 > > > _______________________________________________ > 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 Thu, Jun 13, 2013 at 11:33:12AM +0200, Matthias Wessendorf wrote: > JIRA => https://issues.jboss.org/browse/AEROGEAR-1261 Please assign those to me next time - spent a good time trying to find it :P

-- qmx _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

Sebi, When a sale agent logs in he should see a list of leads with criteria like all lead belonging to him or leads made in his area or just all leads? as the admin user does selective push (with geolocation criteria or other) i wonder if it makes sense to display all leads at initial login. On the other hand if the sale agent got only its lead there is no point to broadcast to others when a lead is accepted. wdyt? On 16 June 2013 11:56, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: On Sun, Jun 16, 2013 at 7:46 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: On Thu, Jun 13, 2013 at 11:33:12AM +0200, Matthias Wessendorf wrote: > JIRA => https://issues.jboss.org/browse/AEROGEAR-1261 Please assign those to me next time - spent a good time trying to find it :P Oh, sorry :) I thought I did that. Added (and reopened) for one more repo request: aerogear-push-quickstart-web Cheers! Matthias -- qmx _______________________________________________ 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

Hi guys, So I see it with 2 tabs: one "in progress leads" with all the leads accepted by the agent logged (default screen) another with "new leads" with all pushed leads unassigned a bubble notification appear on "new leads" tab icon once a lead has been pushed by the admin the sale agent can then accept this lead which then move to the "in progress tab" If another agent accept the lead, the lead should disappear from the "new leads" are you ok with the UI workflow? On 20 June 2013 23:33, Sébastien Blanc <scm.blanc(a)gmail.com&gt; wrote: > Show all leads that have no sale agent id set > > Envoyé de mon iPhone > > Le Jun 20, 2013 à 22:21, Corinne Krych <corinnekrych(a)gmail.com&gt; a écrit : > > Sebi, > > When a sale agent logs in he should see a list of leads with criteria > like all lead belonging to him or leads made in his area or just all leads? > as the admin user does selective push (with geolocation criteria or > other) i wonder if it makes sense to display all leads at initial login. > > On the other hand if the sale agent got only its lead there is no point > to broadcast to others when a lead is accepted. > > wdyt? > > > On 16 June 2013 11:56, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > >> >> >> >> On Sun, Jun 16, 2013 at 7:46 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: >> >>> On Thu, Jun 13, 2013 at 11:33:12AM +0200, Matthias Wessendorf wrote: >>> > JIRA => https://issues.jboss.org/browse/AEROGEAR-1261 >>> >>> Please assign those to me next time - spent a good time trying to find >>> it :P >>> >> >> Oh, sorry :) I thought I did that. Added (and reopened) for one more >> repo request: >> >> - aerogear-push-quickstart-web >> >> >> >> Cheers! >> Matthias >> >> >> >>> >>> -- >>> qmx >>> _______________________________________________ >>> 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 > > > _______________________________________________ > 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 Fri, Jun 21, 2013 at 9:02 AM, Sebastien Blanc <scm.blanc(a)gmail.com&gt;wrote: > I like it but for now there is no service to retrieve leads by > SaleAgents, so we have 2 options : > > - Implement the service (Doh!) > - Store the accepted leads on the device > +1 on device storing (using the AG-DataStore API) > > Seb > > > > On Fri, Jun 21, 2013 at 8:38 AM, Corinne Krych <corinnekrych(a)gmail.com&gt;wrote: > >> Hi guys, >> >> So I see it with 2 tabs: >> one "in progress leads" with all the leads accepted by the agent logged >> (default screen) >> another with "new leads" with all pushed leads unassigned >> >> a bubble notification appear on "new leads" tab icon once a lead has >> been pushed by the admin >> >> the sale agent can then accept this lead which then move to the "in >> progress tab" >> >> If another agent accept the lead, the lead should disappear from the >> "new leads" >> >> are you ok with the UI workflow? >> >> >> On 20 June 2013 23:33, Sébastien Blanc <scm.blanc(a)gmail.com&gt; wrote: >> >>> Show all leads that have no sale agent id set >>> >>> Envoyé de mon iPhone >>> >>> Le Jun 20, 2013 à 22:21, Corinne Krych <corinnekrych(a)gmail.com&gt; a >>> écrit : >>> >>> Sebi, >>> >>> When a sale agent logs in he should see a list of leads with criteria >>> like all lead belonging to him or leads made in his area or just all leads? >>> as the admin user does selective push (with geolocation criteria or >>> other) i wonder if it makes sense to display all leads at initial login. >>> >>> On the other hand if the sale agent got only its lead there is no point >>> to broadcast to others when a lead is accepted. >>> >>> wdyt? >>> >>> >>> On 16 June 2013 11:56, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >>> >>>> >>>> >>>> >>>> On Sun, Jun 16, 2013 at 7:46 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: >>>> >>>>> On Thu, Jun 13, 2013 at 11:33:12AM +0200, Matthias Wessendorf wrote: >>>>> > JIRA => https://issues.jboss.org/browse/AEROGEAR-1261 >>>>> >>>>> Please assign those to me next time - spent a good time trying to find >>>>> it :P >>>>> >>>> >>>> Oh, sorry :) I thought I did that. Added (and reopened) for one more >>>> repo request: >>>> >>>> - aerogear-push-quickstart-web >>>> >>>> >>>> >>>> Cheers! >>>> Matthias >>>> >>>> >>>> >>>>> >>>>> -- >>>>> qmx >>>>> _______________________________________________ >>>>> 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 >>> >>> >>> _______________________________________________ >>> 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 >> > > > _______________________________________________ > 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 Fri, Jun 21, 2013 at 9:20 AM, Corinne Krych <corinnekrych(a)gmail.com&gt;wrote: > if we go go for storing the lead locally in "in progress tab" are we > going to display the leads from local storage then and not the one not > assigned. is that how you see it? > Yes, and that could be a good start for in the future when we will expand the demo with offline and sync (NOT NOW :) ) > > > On 21 June 2013 09:07, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > >> >> >> >> On Fri, Jun 21, 2013 at 9:02 AM, Sebastien Blanc <scm.blanc(a)gmail.com&gt;wrote: >> >>> I like it but for now there is no service to retrieve leads by >>> SaleAgents, so we have 2 options : >>> >>> - Implement the service (Doh!) >>> - Store the accepted leads on the device >>> >> >> +1 on device storing (using the AG-DataStore API) >> >> >>> >>> Seb >>> >>> >>> >>> On Fri, Jun 21, 2013 at 8:38 AM, Corinne Krych <corinnekrych(a)gmail.com&gt;wrote: >>> >>>> Hi guys, >>>> >>>> So I see it with 2 tabs: >>>> one "in progress leads" with all the leads accepted by the agent >>>> logged (default screen) >>>> another with "new leads" with all pushed leads unassigned >>>> >>>> a bubble notification appear on "new leads" tab icon once a lead has >>>> been pushed by the admin >>>> >>>> the sale agent can then accept this lead which then move to the "in >>>> progress tab" >>>> >>>> If another agent accept the lead, the lead should disappear from the >>>> "new leads" >>>> >>>> are you ok with the UI workflow? >>>> >>>> >>>> On 20 June 2013 23:33, Sébastien Blanc <scm.blanc(a)gmail.com&gt; wrote: >>>> >>>>> Show all leads that have no sale agent id set >>>>> >>>>> Envoyé de mon iPhone >>>>> >>>>> Le Jun 20, 2013 à 22:21, Corinne Krych <corinnekrych(a)gmail.com&gt; a >>>>> écrit : >>>>> >>>>> Sebi, >>>>> >>>>> When a sale agent logs in he should see a list of leads with criteria >>>>> like all lead belonging to him or leads made in his area or just all leads? >>>>> as the admin user does selective push (with geolocation criteria or >>>>> other) i wonder if it makes sense to display all leads at initial login. >>>>> >>>>> On the other hand if the sale agent got only its lead there is no >>>>> point to broadcast to others when a lead is accepted. >>>>> >>>>> wdyt? >>>>> >>>>> >>>>> On 16 June 2013 11:56, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Sun, Jun 16, 2013 at 7:46 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: >>>>>> >>>>>>> On Thu, Jun 13, 2013 at 11:33:12AM +0200, Matthias Wessendorf wrote: >>>>>>> > JIRA => https://issues.jboss.org/browse/AEROGEAR-1261 >>>>>>> >>>>>>> Please assign those to me next time - spent a good time trying to >>>>>>> find >>>>>>> it :P >>>>>>> >>>>>> >>>>>> Oh, sorry :) I thought I did that. Added (and reopened) for one more >>>>>> repo request: >>>>>> >>>>>> - aerogear-push-quickstart-web >>>>>> >>>>>> >>>>>> >>>>>> Cheers! >>>>>> Matthias >>>>>> >>>>>> >>>>>> >>>>>>> >>>>>>> -- >>>>>>> qmx >>>>>>> _______________________________________________ >>>>>>> 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 >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>> >>> >>> _______________________________________________ >>> 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 >

So to sum up: 1. Your are a Sale Agent (SA) and you log yourself 2. First screen displayed a list of all unassigned leads retrieved server side (Rest service by default send only unassigned leads) 3. An admin pushes a new lead to a chosen list of SA (including you) 4. You receive the push notification, alert is displayed 5. Your device refresh the list of unassigned leads (server side call). Potentially retrieving also unassigned leads not directly pushed to you. Nice to have feature: The one pushed to you should be highlighted. 6. You accept the lead. The lead is removed from unassigned list and go in Second tab: your accepted list which is stored locally on you device. 7. Nice to have: On acceptation of your lead, you send an update to server. Server side broadcast to all SA (except yourself) to refresh unassigned leads list.

ok for all? Corinne On 21 June 2013 09:41, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: I think I am going to change the GET /leads service to retrieve only unassigned leads rather than a new service On Fri, Jun 21, 2013 at 9:35 AM, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: On Fri, Jun 21, 2013 at 9:20 AM, Corinne Krych <corinnekrych(a)gmail.com&gt; wrote: if we go go for storing the lead locally in "in progress tab" are we going to display the leads from local storage then and not the one not assigned. is that how you see it? Yes, and that could be a good start for in the future when we will expand the demo with offline and sync (NOT NOW :) ) On 21 June 2013 09:07, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: On Fri, Jun 21, 2013 at 9:02 AM, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: I like it but for now there is no service to retrieve leads by SaleAgents, so we have 2 options : - Implement the service (Doh!) - Store the accepted leads on the device +1 on device storing (using the AG-DataStore API) Seb On Fri, Jun 21, 2013 at 8:38 AM, Corinne Krych <corinnekrych(a)gmail.com&gt; wrote: Hi guys, So I see it with 2 tabs: one "in progress leads" with all the leads accepted by the agent logged (default screen) another with "new leads" with all pushed leads unassigned a bubble notification appear on "new leads" tab icon once a lead has been pushed by the admin the sale agent can then accept this lead which then move to the "in progress tab" If another agent accept the lead, the lead should disappear from the "new leads" are you ok with the UI workflow? On 20 June 2013 23:33, Sébastien Blanc <scm.blanc(a)gmail.com&gt; wrote: Show all leads that have no sale agent id set Envoyé de mon iPhone Le Jun 20, 2013 à 22:21, Corinne Krych <corinnekrych(a)gmail.com&gt; a écrit : > Sebi, > > When a sale agent logs in he should see a list of leads with criteria like all lead belonging to him or leads made in his area or just all leads? > as the admin user does selective push (with geolocation criteria or other) i wonder if it makes sense to display all leads at initial login. > > On the other hand if the sale agent got only its lead there is no point to broadcast to others when a lead is accepted. > > wdyt? > > > On 16 June 2013 11:56, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > > > > On Sun, Jun 16, 2013 at 7:46 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: > On Thu, Jun 13, 2013 at 11:33:12AM +0200, Matthias Wessendorf wrote: > > JIRA => https://issues.jboss.org/browse/AEROGEAR-1261 > > Please assign those to me next time - spent a good time trying to find > it :P > > Oh, sorry :) I thought I did that. Added (and reopened) for one more repo request: > aerogear-push-quickstart-web > > > Cheers! > Matthias > > > > -- > qmx > _______________________________________________ > 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 _______________________________________________ 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 _______________________________________________ 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 _______________________________________________ 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 Fri, Jun 21, 2013 at 2:15 PM, Kris Borchers <kris(a)redhat.com&gt; wrote: > I think this all sounds good except see #7 > > On Jun 21, 2013, at 3:11 AM, Corinne Krych <corinnekrych(a)gmail.com&gt; > wrote: > > So to sum up: > > 1. Your are a Sale Agent (SA) and you log yourself > > 2. First screen displayed a list of all unassigned leads retrieved server > side (Rest service by default send only unassigned leads) > > 3. An admin pushes a new lead to a chosen list of SA (including you) > > 4. You receive the push notification, alert is displayed > > 5. Your device refresh the list of unassigned leads (server side call). > Potentially retrieving also unassigned leads not directly pushed to you. > Nice to have feature: The one pushed to you should be highlighted. > > 6. You accept the lead. The lead is removed from unassigned list and go > in Second tab: your accepted list which is stored locally on you device. > > 7. Nice to have: On acceptation of your lead, you send an update to > server. Server side broadcast to all SA (except yourself) to > refresh unassigned leads list. > > I don't think this is a nice to have but a necessity. Otherwise you could > have multiple users trying to assign the same lead. > +1 it also shows a nice integration between all the layers: mobile, backend/business server app, and the PushServer(s) > > > ok for all? > > Corinne > > > On 21 June 2013 09:41, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: > >> I think I am going to change the GET /leads service to retrieve only >> unassigned leads rather than a new service >> >> >> On Fri, Jun 21, 2013 at 9:35 AM, Sebastien Blanc <scm.blanc(a)gmail.com&gt;wrote: >> >>> >>> >>> >>> On Fri, Jun 21, 2013 at 9:20 AM, Corinne Krych <corinnekrych(a)gmail.com&gt;wrote: >>> >>>> if we go go for storing the lead locally in "in progress tab" are we >>>> going to display the leads from local storage then and not the one not >>>> assigned. is that how you see it? >>>> >>> >>> Yes, and that could be a good start for in the future when we will >>> expand the demo with offline and sync (NOT NOW :) ) >>> >>> >>>> >>>> >>>> On 21 June 2013 09:07, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >>>> >>>>> >>>>> >>>>> >>>>> On Fri, Jun 21, 2013 at 9:02 AM, Sebastien Blanc <scm.blanc(a)gmail.com >>>>> > wrote: >>>>> >>>>>> I like it but for now there is no service to retrieve leads by >>>>>> SaleAgents, so we have 2 options : >>>>>> >>>>>> - Implement the service (Doh!) >>>>>> - Store the accepted leads on the device >>>>>> >>>>> >>>>> +1 on device storing (using the AG-DataStore API) >>>>> >>>>> >>>>>> >>>>>> Seb >>>>>> >>>>>> >>>>>> >>>>>> On Fri, Jun 21, 2013 at 8:38 AM, Corinne Krych < >>>>>> corinnekrych(a)gmail.com&gt; wrote: >>>>>> >>>>>>> Hi guys, >>>>>>> >>>>>>> So I see it with 2 tabs: >>>>>>> one "in progress leads" with all the leads accepted by the agent >>>>>>> logged (default screen) >>>>>>> another with "new leads" with all pushed leads unassigned >>>>>>> >>>>>>> a bubble notification appear on "new leads" tab icon once a lead >>>>>>> has been pushed by the admin >>>>>>> >>>>>>> the sale agent can then accept this lead which then move to the "in >>>>>>> progress tab" >>>>>>> >>>>>>> If another agent accept the lead, the lead should disappear from >>>>>>> the "new leads" >>>>>>> >>>>>>> are you ok with the UI workflow? >>>>>>> >>>>>>> >>>>>>> On 20 June 2013 23:33, Sébastien Blanc <scm.blanc(a)gmail.com&gt; wrote: >>>>>>> >>>>>>>> Show all leads that have no sale agent id set >>>>>>>> >>>>>>>> Envoyé de mon iPhone >>>>>>>> >>>>>>>> Le Jun 20, 2013 à 22:21, Corinne Krych <corinnekrych(a)gmail.com&gt; a >>>>>>>> écrit : >>>>>>>> >>>>>>>> Sebi, >>>>>>>> >>>>>>>> When a sale agent logs in he should see a list of leads with >>>>>>>> criteria like all lead belonging to him or leads made in his area or just >>>>>>>> all leads? >>>>>>>> as the admin user does selective push (with geolocation criteria >>>>>>>> or other) i wonder if it makes sense to display all leads at initial login. >>>>>>>> >>>>>>>> On the other hand if the sale agent got only its lead there is no >>>>>>>> point to broadcast to others when a lead is accepted. >>>>>>>> >>>>>>>> wdyt? >>>>>>>> >>>>>>>> >>>>>>>> On 16 June 2013 11:56, Matthias Wessendorf <matzew(a)apache.org&gt;wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Sun, Jun 16, 2013 at 7:46 AM, Douglas Campos <qmx(a)qmx.me&gt;wrote: >>>>>>>>> >>>>>>>>>> On Thu, Jun 13, 2013 at 11:33:12AM +0200, Matthias Wessendorf >>>>>>>>>> wrote: >>>>>>>>>> > JIRA => https://issues.jboss.org/browse/AEROGEAR-1261 >>>>>>>>>> >>>>>>>>>> Please assign those to me next time - spent a good time trying >>>>>>>>>> to find >>>>>>>>>> it :P >>>>>>>>>> >>>>>>>>> >>>>>>>>> Oh, sorry :) I thought I did that. Added (and reopened) for one >>>>>>>>> more repo request: >>>>>>>>> >>>>>>>>> - aerogear-push-quickstart-web >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Cheers! >>>>>>>>> Matthias >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> qmx >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>> >>> >>> >> >> _______________________________________________ >> 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 > > > > _______________________________________________ > 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

Yep, it's a must have ! Don't worry , I think I will update the repo with that today On Fri, Jun 21, 2013 at 2:37 PM, Corinne Krych <corinnekrych(a)gmail.com&gt;wrote: > +1 Kris. Very true. > > > On 21 June 2013 14:18, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > >> >> >> >> On Fri, Jun 21, 2013 at 2:15 PM, Kris Borchers <kris(a)redhat.com&gt; wrote: >> >>> I think this all sounds good except see #7 >>> >>> On Jun 21, 2013, at 3:11 AM, Corinne Krych <corinnekrych(a)gmail.com&gt; >>> wrote: >>> >>> So to sum up: >>> >>> 1. Your are a Sale Agent (SA) and you log yourself >>> >>> 2. First screen displayed a list of all unassigned leads retrieved >>> server side (Rest service by default send only unassigned leads) >>> >>> 3. An admin pushes a new lead to a chosen list of SA (including you) >>> >>> 4. You receive the push notification, alert is displayed >>> >>> 5. Your device refresh the list of unassigned leads (server side call). >>> Potentially retrieving also unassigned leads not directly pushed to you. >>> Nice to have feature: The one pushed to you should be highlighted. >>> >>> 6. You accept the lead. The lead is removed from unassigned list and go >>> in Second tab: your accepted list which is stored locally on you device. >>> >>> 7. Nice to have: On acceptation of your lead, you send an update to >>> server. Server side broadcast to all SA (except yourself) to >>> refresh unassigned leads list. >>> >>> I don't think this is a nice to have but a necessity. Otherwise you >>> could have multiple users trying to assign the same lead. >>> >> >> +1 >> >> it also shows a nice integration between all the layers: mobile, >> backend/business server app, and the PushServer(s) >> >> >> >>> >>> >>> ok for all? >>> >>> Corinne >>> >>> >>> On 21 June 2013 09:41, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: >>> >>>> I think I am going to change the GET /leads service to retrieve only >>>> unassigned leads rather than a new service >>>> >>>> >>>> On Fri, Jun 21, 2013 at 9:35 AM, Sebastien Blanc <scm.blanc(a)gmail.com&gt;wrote: >>>> >>>>> >>>>> >>>>> >>>>> On Fri, Jun 21, 2013 at 9:20 AM, Corinne Krych < >>>>> corinnekrych(a)gmail.com&gt; wrote: >>>>> >>>>>> if we go go for storing the lead locally in "in progress tab" are we >>>>>> going to display the leads from local storage then and not the one not >>>>>> assigned. is that how you see it? >>>>>> >>>>> >>>>> Yes, and that could be a good start for in the future when we will >>>>> expand the demo with offline and sync (NOT NOW :) ) >>>>> >>>>> >>>>>> >>>>>> >>>>>> On 21 June 2013 09:07, Matthias Wessendorf <matzew(a)apache.org&gt;wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Fri, Jun 21, 2013 at 9:02 AM, Sebastien Blanc < >>>>>>> scm.blanc(a)gmail.com&gt; wrote: >>>>>>> >>>>>>>> I like it but for now there is no service to retrieve leads by >>>>>>>> SaleAgents, so we have 2 options : >>>>>>>> >>>>>>>> - Implement the service (Doh!) >>>>>>>> - Store the accepted leads on the device >>>>>>>> >>>>>>> >>>>>>> +1 on device storing (using the AG-DataStore API) >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> Seb >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Jun 21, 2013 at 8:38 AM, Corinne Krych < >>>>>>>> corinnekrych(a)gmail.com&gt; wrote: >>>>>>>> >>>>>>>>> Hi guys, >>>>>>>>> >>>>>>>>> So I see it with 2 tabs: >>>>>>>>> one "in progress leads" with all the leads accepted by the agent >>>>>>>>> logged (default screen) >>>>>>>>> another with "new leads" with all pushed leads unassigned >>>>>>>>> >>>>>>>>> a bubble notification appear on "new leads" tab icon once a lead >>>>>>>>> has been pushed by the admin >>>>>>>>> >>>>>>>>> the sale agent can then accept this lead which then move to the >>>>>>>>> "in progress tab" >>>>>>>>> >>>>>>>>> If another agent accept the lead, the lead should disappear from >>>>>>>>> the "new leads" >>>>>>>>> >>>>>>>>> are you ok with the UI workflow? >>>>>>>>> >>>>>>>>> >>>>>>>>> On 20 June 2013 23:33, Sébastien Blanc <scm.blanc(a)gmail.com&gt;wrote: >>>>>>>>> >>>>>>>>>> Show all leads that have no sale agent id set >>>>>>>>>> >>>>>>>>>> Envoyé de mon iPhone >>>>>>>>>> >>>>>>>>>> Le Jun 20, 2013 à 22:21, Corinne Krych <corinnekrych(a)gmail.com&gt; >>>>>>>>>> a écrit : >>>>>>>>>> >>>>>>>>>> Sebi, >>>>>>>>>> >>>>>>>>>> When a sale agent logs in he should see a list of leads with >>>>>>>>>> criteria like all lead belonging to him or leads made in his area or just >>>>>>>>>> all leads? >>>>>>>>>> as the admin user does selective push (with geolocation criteria >>>>>>>>>> or other) i wonder if it makes sense to display all leads at initial login. >>>>>>>>>> >>>>>>>>>> On the other hand if the sale agent got only its lead there is >>>>>>>>>> no point to broadcast to others when a lead is accepted. >>>>>>>>>> >>>>>>>>>> wdyt? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 16 June 2013 11:56, Matthias Wessendorf <matzew(a)apache.org&gt;wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Sun, Jun 16, 2013 at 7:46 AM, Douglas Campos <qmx(a)qmx.me&gt;wrote: >>>>>>>>>>> >>>>>>>>>>>> On Thu, Jun 13, 2013 at 11:33:12AM +0200, Matthias Wessendorf >>>>>>>>>>>> wrote: >>>>>>>>>>>> > JIRA => https://issues.jboss.org/browse/AEROGEAR-1261 >>>>>>>>>>>> >>>>>>>>>>>> Please assign those to me next time - spent a good time trying >>>>>>>>>>>> to find >>>>>>>>>>>> it :P >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Oh, sorry :) I thought I did that. Added (and reopened) for one >>>>>>>>>>> more repo request: >>>>>>>>>>> >>>>>>>>>>> - aerogear-push-quickstart-web >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Cheers! >>>>>>>>>>> Matthias >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> qmx >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> 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 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>> >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> 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 >>> >>> >>> >>> _______________________________________________ >>> 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 >

it's only visible on Android and iOS :-) I'd vote for {"alert" : "A new lead has been created"} (something like that, in a more proper English :)) On Fri, Jun 21, 2013 at 3:31 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt;wrote: > To all the Clients devs : > I need to know what you want to receive in the alert field of the push > message : All is possible , just scream your wishes ! > > > > On Fri, Jun 21, 2013 at 2:58 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt;wrote: > >> Yep, it's a must have ! Don't worry , I think I will update the repo >> with that today >> >> >> >> On Fri, Jun 21, 2013 at 2:37 PM, Corinne Krych <corinnekrych(a)gmail.com&gt;wrote: >> >>> +1 Kris. Very true. >>> >>> >>> On 21 June 2013 14:18, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >>> >>>> >>>> >>>> >>>> On Fri, Jun 21, 2013 at 2:15 PM, Kris Borchers <kris(a)redhat.com&gt;wrote: >>>> >>>>> I think this all sounds good except see #7 >>>>> >>>>> On Jun 21, 2013, at 3:11 AM, Corinne Krych <corinnekrych(a)gmail.com&gt; >>>>> wrote: >>>>> >>>>> So to sum up: >>>>> >>>>> 1. Your are a Sale Agent (SA) and you log yourself >>>>> >>>>> 2. First screen displayed a list of all unassigned leads retrieved >>>>> server side (Rest service by default send only unassigned leads) >>>>> >>>>> 3. An admin pushes a new lead to a chosen list of SA (including you) >>>>> >>>>> 4. You receive the push notification, alert is displayed >>>>> >>>>> 5. Your device refresh the list of unassigned leads (server side >>>>> call). Potentially retrieving also unassigned leads not directly pushed to >>>>> you. Nice to have feature: The one pushed to you should be highlighted. >>>>> >>>>> 6. You accept the lead. The lead is removed from unassigned list and >>>>> go in Second tab: your accepted list which is stored locally on you device. >>>>> >>>>> 7. Nice to have: On acceptation of your lead, you send an update to >>>>> server. Server side broadcast to all SA (except yourself) to >>>>> refresh unassigned leads list. >>>>> >>>>> I don't think this is a nice to have but a necessity. Otherwise you >>>>> could have multiple users trying to assign the same lead. >>>>> >>>> >>>> +1 >>>> >>>> it also shows a nice integration between all the layers: mobile, >>>> backend/business server app, and the PushServer(s) >>>> >>>> >>>> >>>>> >>>>> >>>>> ok for all? >>>>> >>>>> Corinne >>>>> >>>>> >>>>> On 21 June 2013 09:41, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: >>>>> >>>>>> I think I am going to change the GET /leads service to retrieve only >>>>>> unassigned leads rather than a new service >>>>>> >>>>>> >>>>>> On Fri, Jun 21, 2013 at 9:35 AM, Sebastien Blanc < >>>>>> scm.blanc(a)gmail.com&gt; wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Fri, Jun 21, 2013 at 9:20 AM, Corinne Krych < >>>>>>> corinnekrych(a)gmail.com&gt; wrote: >>>>>>> >>>>>>>> if we go go for storing the lead locally in "in progress tab" are >>>>>>>> we going to display the leads from local storage then and not the one not >>>>>>>> assigned. is that how you see it? >>>>>>>> >>>>>>> >>>>>>> Yes, and that could be a good start for in the future when we will >>>>>>> expand the demo with offline and sync (NOT NOW :) ) >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On 21 June 2013 09:07, Matthias Wessendorf <matzew(a)apache.org&gt;wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Fri, Jun 21, 2013 at 9:02 AM, Sebastien Blanc < >>>>>>>>> scm.blanc(a)gmail.com&gt; wrote: >>>>>>>>> >>>>>>>>>> I like it but for now there is no service to retrieve leads by >>>>>>>>>> SaleAgents, so we have 2 options : >>>>>>>>>> >>>>>>>>>> - Implement the service (Doh!) >>>>>>>>>> - Store the accepted leads on the device >>>>>>>>>> >>>>>>>>> >>>>>>>>> +1 on device storing (using the AG-DataStore API) >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> Seb >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Fri, Jun 21, 2013 at 8:38 AM, Corinne Krych < >>>>>>>>>> corinnekrych(a)gmail.com&gt; wrote: >>>>>>>>>> >>>>>>>>>>> Hi guys, >>>>>>>>>>> >>>>>>>>>>> So I see it with 2 tabs: >>>>>>>>>>> one "in progress leads" with all the leads accepted by the >>>>>>>>>>> agent logged (default screen) >>>>>>>>>>> another with "new leads" with all pushed leads unassigned >>>>>>>>>>> >>>>>>>>>>> a bubble notification appear on "new leads" tab icon once a >>>>>>>>>>> lead has been pushed by the admin >>>>>>>>>>> >>>>>>>>>>> the sale agent can then accept this lead which then move to the >>>>>>>>>>> "in progress tab" >>>>>>>>>>> >>>>>>>>>>> If another agent accept the lead, the lead should disappear >>>>>>>>>>> from the "new leads" >>>>>>>>>>> >>>>>>>>>>> are you ok with the UI workflow? >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On 20 June 2013 23:33, Sébastien Blanc <scm.blanc(a)gmail.com&gt;wrote: >>>>>>>>>>> >>>>>>>>>>>> Show all leads that have no sale agent id set >>>>>>>>>>>> >>>>>>>>>>>> Envoyé de mon iPhone >>>>>>>>>>>> >>>>>>>>>>>> Le Jun 20, 2013 à 22:21, Corinne Krych <corinnekrych(a)gmail.com&gt; >>>>>>>>>>>> a écrit : >>>>>>>>>>>> >>>>>>>>>>>> Sebi, >>>>>>>>>>>> >>>>>>>>>>>> When a sale agent logs in he should see a list of leads with >>>>>>>>>>>> criteria like all lead belonging to him or leads made in his area or just >>>>>>>>>>>> all leads? >>>>>>>>>>>> as the admin user does selective push (with geolocation >>>>>>>>>>>> criteria or other) i wonder if it makes sense to display all leads at >>>>>>>>>>>> initial login. >>>>>>>>>>>> >>>>>>>>>>>> On the other hand if the sale agent got only its lead there is >>>>>>>>>>>> no point to broadcast to others when a lead is accepted. >>>>>>>>>>>> >>>>>>>>>>>> wdyt? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On 16 June 2013 11:56, Matthias Wessendorf <matzew(a)apache.org&gt;wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Sun, Jun 16, 2013 at 7:46 AM, Douglas Campos <qmx(a)qmx.me&gt;wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> On Thu, Jun 13, 2013 at 11:33:12AM +0200, Matthias >>>>>>>>>>>>>> Wessendorf wrote: >>>>>>>>>>>>>> > JIRA => https://issues.jboss.org/browse/AEROGEAR-1261 >>>>>>>>>>>>>> >>>>>>>>>>>>>> Please assign those to me next time - spent a good time >>>>>>>>>>>>>> trying to find >>>>>>>>>>>>>> it :P >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Oh, sorry :) I thought I did that. Added (and reopened) for >>>>>>>>>>>>> one more repo request: >>>>>>>>>>>>> >>>>>>>>>>>>> - aerogear-push-quickstart-web >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Cheers! >>>>>>>>>>>>> Matthias >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> qmx >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> 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 >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >> >> > > _______________________________________________ > 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

Good point Corinne ! Let me change that ! On Fri, Jun 21, 2013 at 5:03 PM, Corinne Krych <corinnekrych(a)gmail.com&gt;wrote: > I would like {"alert" : "Lead <name> available"} > > as the admin can create a lead and not push it. The lead can get pushed > later (after creation) > Beside if the SA has dismissed the lead, admin can decide to push it > again to SA. > > > On 21 June 2013 15:34, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > >> it's only visible on Android and iOS :-) >> >> I'd vote for {"alert" : "A new lead has been created"} >> >> (something like that, in a more proper English :)) >> >> >> On Fri, Jun 21, 2013 at 3:31 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt;wrote: >> >>> To all the Clients devs : >>> I need to know what you want to receive in the alert field of the push >>> message : All is possible , just scream your wishes ! >>> >>> >>> >>> On Fri, Jun 21, 2013 at 2:58 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt;wrote: >>> >>>> Yep, it's a must have ! Don't worry , I think I will update the repo >>>> with that today >>>> >>>> >>>> >>>> On Fri, Jun 21, 2013 at 2:37 PM, Corinne Krych <corinnekrych(a)gmail.com >>>> > wrote: >>>> >>>>> +1 Kris. Very true. >>>>> >>>>> >>>>> On 21 June 2013 14:18, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Fri, Jun 21, 2013 at 2:15 PM, Kris Borchers <kris(a)redhat.com&gt;wrote: >>>>>> >>>>>>> I think this all sounds good except see #7 >>>>>>> >>>>>>> On Jun 21, 2013, at 3:11 AM, Corinne Krych <corinnekrych(a)gmail.com&gt; >>>>>>> wrote: >>>>>>> >>>>>>> So to sum up: >>>>>>> >>>>>>> 1. Your are a Sale Agent (SA) and you log yourself >>>>>>> >>>>>>> 2. First screen displayed a list of all unassigned leads retrieved >>>>>>> server side (Rest service by default send only unassigned leads) >>>>>>> >>>>>>> 3. An admin pushes a new lead to a chosen list of SA (including you) >>>>>>> >>>>>>> 4. You receive the push notification, alert is displayed >>>>>>> >>>>>>> 5. Your device refresh the list of unassigned leads (server side >>>>>>> call). Potentially retrieving also unassigned leads not directly pushed to >>>>>>> you. Nice to have feature: The one pushed to you should be highlighted. >>>>>>> >>>>>>> 6. You accept the lead. The lead is removed from unassigned list >>>>>>> and go in Second tab: your accepted list which is stored locally on you >>>>>>> device. >>>>>>> >>>>>>> 7. Nice to have: On acceptation of your lead, you send an update to >>>>>>> server. Server side broadcast to all SA (except yourself) to >>>>>>> refresh unassigned leads list. >>>>>>> >>>>>>> I don't think this is a nice to have but a necessity. Otherwise you >>>>>>> could have multiple users trying to assign the same lead. >>>>>>> >>>>>> >>>>>> +1 >>>>>> >>>>>> it also shows a nice integration between all the layers: mobile, >>>>>> backend/business server app, and the PushServer(s) >>>>>> >>>>>> >>>>>> >>>>>>> >>>>>>> >>>>>>> ok for all? >>>>>>> >>>>>>> Corinne >>>>>>> >>>>>>> >>>>>>> On 21 June 2013 09:41, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: >>>>>>> >>>>>>>> I think I am going to change the GET /leads service to retrieve >>>>>>>> only unassigned leads rather than a new service >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Jun 21, 2013 at 9:35 AM, Sebastien Blanc < >>>>>>>> scm.blanc(a)gmail.com&gt; wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Fri, Jun 21, 2013 at 9:20 AM, Corinne Krych < >>>>>>>>> corinnekrych(a)gmail.com&gt; wrote: >>>>>>>>> >>>>>>>>>> if we go go for storing the lead locally in "in progress tab" >>>>>>>>>> are we going to display the leads from local storage then and not the one >>>>>>>>>> not assigned. is that how you see it? >>>>>>>>>> >>>>>>>>> >>>>>>>>> Yes, and that could be a good start for in the future when we >>>>>>>>> will expand the demo with offline and sync (NOT NOW :) ) >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 21 June 2013 09:07, Matthias Wessendorf <matzew(a)apache.org&gt;wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Fri, Jun 21, 2013 at 9:02 AM, Sebastien Blanc < >>>>>>>>>>> scm.blanc(a)gmail.com&gt; wrote: >>>>>>>>>>> >>>>>>>>>>>> I like it but for now there is no service to retrieve leads by >>>>>>>>>>>> SaleAgents, so we have 2 options : >>>>>>>>>>>> >>>>>>>>>>>> - Implement the service (Doh!) >>>>>>>>>>>> - Store the accepted leads on the device >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> +1 on device storing (using the AG-DataStore API) >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Seb >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Fri, Jun 21, 2013 at 8:38 AM, Corinne Krych < >>>>>>>>>>>> corinnekrych(a)gmail.com&gt; wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi guys, >>>>>>>>>>>>> >>>>>>>>>>>>> So I see it with 2 tabs: >>>>>>>>>>>>> one "in progress leads" with all the leads accepted by the >>>>>>>>>>>>> agent logged (default screen) >>>>>>>>>>>>> another with "new leads" with all pushed leads unassigned >>>>>>>>>>>>> >>>>>>>>>>>>> a bubble notification appear on "new leads" tab icon once a >>>>>>>>>>>>> lead has been pushed by the admin >>>>>>>>>>>>> >>>>>>>>>>>>> the sale agent can then accept this lead which then move to >>>>>>>>>>>>> the "in progress tab" >>>>>>>>>>>>> >>>>>>>>>>>>> If another agent accept the lead, the lead should disappear >>>>>>>>>>>>> from the "new leads" >>>>>>>>>>>>> >>>>>>>>>>>>> are you ok with the UI workflow? >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On 20 June 2013 23:33, Sébastien Blanc <scm.blanc(a)gmail.com&gt;wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Show all leads that have no sale agent id set >>>>>>>>>>>>>> >>>>>>>>>>>>>> Envoyé de mon iPhone >>>>>>>>>>>>>> >>>>>>>>>>>>>> Le Jun 20, 2013 à 22:21, Corinne Krych < >>>>>>>>>>>>>> corinnekrych(a)gmail.com&gt; a écrit : >>>>>>>>>>>>>> >>>>>>>>>>>>>> Sebi, >>>>>>>>>>>>>> >>>>>>>>>>>>>> When a sale agent logs in he should see a list of leads with >>>>>>>>>>>>>> criteria like all lead belonging to him or leads made in his area or just >>>>>>>>>>>>>> all leads? >>>>>>>>>>>>>> as the admin user does selective push (with geolocation >>>>>>>>>>>>>> criteria or other) i wonder if it makes sense to display all leads at >>>>>>>>>>>>>> initial login. >>>>>>>>>>>>>> >>>>>>>>>>>>>> On the other hand if the sale agent got only its lead there >>>>>>>>>>>>>> is no point to broadcast to others when a lead is accepted. >>>>>>>>>>>>>> >>>>>>>>>>>>>> wdyt? >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On 16 June 2013 11:56, Matthias Wessendorf < >>>>>>>>>>>>>> matzew(a)apache.org&gt; wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Sun, Jun 16, 2013 at 7:46 AM, Douglas Campos <qmx(a)qmx.me >>>>>>>>>>>>>>> > wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Thu, Jun 13, 2013 at 11:33:12AM +0200, Matthias >>>>>>>>>>>>>>>> Wessendorf wrote: >>>>>>>>>>>>>>>> > JIRA => https://issues.jboss.org/browse/AEROGEAR-1261 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Please assign those to me next time - spent a good time >>>>>>>>>>>>>>>> trying to find >>>>>>>>>>>>>>>> it :P >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Oh, sorry :) I thought I did that. Added (and reopened) for >>>>>>>>>>>>>>> one more repo request: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> - aerogear-push-quickstart-web >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Cheers! >>>>>>>>>>>>>>> Matthias >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> qmx >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> 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 >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> 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 >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>> >>>> >>>> >>> >>> _______________________________________________ >>> 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 >

+1 On 21 June 2013 17:08, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: > > http://github.com/aerogear/aerogear-push-quickstart-backend/commit/5be6e725f > > I've also updated the broadcast message to {"alert" : "Lead <name> has > been accepted"} > > > > On Fri, Jun 21, 2013 at 5:05 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt;wrote: > >> Good point Corinne ! Let me change that ! >> >> >> >> On Fri, Jun 21, 2013 at 5:03 PM, Corinne Krych <corinnekrych(a)gmail.com&gt;wrote: >> >>> I would like {"alert" : "Lead <name> available"} >>> >>> as the admin can create a lead and not push it. The lead can get pushed >>> later (after creation) >>> Beside if the SA has dismissed the lead, admin can decide to push it >>> again to SA. >>> >>> >>> On 21 June 2013 15:34, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >>> >>>> it's only visible on Android and iOS :-) >>>> >>>> I'd vote for {"alert" : "A new lead has been created"} >>>> >>>> (something like that, in a more proper English :)) >>>> >>>> >>>> On Fri, Jun 21, 2013 at 3:31 PM, Sebastien Blanc <scm.blanc(a)gmail.com&gt;wrote: >>>> >>>>> To all the Clients devs : >>>>> I need to know what you want to receive in the alert field of the >>>>> push message : All is possible , just scream your wishes ! >>>>> >>>>> >>>>> >>>>> On Fri, Jun 21, 2013 at 2:58 PM, Sebastien Blanc <scm.blanc(a)gmail.com >>>>> > wrote: >>>>> >>>>>> Yep, it's a must have ! Don't worry , I think I will update the repo >>>>>> with that today >>>>>> >>>>>> >>>>>> >>>>>> On Fri, Jun 21, 2013 at 2:37 PM, Corinne Krych < >>>>>> corinnekrych(a)gmail.com&gt; wrote: >>>>>> >>>>>>> +1 Kris. Very true. >>>>>>> >>>>>>> >>>>>>> On 21 June 2013 14:18, Matthias Wessendorf <matzew(a)apache.org&gt;wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Jun 21, 2013 at 2:15 PM, Kris Borchers <kris(a)redhat.com&gt;wrote: >>>>>>>> >>>>>>>>> I think this all sounds good except see #7 >>>>>>>>> >>>>>>>>> On Jun 21, 2013, at 3:11 AM, Corinne Krych < >>>>>>>>> corinnekrych(a)gmail.com&gt; wrote: >>>>>>>>> >>>>>>>>> So to sum up: >>>>>>>>> >>>>>>>>> 1. Your are a Sale Agent (SA) and you log yourself >>>>>>>>> >>>>>>>>> 2. First screen displayed a list of all unassigned leads >>>>>>>>> retrieved server side (Rest service by default send only unassigned leads) >>>>>>>>> >>>>>>>>> 3. An admin pushes a new lead to a chosen list of SA (including >>>>>>>>> you) >>>>>>>>> >>>>>>>>> 4. You receive the push notification, alert is displayed >>>>>>>>> >>>>>>>>> 5. Your device refresh the list of unassigned leads (server side >>>>>>>>> call). Potentially retrieving also unassigned leads not directly pushed to >>>>>>>>> you. Nice to have feature: The one pushed to you should be highlighted. >>>>>>>>> >>>>>>>>> 6. You accept the lead. The lead is removed from unassigned list >>>>>>>>> and go in Second tab: your accepted list which is stored locally on you >>>>>>>>> device. >>>>>>>>> >>>>>>>>> 7. Nice to have: On acceptation of your lead, you send an update >>>>>>>>> to server. Server side broadcast to all SA (except yourself) to >>>>>>>>> refresh unassigned leads list. >>>>>>>>> >>>>>>>>> I don't think this is a nice to have but a necessity. Otherwise >>>>>>>>> you could have multiple users trying to assign the same lead. >>>>>>>>> >>>>>>>> >>>>>>>> +1 >>>>>>>> >>>>>>>> it also shows a nice integration between all the layers: mobile, >>>>>>>> backend/business server app, and the PushServer(s) >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> ok for all? >>>>>>>>> >>>>>>>>> Corinne >>>>>>>>> >>>>>>>>> >>>>>>>>> On 21 June 2013 09:41, Sebastien Blanc <scm.blanc(a)gmail.com&gt;wrote: >>>>>>>>> >>>>>>>>>> I think I am going to change the GET /leads service to retrieve >>>>>>>>>> only unassigned leads rather than a new service >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Fri, Jun 21, 2013 at 9:35 AM, Sebastien Blanc < >>>>>>>>>> scm.blanc(a)gmail.com&gt; wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Fri, Jun 21, 2013 at 9:20 AM, Corinne Krych < >>>>>>>>>>> corinnekrych(a)gmail.com&gt; wrote: >>>>>>>>>>> >>>>>>>>>>>> if we go go for storing the lead locally in "in progress tab" >>>>>>>>>>>> are we going to display the leads from local storage then and not the one >>>>>>>>>>>> not assigned. is that how you see it? >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Yes, and that could be a good start for in the future when we >>>>>>>>>>> will expand the demo with offline and sync (NOT NOW :) ) >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On 21 June 2013 09:07, Matthias Wessendorf <matzew(a)apache.org&gt;wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Fri, Jun 21, 2013 at 9:02 AM, Sebastien Blanc < >>>>>>>>>>>>> scm.blanc(a)gmail.com&gt; wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> I like it but for now there is no service to retrieve leads >>>>>>>>>>>>>> by SaleAgents, so we have 2 options : >>>>>>>>>>>>>> >>>>>>>>>>>>>> - Implement the service (Doh!) >>>>>>>>>>>>>> - Store the accepted leads on the device >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> +1 on device storing (using the AG-DataStore API) >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Seb >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Fri, Jun 21, 2013 at 8:38 AM, Corinne Krych < >>>>>>>>>>>>>> corinnekrych(a)gmail.com&gt; wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Hi guys, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> So I see it with 2 tabs: >>>>>>>>>>>>>>> one "in progress leads" with all the leads accepted by the >>>>>>>>>>>>>>> agent logged (default screen) >>>>>>>>>>>>>>> another with "new leads" with all pushed leads unassigned >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> a bubble notification appear on "new leads" tab icon once a >>>>>>>>>>>>>>> lead has been pushed by the admin >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> the sale agent can then accept this lead which then move to >>>>>>>>>>>>>>> the "in progress tab" >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> If another agent accept the lead, the lead should disappear >>>>>>>>>>>>>>> from the "new leads" >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> are you ok with the UI workflow? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On 20 June 2013 23:33, Sébastien Blanc <scm.blanc(a)gmail.com >>>>>>>>>>>>>>> > wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Show all leads that have no sale agent id set >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Envoyé de mon iPhone >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Le Jun 20, 2013 à 22:21, Corinne Krych < >>>>>>>>>>>>>>>> corinnekrych(a)gmail.com&gt; a écrit : >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Sebi, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> When a sale agent logs in he should see a list of leads >>>>>>>>>>>>>>>> with criteria like all lead belonging to him or leads made in his area or >>>>>>>>>>>>>>>> just all leads? >>>>>>>>>>>>>>>> as the admin user does selective push (with geolocation >>>>>>>>>>>>>>>> criteria or other) i wonder if it makes sense to display all leads at >>>>>>>>>>>>>>>> initial login. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On the other hand if the sale agent got only its lead >>>>>>>>>>>>>>>> there is no point to broadcast to others when a lead is accepted. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> wdyt? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On 16 June 2013 11:56, Matthias Wessendorf < >>>>>>>>>>>>>>>> matzew(a)apache.org&gt; wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Sun, Jun 16, 2013 at 7:46 AM, Douglas Campos < >>>>>>>>>>>>>>>>> qmx(a)qmx.me&gt; wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Thu, Jun 13, 2013 at 11:33:12AM +0200, Matthias >>>>>>>>>>>>>>>>>> Wessendorf wrote: >>>>>>>>>>>>>>>>>> > JIRA => https://issues.jboss.org/browse/AEROGEAR-1261 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Please assign those to me next time - spent a good time >>>>>>>>>>>>>>>>>> trying to find >>>>>>>>>>>>>>>>>> it :P >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Oh, sorry :) I thought I did that. Added (and reopened) >>>>>>>>>>>>>>>>> for one more repo request: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> - aerogear-push-quickstart-web >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Cheers! >>>>>>>>>>>>>>>>> Matthias >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>> qmx >>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> 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 >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>> >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >> >> > > _______________________________________________ > 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

I like it but for now there is no service to retrieve leads by SaleAgents, so we have 2 options : - Implement the service (Doh!) - Store the accepted leads on the device Seb On Fri, Jun 21, 2013 at 8:38 AM, Corinne Krych <corinnekrych(a)gmail.com&gt;wrote: > Hi guys, > > So I see it with 2 tabs: > one "in progress leads" with all the leads accepted by the agent logged > (default screen) > another with "new leads" with all pushed leads unassigned > > a bubble notification appear on "new leads" tab icon once a lead has been > pushed by the admin > > the sale agent can then accept this lead which then move to the "in > progress tab" > > If another agent accept the lead, the lead should disappear from the "new > leads" > > are you ok with the UI workflow? > > > On 20 June 2013 23:33, Sébastien Blanc <scm.blanc(a)gmail.com&gt; wrote: > >> Show all leads that have no sale agent id set >> >> Envoyé de mon iPhone >> >> Le Jun 20, 2013 à 22:21, Corinne Krych <corinnekrych(a)gmail.com&gt; a >> écrit : >> >> Sebi, >> >> When a sale agent logs in he should see a list of leads with criteria >> like all lead belonging to him or leads made in his area or just all leads? >> as the admin user does selective push (with geolocation criteria or >> other) i wonder if it makes sense to display all leads at initial login. >> >> On the other hand if the sale agent got only its lead there is no point >> to broadcast to others when a lead is accepted. >> >> wdyt? >> >> >> On 16 June 2013 11:56, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >> >>> >>> >>> >>> On Sun, Jun 16, 2013 at 7:46 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: >>> >>>> On Thu, Jun 13, 2013 at 11:33:12AM +0200, Matthias Wessendorf wrote: >>>> > JIRA => https://issues.jboss.org/browse/AEROGEAR-1261 >>>> >>>> Please assign those to me next time - spent a good time trying to find >>>> it :P >>>> >>> >>> Oh, sorry :) I thought I did that. Added (and reopened) for one more >>> repo request: >>> >>> - aerogear-push-quickstart-web >>> >>> >>> >>> Cheers! >>> Matthias >>> >>> >>> >>>> >>>> -- >>>> qmx >>>> _______________________________________________ >>>> 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 >> >> >> _______________________________________________ >> 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 > _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

Hey ! We would like to provide, in a quite short delay (coming 2 weeks) a demo showing all the different bits of the "push" world , meaning : client | push server | JEE Backend App We already have the push server (aerogear-unified-push-server) : so we need a client (iOS and maybe also Android) and a simple JEE backend application. The backend app will mostly be scaffolded and will use the aerogear-unified-push-java-client to send messages to the Push Server. Then of course, we need to think about an idea of the application itself. It needs to stay really simple, show how we can send selectively and should be a bit "business" related. So, I came up with an idea this morning that we can discuss here, of course if you have any other idea don't hesitate to share it. Push Demo Introduction Prodoctor is a company in the health care industry, selling a revolutionary tensiometer. Their clients are doctors. Prodoctor has several sales agents all over the United States. At the headquarters, they have their "first line" sales department doing cold calls all along the day. As soon they have a concrete lead, they use their Prodoctor Admin app to filter out available sales Agents available in the lead area. They can then send them a push notification. The sales agent receives the notification on their mobile device that a new lead is available. The agent will handle the lead by "accepting" the notification informing the other agents that the lead has been processed. The client app The client consist of a list of leads : a lead can be "open" or "in process", leads "in process" of other sales are not visible. optional : when the client tap a lead it appears on a map The client has a status that he can set: STANDBY | WITH_CLIENT |PTO The client has a location The client has an alias Prodoctor Admin client The admin client can create a new lead : A lead consist of a name and a location The admin client can query for Sales Agents based on : Status Location The admin client can assign a lead to a selection (1..n) of sales agents, this will send out the notifications. The admin client manage the Sales Agents DB. _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

Hi, Thanks for the feedback Some comments inline On Mon, Jun 24, 2013 at 6:28 AM, Deepali Khushraj <dkhushra(a)redhat.com&gt;wrote: > Overall the scenario sounds good. > > A few comments: > > *Terminology: *Although leads can be manually assigned, most CRM systems > have auto-lead assignment based on the criteria of the leads. The admin in > these systems is usually creating the rules of assignment, rather than > manually assigning leads. Related suggestions: > * instead of making a distinction between "admin client" and "client app", > we could consider them as two versions of the same app - desktop Vs mobile. > * typically the distinction on who can do what is based on the user role, > rather than "admin" rights. Therefore, I'd suggest renaming "admin client" > to exclude the word "admin". Perhaps call this person a "sales lead" or > something. > Thanks, for the terminology precisions, makes sense. Concerning, the auto-lead assignement, I like the idea and as you said it seems to reflect more the reality. I will think on how that add this but I don't think it will be present in the very first version.

> > *Pitch:* IMO, this demo motivates the fact that Prodoctor is able to use > push notifications to ensure potential customers get immediate attention > from sales. For example, if a sales agent is at a conference, and a > potential lead came from a customer at the same conference, the SA is > immediately notified and could utilize the opportunity to meet with the > customer in person to show a demo. Talking about the end-effect of such a > notification would be good. > Exactly ! that was a bit the conclusion in my "introduction" section : "In this highly competitive market of the tensiometers, be able to process a lead directly is for sure a competitve advantage." But I like your pitch and I will add it to the readme. > > *Related Scenario: *A related scenario for future. Push notifications to > get immediate approval of discount requests to close "opportunities" (a > lead is typically converted into an "opportunity", once it's established to > have potential for a sale). For example, a SA could get immediate approval > for a discounted rate, from the division head, while interacting with the > customer to ensure the opportunity is converted to a sale. > Really interesting > > D. > > On Jun 11, 2013, at 10:45 AM, Sebastien Blanc <scm.blanc(a)gmail.com&gt; wrote: > > Hey ! > We would like to provide, in a quite short delay (coming 2 weeks) a demo > showing all the different bits of the "push" world , meaning : > client | push server | JEE Backend App > > We already have the push server (aerogear-unified-push-server) : so we > need a client (iOS and maybe also Android) and a simple JEE backend > application. The backend app will mostly be scaffolded and will use the > aerogear-unified-push-java-client to send messages to the Push Server. > > Then of course, we need to think about an idea of the application itself. > It needs to stay really simple, show how we can send selectively and > should be a bit "business" related. > > So, I came up with an idea this morning that we can discuss here, of > course if you have any other idea don't hesitate to share it. > > Push Demo <https://gist.github.com/sebastienblanc/5755548#introduction> > Introduction > > Prodoctor is a company in the health care industry, selling a > revolutionary tensiometer. Their clients are doctors. Prodoctor has several > sales agents all over the United States. At the headquarters, they have > their "first line" sales department doing cold calls all along the day. > As soon they have a concrete lead, they use their Prodoctor Admin app to > filter out available sales Agents available in the lead area. They can then > send them a push notification. > > The sales agent receives the notification on their mobile device that a > new lead is available. The agent will handle the lead by "accepting" the > notification informing the other agents that the lead has been processed. > <https://gist.github.com/sebastienblanc/5755548#the-client-app>The > client app > > 1. The client consist of a list of leads : a lead can be "open" or "in > process", leads "in process" of other sales are not visible. > > > - optional : when the client tap a lead it appears on a map > > > 1. The client has a status that he can set: STANDBY | WITH_CLIENT |PTO > 2. The client has a location > 3. The client has an alias > > <https://gist.github.com/sebastienblanc/5755548#prodoctor-admin-client>... > Admin client > > 1. The admin client can create a new lead : > > > - A lead consist of a name and a location > > > 1. The admin client can query for Sales Agents based on : > > > - Status > - Location > > > 1. > > The admin client can assign a lead to a selection (1..n) of sales > agents, this will send out the notifications. > 2. > > The admin client manage the Sales Agents DB. > > _______________________________________________ > > 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 >