[aerogear-dev] Chrome Push API with AeroGear Unified Push Example

[Idel Pivnitskiy]

Thank you, guys!


> i remember writing a blog post on using the Android variant for chrome,
> but i don't think i ever created an example for it.  And i think it was
> only for packaged apps at that time.
>

Yes, previously it worked just with chrome extensions and applications.


> I've actually been looking at Web Push a little lately and i noticed that
> to send a payload, there are some extra bits of info, that are attached to
> the subscription object that would probably need to be stored on the UPS
> somehow.   I believe this is the same for FF too.


Chrome does not support payload in push notifications because they haven't
implemented encryption yet. Encryption of push messages is mandatory.
That's why they decided to keep it null. But according to the MDN, FF
should support it [1]. I will check.

I also want to notice, that FCM/GCM does not support Web Push protocol now.
Googlers just implemented a Push API [2] in Chrome (browser part of
WebPush) and use their proprietary protocol for push message delivering.

[1] https://developer.mozilla.org/ru/docs/Web/API/PushEvent
[2] https://www.w3.org/TR/push-api/

Best regards,
Idel Pivnitskiy
--
Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>

On Mon, Jun 27, 2016 at 3:47 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> Awesome.
>
> i remember writing a blog post on using the Android variant for chrome,
> but i don't think i ever created an example for it.  And i think it was
> only for packaged apps at that time.  So this is really nice.
>
>
> I've actually been looking at Web Push a little lately and i noticed that
> to send a payload, there are some extra bits of info, that are attached to
> the subscription object that would probably need to be stored on the UPS
> somehow.   I believe this is the same for FF too.
>
> I wonder if we should start looking at a "WebPush" variant.  If only
> Safari would follow suit.
>
>
>
> On Mon, Jun 27, 2016 at 4:45 AM, Oleg Matskiv <omatskiv at redhat.com> wrote:
>
>> Hello Idel,
>> Great demo !
>>
>> Thank you for sharing.
>>
>> On Mon, Jun 27, 2016 at 2:25 AM, Idel Pivnitskiy <
>> idel.pivnitskiy at gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> I've created an example, which shows how Chrome Push API could work with
>>> AeroGear Unified Push. It works without any changes to the UPS code base!
>>>
>>> Here is a sample app:
>>> https://github.com/aerogear/aerogear-js-cookbook/pull/13
>>> And here is a demo: https://youtu.be/o6FdbJm-47Y
>>>
>>> Hope you will enjoy! :)
>>>
>>> Best regards,
>>> Idel Pivnitskiy
>>> --
>>> Twitter: @idelpivnitskiy <https://twitter.com/idelpivnitskiy>
>>> GitHub: @idelpivnitskiy <https://github.com/idelpivnitskiy>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Oleg Matskiv
>> Associate Quality Engineer
>> Red Hat Mobile Application Platform
>> omatskiv at redhat.com
>>
>> _______________________________________________
>> 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/20160628/173c1e43/attachment.html