쉐도잉 연습: WWDC26: Modernize your UIKit app | Apple - YouTube로 영어 말하기 배우기
C1
Hi, I'm Michael Ox, an Engineering Manager on the UI Frameworks team.
166 문장
문장이 너무 짧거나 길면 Edit를 눌러 조정하세요.
1
Hi, I'm Michael Ox, an Engineering Manager on the UI Frameworks team.
2
And today, I'll tell you how to modernize your UIKit app.
3
In this video, I'll tell you about some big changes to app adaptivity requirements and how iPhone apps are fully resizable.
4
Next, I'll present some new APIs in tab bars, navigation bars and menus.
5
Then, I'll talk about how to support Apple intelligence and some changes you should be aware of.
6
And finally, I'll cover a new skill that helps an agent to handle most of this modernization work automatically.
7
Let's get started with app adaptivity.
8
Your app can already appear in many different environments.
9
There are different screen sizes and apps can run side by side with other apps and even themselves.
10
On iPad, people expect apps to resize and move to external displays seamlessly.
11
On iPhone, people expect apps to work in both portrait and landscape orientations.
12
They also expect to mirror their iPhone to the Mac.
13
In iOS and macOS 27, this experience has been improved, and apps running in these environments are now exposed to many
14
of the dynamic changes any app native to the platform needs to support.
15
When people use iPhone mirroring on the Mac, they can fully resize the iPhone window, allowing your apps to resize and adapt.
16
Likewise, an iPhone-only app running on iPad will be fully resizable like any other iPad app.
17
Because of this, it is important that your app dynamically adjusts to any available scene size at runtime.
18
If your app is a universal binary, you're off to a great start start, but there's more to do to make your app fully adaptive
19
and have it dynamically adjust to the environment it is running in.
20
I will cover the most important steps and common issues you might encounter when making your app more adaptive.
21
Verifying your app is no longer using App Lifecycle and instead has adopted Scene Lifecycle, the basis for any adaptive app.
22
Making sure your app is not using main screen references.
23
And how to handle user interface idiom and interface orientation checks.
24
The first step is to move from App Lifecycle to Scene Lifecycle.
25
Most apps are already using Scene Lifecycle.
26
It is the basis for an adaptive app
27
and for many of the other tasks I'm going to show you in this video.
28
UiScene Lifecycle is now required when building with the latest SDKs.
29
Without it, your application will no longer launch.
30
Verify that your app is using a UI scene delegate, which is the basis for scene lifecycle.
31
If you have not yet migrated to scene lifecycle, check out the video Make your UIKit app more flexible from WWDC25,
32
and read Transitioning to the UIKit scene-based lifecycle in the documentation.
33
Next, when your iPhone app is mirrored on a Mac, or when a person moves your app to an external display on the iPad,
34
iPad, the screen associated with your scene changes. That means
35
that any reference to the main screen in your code will provide incorrect information for the environment your app is running in.
36
It is important that you do not reference the main screen in your app.
37
Instead, access the screen dynamically from a Windows window scene.
38
When a view or view controller is not available in immediate context, pass in a screen reference to any method that needs it.
39
Even better than fetching the correct screen is to remove screen references altogether.
40
There are a lot of other APIs that are better suited for an adaptive app.
41
I'll take you through two common patterns.
42
Accessing the scale of the screen should be replaced with the trait collection's display scale.
43
Views and view controllers automatically update their trait collections and provide reasonable fallbacks even when they're not part of the visible hierarchy.
44
A lot of common override points are also tracked, meaning that you do not need to explicitly monitor for changes.
45
Instead, the system tracks which trade collection properties are being used inside common layout and drawing methods, like layout subviews, update properties,
46
draw rect, and many others.
47
If a change to a tracked trade is detected, the system will ensure these methods are called again, so your UI automatically updates accordingly.
48
Check out Automatic Trade Tracking in the documentation to learn more.
49
In places where Automatic Trade Tracking is not available, Register for Trade Changes can be used to observe changes.
50
This method allows you to set up a closure that is called when a specific trade in the receiving view changes.
51
Use this to invalidate caches or update other data related to that view.
52
Check out Adapting Your App When Traits Change in the documentation to learn more.
53
Another common use of the screen is to check its bounce to get the amount of space available to your app.
54
However, in an adaptive environment, the space your scene has available is not always the full screen.
55
So if you still have any reference to screen bounds in your app, now is the time to remove these.
56
The Window Scene's Effective Geometry provides information on how much space your app has available.
57
If you need to monitor the Effective Geometry for changes, implement Window Scene Did Update Effective Geometry in your Scene Delegate.
58
In your Views and View Controllers, instead of referencing the scene bounds, use the available size of your view controller's view
59
or your view super view to determine how much space is available to it.
60
This makes your UI less dependent on how it is presented.
61
It will adjust better when your view controller appears in other contexts, for example inside of a split view controller.
62
For games, resizing can be challenging.
63
Due to this, UI Requires Fullscreen is honored on iPhone in resizable environments starting in iOS 27.
64
Its behavior has also been updated and no longer opts your app fully out of resizing.
65
Instead, it enables discrete resizing that honors your supported interface orientations.
66
In discrete resizing, every time a person changes the scene size, the system transitions the scene to a new screen configuration matching that size.
67
So your game always renders at full quality in the available space.
68
If your app is using the user interface idiom trait, be aware that this trait is no longer meaningful for any kind of layout decision.
69
Your app is expected to use the additional space in a meaningful way, regardless of whether it is running in the phone or pad user interface idiom.
70
When your iPhone app is running on an iPad or an iPhone mirroring on the Mac, it will be fully resizable, but it will still run under the phone user interface idiom.
71
Stop checking the user interface idiom for any layout decisions in your code.
72
Use size classes instead to handle sizing constraints such as collapsing menus and updating your app's layout for the available space.
73
If you need finer control, use the surrounding view size like I mentioned earlier.
74
Interface orientation also is no longer useful for layout decisions.
75
In iOS 27, an app-supported interface orientation is a preference provided to the system to the system.
76
It will be ignored when your app is running in a resizable environment.
77
You should not consider interface orientation for any layout calculations.
78
In iPhone mirroring on the Mac, your app will always be running in the portrait interface orientation regardless of the aspect ratio of your app's scene.
79
Any interface orientation checks in your app should also be updated to use size classes.
80
This conceptual shift was introduced in iOS 8.
81
At WWDC 2014, Bruce Nilo said, a device rotation is only an animated bounce change.
82
With an array of device sizes, resizable windows on iPad, and resizable iPhone apps on Mac, today this insight is more relevant than ever.
83
And speaking of interface orientation, in iOS 27, UI View also conforms to the new body protocols from Core Motion and Core Location.
84
This makes it much easier to configure your motion and location managers.
85
Connect them to the view that visualizes the motion data, such as a compass or a map view.
86
This ensures the data is always in the right coordinate space, regardless of interface orientation.
87
That covers the main adaptivity changes.
88
Now, here's how to test these changes in your app.
89
Xcode 27 brings new ways to iterate your app's behavior across
90
different screen sizes without having to install your app on multiple separate simulators or devices.
91
In the new DeviceHub app, as well as in Xcode Previews, click the Enter Resize Mode icon.
92
Then, drag the edges of the device to resize it freely.
93
This allows you to iterate on your changes quicker.
94
Once you are satisfied with the results, make sure to test iPhone mirroring and iPad with real devices.
95
To learn more about the DeviceHub app and its tools, watch Get the Most Out of DeviceHub. And that's adaptivity.
96
Before I show you a new agentic coding skill
97
that can help you with the work necessary to make your app fully adaptive, there are two more topics to cover.
98
First up, bars and menus.
99
On iPad, tab bars can expand into a full sidebar representation to surface more sections of the app hierarchy
100
when the current environment supports a sidebar.
101
On iPhone, the bottom tab bar is shown across all sizes by default.
102
New in iOS 27, iPhone apps can also opt into sidebars by setting the tabbar controller's Sidebar Preferred Placement to Sidebar.
103
Note that in contrast to the iPad, this is an app choice.
104
If your app opts into the sidebar representation, there is no way to toggle between a sidebar and tabbar layout in the UI.
105
Instead, the system determines if there is enough space to show a sidebar.
106
For example, when the horizontal size class is regular.
107
To determine if the tab bar sidebar representation can be shown, use the sidebars is available property.
108
If a sidebar is not currently available, surface the UI behind nested tabs in other parts of your app.
109
To learn more about managing tab groups, watch Make Your UIKit app more flexible from WWDC 25.
110
And to learn more about tabbars and its integration with sidebars, watch Elevate Your tab and sidebar experience in iPadOS from WWDC24.
111
UITabbarController also lets you customize the prominent tab.
112
The prominent tab is always visible, even when the tabbar collapses during scrolling.
113
In iOS 27, you have the option to make any tab prominent by setting the prominent tab identifier.
114
Okay, that's tabbars.
115
Now let's talk about navigation bars.
116
Navigation bars can interactively slide away as people scroll.
117
This provides more room on the screen for your app's content.
118
By default, navigation bars minimize in certain conditions defined by the system.
119
You can force this behavior one way
120
or the other by setting the Bar Minimization Behavior property on your navigation item to Always or Never.
121
If you handle Safe Area Avoidance yourself, set Bar Minimization Safe Area Adjustment to Never,
122
so Bar Minimization doesn't update insets automatically.
123
Another change during scroll interactions is an updated appearance for the scroll edge effects.
124
As such, you should review your design, especially where you have previously overwritten the defaults provided by the OS.
125
In particular, the automatic style no longer switches between the existing soft and hard styles, but provides its own visuals for additional clarity.
126
If you have overwritten the style from automatic previously, that decision should be re-evaluated especially when set to soft,
127
as that no longer matches the default system appearance.
128
With the refined look of liquid glass, images you set on menu elements may not be shown by default in some contexts,
129
such as in the menu bars on iPadOS and macOS.
130
If you still need an image to be visible, set the preferred image visibility property to override the default system behavior.
131
Review the updated human interface guidelines for when to include visible images in a menu element.
132
And that's Bars and Menus.
133
Now, how to support Apple intelligence in your app.
134
Menus in iOS 27 feature an Ask Siri button to allow people to start a conversation with Siri right from your app.
135
This is a powerful entry point that allows people to interact with the context they care about.
136
Menus will automatically display this item when there's content relevant for Siri.
137
To provide more relevant information specific to your app, use the new View Annotations API.
138
With it, you can annotate specific views with app entities.
139
Check out Explore Advanced App Intents features for Siri and Apple Intelligence to learn more.
140
If your app supports drag and drop, Siri can load resources from your application's drag handlers.
141
When Apple Intelligence is invoked from context menus, the system will call available drag delegate methods to load the content.
142
Avoid performing animations or presenting modal UI from session will begin.
143
Drag sessions can be initiated without a user gesture.
144
If your app has a stateful UI that shows up when a user initiates a drag, put that code in sessionDidMove instead.
145
If the adaptivity changes I outlined sound like a lot of work, I've got you covered.
146
Let's talk about what's on everyone's mind, agentic coding.
147
New in Xcode 27 is an app modernization skill.
148
It has a deep understanding of the adaptivity tasks I outlined.
149
And with the context of your project, it can make a lot of these changes automatically.
150
Use Xcode's intelligence features and ask an agent to make your app more adaptable.
151
It will automatically convert main screen calls to trait collection or scene bounce checks, adding invalidation logic if necessary.
152
It will also replace interface orientation checks with size class checks.
153
It will even convert your app to use scene lifecycle.
154
For more complex tasks, it will ask clarifying questions.
155
And for tasks too large to handle in a single session, it will add comments to help you keep track of the remaining work.
156
And to use skills in other tools, you can export the ones Xcode uses with XCRun Agent Skills Export.
157
This will create markdown files that you can then import in your workflows.
158
Skills like this one are a powerful way to prepare your app for resizable environments. And that's it.
159
These are the most important things to modernize your app.
160
Build your app with the iOS 27 SDK
161
and try out the resizable simulator in the new DeviceHub app and test your app in iPhone mirroring on macOS 27.
162
Identify areas in your app that need to be a little more flexible.
163
And if you like agentic coding, give the new skill a try and discover how much it can do automatically.
164
Thanks for joining.
165
I cannot wait to resize your apps.
166
you
앱 다운로드
당신이 말하는 모든 문장을 AI가 채점
TRENDING
인기 동영상
맥락 및 배경
안녕하세요, 저는 UI 프레임워크 팀의 엔지니어링 매니저 마이클 옥스입니다. 오늘은 UIKit 앱을 현대화하는 방법에 대해 말씀드리겠습니다. 이 비디오에서는 앱 적응성 요구 사항의 주요 변화와 iPhone 앱의 전체 크기 조정 가능성에 대해 설명합니다. 또한 탭 바, 내비게이션 바 및 메뉴의 새로운 API에 대해서도 다루겠습니다. 이러한 내용을 통해 유튜브 영어 공부와 영어 발음 교정에 도움이 될 수 있도록 합니다.
일상 소통을 위한 5가지 주요 문구
- “앱 적응성을 현대화해보세요.” - 비즈니스 환경에서 앱의 적응성을 강조합니다.
- “외부 디스플레이에 앱을 이동하세요.” - iPad와 Mac 환경에서 응용 프로그램의 이동을 안내합니다.
- “UI Scene 수명 주기에 대해 알아보세요.” - 최신 SDK를 이해하는 데 필수적인 요소입니다.
- “트레이트 컬렉션을 사용하세요.” - 화면 크기에 따라 적절한 UI 업데이트를 유도합니다.
- “예제를 통해 배워보세요.” - 실습을 통해 이해도를 높여줍니다.
단계별 쉐도잉 가이드
이 비디오는 다소 기술적인 내용을 다루기 때문에 몇 가지 중요 단계를 따라가면서 반복 연습하는 것이 좋습니다. 다음은 이 영상을 통해 익혀야 할 방법들입니다.
- 동영상 반복 시청하기: 처음에는 전체 내용을 파악하기 위해 천천히 시청합니다.
- 쉐도우 스피킹 연습하기: 한 문장씩 멈추고, 발음과 억양을 따라 읽어보세요. 이때 shadow speech 기법을 활용할 수 있습니다.
- 주요 문구 익히기: 위에서 소개한 5가지 문구를 집중적으로 연습합니다. 특히, “UI Scene 수명 주기에 대해 알아보세요.”와 같은 문구를 통해 기술적 용어에 익숙해질 수 있습니다.
이러한 방법들을 통해 유튜브 영어 공부의 효과를 극대화할 수 있으며, 발음이 개선되는 경험을 하게 될 것입니다. 영어 발음 교정이 필요한 부분이 있다면, 다양한 영어 콘텐츠를 활용하여 연습해보세요. shadowspeaks 기법과 같은 혁신적인 방법으로 더욱 자연스러운 의사소통 능력을 개발해 보세요.
쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법
쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.
☕ 커피 한 잔 사주기
ShadowingEnglish는 여러분의 지원 덕분에 100% 무료로 운영됩니다. 서버 및 AI 유지 비용이 많이 듭니다. 여러분의 커피 한 잔이 큰 힘이 됩니다! ��