+
+
+
🎬
+
+The importance of maintaining a **graphical consistency** shouldn't be removed in the `Dark Mode`.
+
+
+Using [bold colors](https://developer.apple.com/videos/play/wwdc2023/10194?time=182) is a good way to **highlight some elements** in the widget.
+
+
+The layout should **adapt the display of information** according to their [relevance](https://developer.apple.com/videos/play/wwdc2023/10194?time=224).
+
+
+
+
+
+
🎬
+
+Whatever the native default transitions (numeric or replace content transitions...) or some customized ones, **smoothness** with **unoverlapping** and **fading** are important notions to be taken into account for transitions in the widget.
+
+
+
+
+
🎬
+
+It's crucial to notify the user by means of an alert if an **update** requires his attention.
+
+
+
+The **standard notification sound** combined with the **screen lighting** are the essential elements that point out an alert that should be highlighted by a specific graphical element as well.
+
+
+
+
+
🎬
+
+This view aims at keeping on using one's device whithout losing sight on the most important information about some running activities.
+For this purpose, it's highly recommended to **avoid useless spaces** around the [sensor region](https://developer.apple.com/videos/play/wwdc2023/10194/?time=700).
+
+
+
+When [alerting](https://developer.apple.com/videos/play/wwdc2023/10194/?time=738) the user about a crucial information, it's better to **expand the view** instead of sending a notification.
+
+
+
+
+
+
+
🎬
+
+
+When expanded, the view should keep the **same information at the same location** in order to [be coherent](https://developer.apple.com/videos/play/wwdc2023/10194/?time=797) and avoid a cognitive work for the user.
+
+
+
+Better is the [refinement](https://developer.apple.com/videos/play/wwdc2023/10194/?time=806) regarding the spaces around the graphic items, better will be the user experience and more undetected will be the sensor region.
+
+
+
+
+
+
+
🎬
+
+Appearing when switching between **multiple apps** while `Live Activities` are still alive, the minimal view aims at providing a relevant information through a teeny-weeny area that must be refined when devising the app.
+
+
+
+
+
+
+
🎬
+
+Few milestones are mandatory for this first lifecycle step:
+1. Implement the **ActivityAttributes** protocol to describe the dynamic and static contents.
+
+2. Define a structure to outline the state and the configuration of the activity.
+
+3. Request and start the `Live Activity`.
+
+
+
+
+
+
+
🎬
+
+When updating an activity, it's important to:
+- **Identify** what needs to be updated,
+
+- **Create an alert** for informing the user the update occurs if need be.
+
+
+
+
+
+
+
🎬
+
+Using the **ActivityStateUpdates** structure is the best way to observe the **four states** an activity may encounter (started, finished, dismissed, stale) so as to provide the appropriate command to be executed as quick as possible.
+
+
+
+
+
+
+
🎬
+
+Before ending an activity, it's important to **create a final content** combined with the **policy** the system should remove the `Live Activity`.
+
+
+
+
+
+
+Besides the **`Lock Screen UI`** that displays the `Live Activities` under a usual notification aspect, it's important to notice that the specific **`Dynamic Island`** is made up of three distinct presentations:
+
+- **[compact](https://developer.apple.com/videos/play/wwdc2023/10184/?time=774)**: when the owner app is the only one to fire an activity,
+
+- **[minimal](https://developer.apple.com/videos/play/wwdc2023/10184/?time=855)**: when more than one app starts a `Live Activity`,
+
+- **[expanded](https://developer.apple.com/videos/play/wwdc2023/10184/?time=905)**: when one of the previous two presentations is touched and held.
+
+
+
+
+
+
+
+
+To realize the interface introduced in the previous tab, the `Live Activity` configuration should be put in the **[WidgetBundle](https://developer.apple.com/videos/play/wwdc2023/10184/?time=650)**.
+
+The implementation for the **`Lock` `Screen` `UI`** concerns the [first closure](https://developer.apple.com/videos/play/wwdc2023/10184/?time=710) of the configuration while the second one deals with the **`Dynamic` `Island`** whose size classes are detailed in the `User interface` tab of this section.
+
+
+
+
+
+
+
🎬
+
+Adding the push notifications service in `Xcode` is necessary for `ActivityKit` to request push tokens.
+
+
+
+
+
+
🎬
+
+Few lines of code are required for enabling and handling push updates.
+
+
+
+
+
+
🎬
+
+Besides the normal `HTTP` headers to be used, the **`APNs` headers are threefold**.
+
+
+
+
+
+
+
🎬
+
+The first `APNs` payload to be sent is made up of **three essential fields**.
+
+
+
+
WWDC 2023
- WWDC 2023 Build accessible apps with SwiftUI and UIKit
- WWDC 2023 Build programmatic UI with Xcode Previews
- WWDC 2023 Expand on Swift macros
- WWDC 2023 Explore pie charts and interactivity in Swift Charts
- WWDC 2023 Generalize APIs with parameter packs
- WWDC 2023 Keynote
- WWDC 2023 Perform accessibility audits for your app
- WWDC 2023 Platforms State of the Union
- WWDC 2023 Unleash the UIKit trait system
+ WWDC 2023 Build accessible apps with SwiftUI and UIKit
+ WWDC 2023 Build programmatic UI with Xcode Previews
+ WWDC 2023 Design dynamic Live Activities
+ WWDC 2023 Expand on Swift macros
+ WWDC 2023 Explore pie charts and interactivity in Swift Charts
+ WWDC 2023 Generalize APIs with parameter packs
+ WWDC 2023 Keynote
+ WWDC 2023 Meet ActivityKit
+ WWDC 2023 Perform accessibility audits for your app
+ WWDC 2023 Platforms State of the Union
+ WWDC 2023 Unleash the UIKit trait system
+ WWDC 2023 Update Live Activities with push notifications
WWDC 2023 What’s new in SF Symbols 5
WWDC 2023 What’s new in Swift
WWDC 2023 What’s new in SwiftUI