[aerogear-dev] Push "all inclusive" demo

Sebastien Blanc scm.blanc at gmail.com
Fri Jun 14 03:48:44 EDT 2013 

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 at apache.org>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 at apache.org>wrote:
>
>>
>>
>>
>> On Wed, Jun 12, 2013 at 3:29 PM, Summers Pittman <supittma at redhat.com>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 at 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
>>>> [image: Inline image 1]
>>>>
>>>>
>>>>
>>>>
>>>> On Wed, Jun 12, 2013 at 9:17 AM, Christos Vasilakis <cvasilak at gmail.com
>>>> > wrote:
>>>>
>>>>> +1
>>>>>
>>>>>    On Jun 11, 2013, at 5:45 PM, Sebastien Blanc <scm.blanc at 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 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>Prodoctor
>>>>> 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 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 listaerogear-dev at lists.jboss.orghttps://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 listaerogear-dev at lists.jboss.orghttps://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
>>
>
>
>
> --
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130614/4c68ed4d/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 61403 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130614/4c68ed4d/attachment-0001.png

More information about the aerogear-dev mailing list