Settings View

SWSettingView (NavigationStack)
  |
  |--- General Settings Section
  |       |--- Language Picker (English / Chinese via @AppStorage)
  |       |--- Share App (ShareLink with App Store URL)
  |
  |--- Legal Section
  |       |--- Terms of Service (Link)
  |       |--- Privacy Policy (Link)
  |
  |--- Recommended Apps Section
  |       |--- App links with icon images (labelWithImage helper)
  |
  |--- Account Actions Section
  |       |--- Sign Out (Button + confirmation alert)
  |       |--- Delete Account (destructive Button + confirmation alert)
  |
  |--- Version Info Section
          |--- App version + build number from Bundle

Key design decisions:

• Platform-specific views — separate SWSettingView+iOS.swift and SWSettingView+macOS.swift files, sharing the same data model and configuration.
• @AppStorage for language — persists the user's language preference across launches without a dedicated settings store.
• Confirmation dialogs — both sign-out and delete-account require explicit user confirmation to prevent accidental actions.
• Configurable constants — URLs and app links are declared as private let properties at the top of the struct for easy customization.

1. Copy SWSettingView+iOS.swift and SWSettingView+macOS.swift into your Xcode project (e.g., under a Settings/ or Module/ group).
2. Update configuration URLs — replace appStoreURL, termsURL, and privacyURL with your actual values.
3. Add app icon images — the recommended apps section references ImageResource assets (.smileMaxLogo, .fullpackLogo, etc.). Either add matching assets to your asset catalog or remove/replace the recommended apps section entirely.
4. Wire up account actions — replace the signOut() and deleteAccount() TODO stubs with your real authentication logic (e.g., calling SWUserManager if you use the Auth module).
5. Embed in your app — add SWSettingView() to your TabView or navigation hierarchy:

   TabView {
       Tab("Settings", systemImage: "gearshape") {
           SWSettingView()
       }
   }

1. Language switching — if your app supports multiple languages, ensure other views also read from @AppStorage("appLanguage") to stay in sync.

1. Image assets required — The recommended apps section uses ImageResource references (.smileMaxLogo, .fullpackLogo, etc.). If these assets are missing from your asset catalog, the build will fail. Either add placeholder images or remove the section.
2. @AppStorage("appLanguage") does not change Locale — This preference key is app-level only. It does not override the system locale. You need to read this value in your views and conditionally format dates, numbers, and strings accordingly.
3. Delete account is client-side only by default — The template stub does not call any backend API. If your app has server-side user data, you must implement proper backend cleanup (e.g., Cognito deleteUser + DynamoDB record removal) in the deleteAccount() method. "Cleanup" also means stored files (photos in R2 / Storage — a cascade never deletes them, see infra-supabase-storage §5) and, for Sign in with Apple users, revoking the Apple authorization with a fresh authorizationCode (5.1.1(v)). If the confirmation promises "deletes your photos", the backend must actually delete them.
4. Force-unwrapped URLs — The recommended app URLs use URL(string:)!. If a URL string is malformed, the app will crash. Verify all URL strings are valid before shipping.
5. Sign Out does not navigate — After signing out, the view remains on the settings screen. You typically need to observe the auth state at a higher level (e.g., in your root view) and switch to the login screen when the user becomes unauthenticated.