ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: WWDC26: Modernize your UIKit app | Apple

Hi, I'm Michael Ox, an Engineering Manager on the UI Frameworks team.

⏸ หยุดชั่วคราว

ความเร็ว:

166 ประโยค

หากประโยคสั้นหรือยาวเกินไป กดที่ Edit เพื่อปรับแก้

Hi, I'm Michael Ox, an Engineering Manager on the UI Frameworks team.

And today, I'll tell you how to modernize your UIKit app.

In this video, I'll tell you about some big changes to app adaptivity requirements and how iPhone apps are fully resizable.

Next, I'll present some new APIs in tab bars, navigation bars and menus.

Then, I'll talk about how to support Apple intelligence and some changes you should be aware of.

And finally, I'll cover a new skill that helps an agent to handle most of this modernization work automatically.

Let's get started with app adaptivity.

Your app can already appear in many different environments.

There are different screen sizes and apps can run side by side with other apps and even themselves.

On iPad, people expect apps to resize and move to external displays seamlessly.

On iPhone, people expect apps to work in both portrait and landscape orientations.

They also expect to mirror their iPhone to the Mac.

In iOS and macOS 27, this experience has been improved, and apps running in these environments are now exposed to many

of the dynamic changes any app native to the platform needs to support.

When people use iPhone mirroring on the Mac, they can fully resize the iPhone window, allowing your apps to resize and adapt.

Likewise, an iPhone-only app running on iPad will be fully resizable like any other iPad app.

Because of this, it is important that your app dynamically adjusts to any available scene size at runtime.

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

and have it dynamically adjust to the environment it is running in.

I will cover the most important steps and common issues you might encounter when making your app more adaptive.

Verifying your app is no longer using App Lifecycle and instead has adopted Scene Lifecycle, the basis for any adaptive app.

Making sure your app is not using main screen references.

And how to handle user interface idiom and interface orientation checks.

The first step is to move from App Lifecycle to Scene Lifecycle.

Most apps are already using Scene Lifecycle.

It is the basis for an adaptive app

and for many of the other tasks I'm going to show you in this video.

UiScene Lifecycle is now required when building with the latest SDKs.

Without it, your application will no longer launch.

Verify that your app is using a UI scene delegate, which is the basis for scene lifecycle.

If you have not yet migrated to scene lifecycle, check out the video Make your UIKit app more flexible from WWDC25,

and read Transitioning to the UIKit scene-based lifecycle in the documentation.

Next, when your iPhone app is mirrored on a Mac, or when a person moves your app to an external display on the iPad,

iPad, the screen associated with your scene changes. That means

that any reference to the main screen in your code will provide incorrect information for the environment your app is running in.

It is important that you do not reference the main screen in your app.

Instead, access the screen dynamically from a Windows window scene.

When a view or view controller is not available in immediate context, pass in a screen reference to any method that needs it.

Even better than fetching the correct screen is to remove screen references altogether.

There are a lot of other APIs that are better suited for an adaptive app.

I'll take you through two common patterns.

Accessing the scale of the screen should be replaced with the trait collection's display scale.

Views and view controllers automatically update their trait collections and provide reasonable fallbacks even when they're not part of the visible hierarchy.

A lot of common override points are also tracked, meaning that you do not need to explicitly monitor for changes.

Instead, the system tracks which trade collection properties are being used inside common layout and drawing methods, like layout subviews, update properties,

draw rect, and many others.

If a change to a tracked trade is detected, the system will ensure these methods are called again, so your UI automatically updates accordingly.

Check out Automatic Trade Tracking in the documentation to learn more.

In places where Automatic Trade Tracking is not available, Register for Trade Changes can be used to observe changes.

This method allows you to set up a closure that is called when a specific trade in the receiving view changes.

Use this to invalidate caches or update other data related to that view.

Check out Adapting Your App When Traits Change in the documentation to learn more.

Another common use of the screen is to check its bounce to get the amount of space available to your app.

However, in an adaptive environment, the space your scene has available is not always the full screen.

So if you still have any reference to screen bounds in your app, now is the time to remove these.

The Window Scene's Effective Geometry provides information on how much space your app has available.

If you need to monitor the Effective Geometry for changes, implement Window Scene Did Update Effective Geometry in your Scene Delegate.

In your Views and View Controllers, instead of referencing the scene bounds, use the available size of your view controller's view

or your view super view to determine how much space is available to it.

This makes your UI less dependent on how it is presented.

It will adjust better when your view controller appears in other contexts, for example inside of a split view controller.

For games, resizing can be challenging.

Due to this, UI Requires Fullscreen is honored on iPhone in resizable environments starting in iOS 27.

Its behavior has also been updated and no longer opts your app fully out of resizing.

Instead, it enables discrete resizing that honors your supported interface orientations.

In discrete resizing, every time a person changes the scene size, the system transitions the scene to a new screen configuration matching that size.

So your game always renders at full quality in the available space.

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.

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.

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.

Stop checking the user interface idiom for any layout decisions in your code.

Use size classes instead to handle sizing constraints such as collapsing menus and updating your app's layout for the available space.

If you need finer control, use the surrounding view size like I mentioned earlier.

Interface orientation also is no longer useful for layout decisions.

In iOS 27, an app-supported interface orientation is a preference provided to the system to the system.

It will be ignored when your app is running in a resizable environment.

You should not consider interface orientation for any layout calculations.

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.

Any interface orientation checks in your app should also be updated to use size classes.

This conceptual shift was introduced in iOS 8.

At WWDC 2014, Bruce Nilo said, a device rotation is only an animated bounce change.

With an array of device sizes, resizable windows on iPad, and resizable iPhone apps on Mac, today this insight is more relevant than ever.

And speaking of interface orientation, in iOS 27, UI View also conforms to the new body protocols from Core Motion and Core Location.

This makes it much easier to configure your motion and location managers.

Connect them to the view that visualizes the motion data, such as a compass or a map view.

This ensures the data is always in the right coordinate space, regardless of interface orientation.

That covers the main adaptivity changes.

Now, here's how to test these changes in your app.

Xcode 27 brings new ways to iterate your app's behavior across

different screen sizes without having to install your app on multiple separate simulators or devices.

In the new DeviceHub app, as well as in Xcode Previews, click the Enter Resize Mode icon.

Then, drag the edges of the device to resize it freely.

This allows you to iterate on your changes quicker.

Once you are satisfied with the results, make sure to test iPhone mirroring and iPad with real devices.

To learn more about the DeviceHub app and its tools, watch Get the Most Out of DeviceHub. And that's adaptivity.

Before I show you a new agentic coding skill

that can help you with the work necessary to make your app fully adaptive, there are two more topics to cover.

First up, bars and menus.

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

TRENDING

ยอดนิยม

เทคนิค Shadowing คืออะไร?

Shadowing เป็นเทคนิคการเรียนรู้ภาษาที่ได้รับการรับรองทางวิทยาศาสตร์ พัฒนาขึ้นสำหรับการฝึกนักแปลมืออาชีพ วิธีการนี้เรียบง่ายแต่ทรงพลัง: คุณฟังเสียงภาษาอังกฤษจากเจ้าของภาษาและพูดตามทันที — เหมือนเงาที่ตามผู้พูดด้วยช่วงเวลาห่าง 1-2 วินาที การวิจัยแสดงว่าเทคนิคนี้ปรับปรุงความแม่นยำในการออกเสียง ทำนองเสียง จังหวะ การเชื่อมเสียง การฟังเข้าใจ และความคล่องแคล่วในการพูดได้อย่างมีนัยสำคัญ

☕ เลี้ยงกาแฟเราสักแก้ว

ShadowingEnglish ยังคงเปิดให้ใช้งาน ฟรี 100% ได้ด้วยการสนับสนุนจากคุณ ค่าใช้จ่ายสำหรับเซิร์ฟเวอร์และ AI นั้นสูงมาก — กาแฟของคุณช่วยให้เราเดินหน้าต่อไปได้! 🙏

บริจาคผ่าน PayPal

ShadowingEnglish.com – ฝึกพูดภาษาอังกฤษแบบ Shadowing

ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: WWDC26: Modernize your UIKit app | Apple

ยอดนิยม

บริบทและพื้นฐาน

5 วลีที่สำคัญสำหรับการสื่อสารประจำวัน

คู่มือการฝึกพูดแบบชาโดว์อิ้ง

เทคนิค Shadowing คืออะไร?

ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: WWDC26: Modernize your UIKit app | Apple

ดาวน์โหลดแอป

บริบทและพื้นฐาน

5 วลีที่สำคัญสำหรับการสื่อสารประจำวัน

คู่มือการฝึกพูดแบบชาโดว์อิ้ง

เทคนิค Shadowing คืออะไร?