watchos-code-review

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Issue Type	Reference
App lifecycle, scenes, background modes, extended runtime	references/lifecycle.md
ClockKit, WidgetKit, timeline providers, Smart Stack	references/complications.md
WCSession, message passing, file transfer, reachability	references/connectivity.md
Memory limits, background refresh, battery optimization	references/performance.md

问题类型	参考链接
应用生命周期、场景、后台模式、扩展运行时	references/lifecycle.md
ClockKit、WidgetKit、时间线提供器、智能堆栈	references/complications.md
WCSession、消息传递、文件传输、可达性	references/connectivity.md
内存限制、后台刷新、电池优化	references/performance.md

SwiftUI App protocol used with
```
@WKApplicationDelegateAdaptor
```
for lifecycle events
```
scenePhase
```
read from root view (not sheets/modals where it's always
```
.active
```
)
```
WKExtendedRuntimeSession
```
started only while app is active (not from background)
Workout sessions recovered in
```
applicationDidFinishLaunching
```
(not just delegate)
Background tasks scheduled at least 5 minutes apart; next scheduled before completing current
```
URLSessionDownloadTask
```
(not
```
DataTask
```
) used for background network requests
WidgetKit used instead of ClockKit for watchOS 9+ complications
Timeline includes future entries (not just current state); gaps avoided
```
TimelineEntryRelevance
```
implemented for Smart Stack prioritization
WCSession delegate set before
```
activate()
```
; singleton pattern used
```
isReachable
```
checked before
```
sendMessage
```
;
```
transferUserInfo
```
for critical data
Received files moved synchronously before delegate callback returns

Is the app using modern SwiftUI lifecycle with delegate adaptor?
Are background tasks completing properly (calling
```
setTaskCompletedWithSnapshot
```
)?
Is UI update frequency reduced when
```
isLuminanceReduced
```
is true?
Are WatchConnectivity delegate callbacks dispatching to main thread?
Is
```
TabView
```
nested within another
```
TabView
```
? (Memory leak on watchOS)