[aerogear-dev] UnifiedPush: Sending notifications from the AdminUI
Matthias Wessendorf
matzew at apache.org
Mon Feb 24 04:37:44 EST 2014
On Mon, Feb 24, 2014 at 8:33 AM, Matthias Wessendorf <matzew at apache.org>wrote:
>
>
>
> On Mon, Feb 24, 2014 at 8:15 AM, Sebastien Blanc <scm.blanc at gmail.com>wrote:
>
>>
>>
>>
>> On Mon, Feb 24, 2014 at 12:08 AM, Burr Sutter <bsutter at redhat.com> wrote:
>>
>>> I think it would be a huge win for the getting started experience - the
>>> docs can say
>>> 1) the iOS device will prompt the end-user (will you accept push
>>> notifications) - say Yes
>>> 2) now look for the device token in the admin console - is it there?
>>> 3) now send it a quick test message, with the app in the foreground,
>>> background, app shutdown, phone on lockscreen, etc - to learn about the
>>> behaviors.
>>>
>> I like this flow but what you want here is to send only to a single
>> device, right ? For that we have to solve this ticket before
>> https://issues.jboss.org/browse/AGPUSH-420
>>
>
> well - he means test to a new app. Which most likely contains just one
> device :-)
>
works great - just tested w/ my iPhone :-)
No more curl - yay !!! :)))
>
>
>
>
>
>>
>>>
>>> On Feb 23, 2014, at 2:15 PM, Sebastien Blanc <scm.blanc at gmail.com>
>>> wrote:
>>>
>>> So I sart playing with it>
>>> If you browse to http://newpush-sblanc.rhcloud.com/ with admin / 123
>>> and select (or create) an application, in the "Send notifications ..."
>>> section you will see a link "test Message", that will open an overlay with
>>> a default send message that is valid. Change it (add criteria / custom
>>> values) or just hit the "Send test Message" and it will send a push
>>> notification to the registred devices.
>>> :)
>>>
>>>
>>> On Sun, Feb 23, 2014 at 1:52 PM, Luke Holmquist <lholmqui at redhat.com>wrote:
>>>
>>>> Let's do it. I was asked that question at my talk the other night.
>>>>
>>>> Sent from my iPhone
>>>>
>>>> On Feb 23, 2014, at 7:06 AM, Matthias Wessendorf <matzew at apache.org>
>>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> over the weekend I spoke w/ a friend: His company is doing some mobile
>>>> (iOS/Android) apps which also support receiving push notifications.
>>>>
>>>> Two examples he told me. After receiving push notification:
>>>>
>>>> * One of their apps basically fetches the latest version of a CSV file,
>>>> stored on a public HTTP Server.
>>>>
>>>> * Another app is used to tell sales guys new brochure files (PDF) are
>>>> available on a protected resource of a webserver (which they _can_ than
>>>> download from w/in the app, if the like to)
>>>>
>>>> The company build a simple console (PHP) which allows them to send new
>>>> push messages, when ever their customers want to.
>>>>
>>>> I showed them our UnifiedPush Server and its usage via our AeroDoc
>>>> example (iOS / backend). They really liked the UnifiedPush Server.
>>>> Especially that it does store all the device metadata.
>>>>
>>>> But since a lot of their mobile apps don't have a backend requirement,
>>>> they would still have to use their own console (which than connects to UPS)
>>>> for submitting all the push messages they want.
>>>>
>>>>
>>>>
>>>> This brings me to [AGPUSH-38] and I really think we should implement
>>>> that feature. Not only for sending test messages! If our UnifiedPush Server
>>>> allows its users to simple send push messages to all of their mobile apps,
>>>> it would make the server even more attractive.
>>>>
>>>> I regret a bit that I was against [AGPUSH-38] in the beginning, I guess
>>>> that's due to my Java enterprise background, where you typically find
>>>> complex setups, and server talk to servers :-(
>>>>
>>>> Anyways, now I really think that the UPS has to have such a 'send push'
>>>> facility inside of the Admin UI :-) I believe that we could reach way more
>>>> potential users with something like that
>>>>
>>>> Any thoughts?
>>>>
>>>>
>>>> Greetings,
>>>> Matthias
>>>>
>>>>
>>>> [AGPUSH-38] https://issues.jboss.org/browse/AGPUSH-38
>>>>
>>>>
>>>> --
>>>> 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
>
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140224/e295d4cc/attachment.html
More information about the aerogear-dev
mailing list