Artwork

Content provided by iOhYes. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by iOhYes or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

114: It's All Unified

47:06
 
Share
 

Archived series ("Inactive feed" status)

When? This feed was archived on May 05, 2018 01:25 (6+ y ago). Last successful fetch was on March 03, 2018 12:11 (6+ y ago)

Why? Inactive feed status. Our servers were unable to retrieve a valid podcast feed for a sustained period.

What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.

Manage episode 150136918 series 55743
Content provided by iOhYes. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by iOhYes or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

Discussion - Notifications in iOS 10

  • Brief breakdown of WWDC sessions related to notifications
  • New stuff
    • APNS Token-based authentication
    • UserNotifications (and UserNotificationsUI) Framework (Unifies Remote and Local Notifications)
    • Access to user-defined notification settings
    • Expanded content
      • Titles
      • Subtitles
      • Media attachments
    • Scheduling and handling within Extensions
    • In-app presentation
    • Removal/update of pending notifications
    • Dismissal actions
    • Service Extensions
  • APNS Token-based authentication
    • Uses JSON Web Tokens (libraries widely available to assist with token generation)
    • For server-side solutions where using a certificate isn’t practical/feasible
    • Addresses issue of certificate expiration (though tokens also expire, new ones can be generated on the fly)
  • UserNotifications Framework

    • Provides a single notifications API across iOS, watchOS and tvOS
      • iOS: Full support for scheduling and management of notifications
      • watchOS: Support for forwarded notifications and local notifications on the watch
      • tvOS: Support for badging app icons
    • Key components/concepts:
      • UNUserNotificationCenter
        • Authorization requests
        • Scheduling via requests (by providing content and triggers)
      • UNNotificationRequest
        • Identifier
        • Content
        • Trigger
      • UNMutableNotificationContent
      • UNNotificationAttachment
        • Audio
        • Images
        • Video
      • Triggers
        • Push (UNPushNotificationTrigger is not instantiated by apps)
        • UNTimeIntervalNotificationTrigger
        • UNCalendarNotificationTrigger
        • UNLocationNotificationTrigger
      • UNUserNotificationCenterDelegate Protocol
        • userNotificationCenter:willPresentNotification:withCompletionHandler:
        • userNotificationCenter:didReceiveNotificationResponse:withCompletionHandler
      • UNNotificationCategory - defines a type of notification, allows actionable notifications and content extensions
      • UNNotificationAction - represents a task you can perform in response to a notification
      • UNNotificationServiceExtension - Entry point for service extensions. Allows you to process the payload of a push notification before it is presented (eg: end-to-end encryption or notification attachments). Use in conjunction with “mutable-content: 1” in the aps portion of an APNS payload.
  • UserNotificationsUI Framework

    • Provides the UNNotificationContentExtension protocol
    • View controllers adopt this protocol, using the VC’s view to display the notification contents
    • Custom content is sandwiched between a header with the application icon and title and the default notification payload (default payload can be hidden using an attribute in the Info.plist)
    • No user interaction
    • Actions are displayed and extensions can respond to them by intercepting action responses
    • Protocol provides a didRecieveNotification: method you can use to set up UI in response to the notification

Picks

Darryl

John

This episode sponsored by Braintree

  continue reading

100 episodes

Artwork

114: It's All Unified

iOhYes

31 subscribers

published

iconShare
 

Archived series ("Inactive feed" status)

When? This feed was archived on May 05, 2018 01:25 (6+ y ago). Last successful fetch was on March 03, 2018 12:11 (6+ y ago)

Why? Inactive feed status. Our servers were unable to retrieve a valid podcast feed for a sustained period.

What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.

Manage episode 150136918 series 55743
Content provided by iOhYes. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by iOhYes or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

Discussion - Notifications in iOS 10

  • Brief breakdown of WWDC sessions related to notifications
  • New stuff
    • APNS Token-based authentication
    • UserNotifications (and UserNotificationsUI) Framework (Unifies Remote and Local Notifications)
    • Access to user-defined notification settings
    • Expanded content
      • Titles
      • Subtitles
      • Media attachments
    • Scheduling and handling within Extensions
    • In-app presentation
    • Removal/update of pending notifications
    • Dismissal actions
    • Service Extensions
  • APNS Token-based authentication
    • Uses JSON Web Tokens (libraries widely available to assist with token generation)
    • For server-side solutions where using a certificate isn’t practical/feasible
    • Addresses issue of certificate expiration (though tokens also expire, new ones can be generated on the fly)
  • UserNotifications Framework

    • Provides a single notifications API across iOS, watchOS and tvOS
      • iOS: Full support for scheduling and management of notifications
      • watchOS: Support for forwarded notifications and local notifications on the watch
      • tvOS: Support for badging app icons
    • Key components/concepts:
      • UNUserNotificationCenter
        • Authorization requests
        • Scheduling via requests (by providing content and triggers)
      • UNNotificationRequest
        • Identifier
        • Content
        • Trigger
      • UNMutableNotificationContent
      • UNNotificationAttachment
        • Audio
        • Images
        • Video
      • Triggers
        • Push (UNPushNotificationTrigger is not instantiated by apps)
        • UNTimeIntervalNotificationTrigger
        • UNCalendarNotificationTrigger
        • UNLocationNotificationTrigger
      • UNUserNotificationCenterDelegate Protocol
        • userNotificationCenter:willPresentNotification:withCompletionHandler:
        • userNotificationCenter:didReceiveNotificationResponse:withCompletionHandler
      • UNNotificationCategory - defines a type of notification, allows actionable notifications and content extensions
      • UNNotificationAction - represents a task you can perform in response to a notification
      • UNNotificationServiceExtension - Entry point for service extensions. Allows you to process the payload of a push notification before it is presented (eg: end-to-end encryption or notification attachments). Use in conjunction with “mutable-content: 1” in the aps portion of an APNS payload.
  • UserNotificationsUI Framework

    • Provides the UNNotificationContentExtension protocol
    • View controllers adopt this protocol, using the VC’s view to display the notification contents
    • Custom content is sandwiched between a header with the application icon and title and the default notification payload (default payload can be hidden using an attribute in the Info.plist)
    • No user interaction
    • Actions are displayed and extensions can respond to them by intercepting action responses
    • Protocol provides a didRecieveNotification: method you can use to set up UI in response to the notification

Picks

Darryl

John

This episode sponsored by Braintree

  continue reading

100 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide