[aerogear-dev] [Push] Notification Actions (iOS8)

[Corinne Krych]

On 10 Jul 2014, at 15:43, Sebastien Blanc <scm.blanc at gmail.com> wrote:

> but tbh I don't really see a use case for the contact app and interactive notifications.
> 
> 


Same here.
Initial idea from Sebi to have it on aeroDoc illustrates better interactive notification

> On Thu, Jul 10, 2014 at 3:43 PM, Sebastien Blanc <scm.blanc at gmail.com> wrote:
> 
> 
> 
> On Thu, Jul 10, 2014 at 3:37 PM, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> 
> 
> On Thu, Jul 10, 2014 at 3:31 PM, Corinne Krych <corinnekrych at gmail.com> wrote:
> I did those sample with interactive notification on local.notification on my initial repo. This is just POC/sample code.
> Then I merged my repo into aerogear-push-helloworld master
> I haven't merged interactive notification in central repo and actually I don't planned to. We have a ticket to demo interactive notification with AeroDoc.
> Let's keep Helloworld simple.
> 
> I agree on keeping HelloWorld simple - but on the MobileContacts, that can be a nice thing ? IMO we should to that first and than bring it to AeroDoc
> Not sure how we could introduce the interactive Notification in the Contact App , maybe " Show Contact | Ignore"  ? 
>  
> 
> ++
> Corinne
> 
> 
> On 10 July 2014 14:42, Matthias Wessendorf <matzew at apache.org> wrote:
> 
> 
> 
> On Thu, Jul 10, 2014 at 2:39 PM, Corinne Krych <corinnekrych at gmail.com> wrote:
> 
> On 10 Jul 2014, at 14:36, Sebastien Blanc <scm.blanc at gmail.com> wrote:
> 
> > Sounds good !
> >
> > Just to confirm does the value of the "action-category" relates to the category.identifier like in https://github.com/corinnekrych/HelloWorld-Swift/blob/local.notification/HelloWorldSwift/AppDelegate.swift#L60 ?
> 
> what's the difference between your repo and this folder:
> https://github.com/aerogear/aerogear-push-helloworld/tree/master/ios-swift
> 
> 
> 
> 
>  
> >
> >
> 
> 
> Yes like commented here:
> https://github.com/corinnekrych/HelloWorld-Swift/blob/local.notification/HelloWorldSwift/AppDelegate.swift#L21
> 
> 
> >
> > On Thu, Jul 10, 2014 at 2:28 PM, Matthias Wessendorf <matzew at apache.org> wrote:
> > Hi,
> >
> > as Corinne mentioned on a different thread, w/ iOS8 Apple introduces new UIUserNotificationActions, that can be grouped into a category (UIUserNotificationCategory).
> >
> > For remote notifications (aka push) those actions can be trigger by sending this JSON payload to APNs:
> >
> > aps {
> >   alert: {...},
> >   category: "SOMETHING"
> > }
> >
> >
> > I'd like to add that feature to the UnifiedPush Server and the Java/Node Senders.
> >
> > Our own message format (see [2]) has already a categoies element, but that is used for filtering/tagging; That element is NOT related to the actual payload of the message (which the apple action/category is all about).
> >
> > Now, I'd like to introduce an "action-category" element inside of the "message" object, like:
> >
> > message: {
> >   .......
> >   "alert":"HELLO!",
> >   .......
> >   "action-category":"SOMETHING"
> > }
> >
> > This value will be send down to the actual device (by Apple) as part of the message. The name is perhaps a bit Apple-oriented, but I think it may fit other platforms as well...
> >
> > Looks like Summers/Passos want to do similar for Android (see [3]).
> >
> > What do you think ?
> >
> >
> > -Matthias
> >
> >
> >
> > [1] What's New in iOS Notifications on:
> > https://developer.apple.com/videos/wwdc/2014/ (caution, for lame reasons only works on Safari O_o)
> >
> > [2] http://aerogear.org/docs/specs/aerogear-push-messages/
> > [3] https://issues.jboss.org/browse/AGDROID-258
> >
> >
> > --
> > 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
> 
> 
> 
> -- 
> 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