@AppStorage vs @Shared(.appStorage)

[daetojemax]

Are there any advantages to using @shared over @AppStorage? I’m using only SwiftUI, and it seems that @AppStorage works exactly the same as @shared in views and view models.

[daetojemax]

Ok, i found the answer in CaseStudies example, sorry.

• In previews and tests, `@Shared(.appStorage)` operates on a quarantined instance of user \
defaults that will not bleed over to other tests, previews or simulators.
• `@Shared(.appStorage)` primarily uses KVO to observe changes to user defaults, which means \
it will update when changes are made from other processes, such as widgets.
• Because of its reliance on KVO, it is possible to animate changes to the value held in \
app storage.

[mbrandonw]

It's also worth mentioning that @AppStorage does not actually work in @Observable/ObservableObject classes. It may seem like it does, but if someone changes the UserDefaults directly (e.g. via set(_:forKey:)), then the state in your class will not update. So it is kinda dangerous to use outside of a SwiftUI view.