把部署、建站、AI 与网络问题，写成能直接解决问题的文章。

The real pitfall is usually not in the syntax, but in whether the "page life cycle" and "task life cycle" are aligned.

What really determines whether the project can be modified later is whether the state boundaries, page responsibilities and component abstractions are set correctly from the beginning.

The settings page looks simple, but it is actually very suitable for practicing page hierarchy, state ownership and component abstraction.

Many SwiftUI performance issues are caused by state granularity, calculation timing, and view update scope getting out of hand

What really needs to be distinguished is how status changes are observed, propagated and closed.

The real adaptation is not to lock the page into one visual condition from the beginning.

What's really hard is keeping the loading, results, errors, and page lifecycle consistent

What really needs to be distinguished is whether the animation is attached to the state change, or whether it needs to be explicitly wrapped for a specific change.