[aerogear-dev] Push "all inclusive" demo

Sebastien Blanc scm.blanc at gmail.com
Fri Jun 21 11:41:54 EDT 2013 

Ok, just a quick end-of-week sum up :
First good news : We managed to have both ios, android and web scenarios
working, meaning being able to send a push message from an "independent"
JEE app to the different devices  using unified-push-server and
simple-push-server \o/

Backend "prodoctor" : I had a lot of feedback and it should  be pretty
"stable" enough for the demo. Thanks Corinne for having detailed the flow
of the app (
https://github.com/aerogear/aerogear-push-quickstart-backend#general-flow )

Clients :

- ios  : Corinne is doing great progress, will be awesome , I'm sure

- android : Daniel has been doing a lot of efforts as well, the app is
almost done

- web : well, there is nothing yet in the official repo but on
https://github.com/aerogear/aerogear-push-quickstart-backend/tree/client and
by browsing to /prodoctor/client you will have a first preview of the work.
Basically, the client connects to the simple push server, when a lead is
pushed, the clients will automatically fire a refresh of the leads list.

We still have to discuss some points like :
- being sure how the device registration is going (passing the alias only
the first time etc ...)
- use case polishing
- Documentation

As usual, all the repos are on github, so if you have the killing
fix/feature , just push your PR !

Seb







On Fri, Jun 21, 2013 at 5:13 PM, Corinne Krych <corinnekrych at gmail.com>wrote:

> +1
>
>
> On 21 June 2013 17:08, Sebastien Blanc <scm.blanc at gmail.com> 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 at gmail.com>wrote:
>>
>>> Good point Corinne ! Let me change that !
>>>
>>>
>>>
>>> On Fri, Jun 21, 2013 at 5:03 PM, Corinne Krych <corinnekrych at gmail.com>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 at apache.org> 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 at gmail.com>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 at 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 at gmail.com> wrote:
>>>>>>>
>>>>>>>> +1 Kris. Very true.
>>>>>>>>
>>>>>>>>
>>>>>>>> On 21 June 2013 14:18, Matthias Wessendorf <matzew at apache.org>wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Fri, Jun 21, 2013 at 2:15 PM, Kris Borchers <kris at redhat.com>wrote:
>>>>>>>>>
>>>>>>>>>> I think this all sounds good except see #7
>>>>>>>>>>
>>>>>>>>>> On Jun 21, 2013, at 3:11 AM, Corinne Krych <
>>>>>>>>>> corinnekrych at gmail.com> 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 at gmail.com>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 at gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Jun 21, 2013 at 9:20 AM, Corinne Krych <
>>>>>>>>>>>> corinnekrych at gmail.com> 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 at apache.org>wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Fri, Jun 21, 2013 at 9:02 AM, Sebastien Blanc <
>>>>>>>>>>>>>> scm.blanc at 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 at gmail.com> 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 at 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 at gmail.com> 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 at apache.org> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Sun, Jun 16, 2013 at 7:46 AM, Douglas Campos <
>>>>>>>>>>>>>>>>>> qmx at 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 at 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 at lists.jboss.org
>>>>>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>>>>>> aerogear-dev at 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 at lists.jboss.org
>>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> aerogear-dev mailing list
>>>>>>>>>> aerogear-dev at 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 at lists.jboss.org
>>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> aerogear-dev mailing list
>>>>>>>> aerogear-dev at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at 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 at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>
>>>
>>>
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130621/3fc4dd51/attachment-0001.html

More information about the aerogear-dev mailing list