# SwiftUI.State: .init(wrappedValue:) vs. .init(initialValue:): what's the difference?

**URL:** <https://forums.swift.org/t/swiftui-state-init-wrappedvalue-vs-init-initialvalue-whats-the-difference/38904>\
**Category:** Using Swift\
**Created:** [July 30, 2020, 8:35pm UTC](https://forums.swift.org/t/swiftui-state-init-wrappedvalue-vs-init-initialvalue-whats-the-difference/38904 "2020-07-30T20:35:21Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![Jon\_Shier](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/jon_shier/32/921_2.png) [@Jon\_Shier](https://forums.swift.org/u/Jon_Shier)\
**Post date:** [July 31, 2020, 6:35pm UTC](https://forums.swift.org/t/swiftui-state-init-wrappedvalue-vs-init-initialvalue-whats-the-difference/38904/19 "2020-07-31T18:35:09Z")

</div>

So to merely set the default value of a `Picker` we need to create a separate type, own an instance outside the view that cares about it, inject it into the view, and use that binding? Even with the new `@StateObject`, that doesn't seem right.

---

_[View the full topic](https://forums.swift.org/t/swiftui-state-init-wrappedvalue-vs-init-initialvalue-whats-the-difference/38904)._