Hey Stewart! Probably not easy to fix, but I think the arrow at 04:19 is pointing to the wrong variable? Should be 'number', not 'name'. LOVE your content. Thanks so much for producing it!
The section at 24:24 is worth its weight in gold. Many thanks. Totally agree with your suggestion to Apple. I was flummoxed until I watched your video.
Have just started using swift coming from react and typescript. Must say the new changes in observation framework really makes it much more simpler. This makes injecting dependencies into child views a lot more maintainable and allows me to write less code. Thank u for this excellent explanation of this new feature! It will save me a lot of time when building new apps! ❤
Thank you so much.! I’ve been wanting to get on this but really needed to make sure I understood how it worked first and as always you did an excellent job providing that.
Thank you Stewart for this very nice introduction to @Observable. It lays out the new, simpler way , of using @State, @Binding @Environment and @Bindable. It will be a great improvement over the old ObservableObject. And as a bonus ContentUnavailableView, really super handy in many contexts. I'm looking forward to future videos on @Observable in more complicated contexts. Quick comment on the previous question. The MVVM pattern with ObservableObject does add a layer between the class with the user data and the user interface. I would imagine that the @Observable macro would work in a similar context.
You can use MVVM with @Observable as well, but there are some limitations. For example, you cannot use @AppStorage within a class that uses @Observable macro. I will eventually cover an work around though.
@@StewartLynchperhaps that’s by design? I.E app storage should not be used in MVVM? I’m just getting into the architecture and have come across MV as this is how Apple build their demo apps.
Thank you Stewart for your fantastic efforts, I want to contribute my humble understanding to observation property wrappers (after experiments with migrating legacy code): an object declared with @State is equivalent to @StateObject before. No wrapper before the object (var) is equivalent to @ObservedObject before. If you need to bind a property of an Observable: In case the Observable is defined with @State we can use ($)object.property In the second case, we need to add @Bindable to var and use ($)object.property I hope this helps clarify things.
Excellent video, as always!! Would it be possible to provide a tutorial where data is downloaded from a web service, stored in model objects and displayed in a view? I'm having difficulty saving the retrieved data to the database in a database manager since the model context required for saving the data can only be accessed inside of a view. I would like to adhere to best practices regarding separation of concerns, if possible. Any advice would be greatly appreciated!
Total novice question, but how does this relate to the Swift Data and Model macro? As I’m working on a new app, I don’t mind targeting the latest release, should I ignore this amazing explanation and move straight to using Model?
Thank you very much! This is very nice! It's so confusing as I learn this: Binding, @Binding, @Bindable, easy to fix all these up. My Xcode 15b6 doesn't auto compile the view body when I type in struct Foo: View { }, compile fixit insert "typealias VIew ...", not var body
Hello! Great video. Just an important question. Why are you using @State for the User custom type at the beginning in the first example, when Apple in their video of WWDC clearly say that you shouldn’t use it with the new Observation Framework? You can just use “user” as a variable without any wrapper in front. @State should be used exclusively if part of the view and if bindings are necessary.
Yup. you are absolutely correct. @State was not necessary until I added the toggle to the isHappy property after which I need to use @State. Thanks for pointing this out. I already have a pinned comment so I can't pin yours to the top. I wish there were a way to edit TH-cam videos and maintain the url.
@@StewartLynch Thanks a lot for your prompt answer Stewart!! ☺️ Anyway I have to say that Apple didn’t make it crystal clear the usage. I mean, when before ios17 I had to use @StateObject, can I know omit any wrapper? And when passing an object that before I had to declare as @ObservedObject in a child view, now I can use nothing too? Is Observation framework managing ownerships automatically? Thanks!
The best way to figure this out is to try it without any macro (not a property wrapper) and see if you get any errors thrown. If you don't then you likely do not need it.
@13:55 wish you'd explain how to use the Extract Subview command. You've given so many hints for streamlining work flow, but not extracting subviews. 😜
I seldom if ever use it as I find it easier to do it manually. Half the time the extract subView does not work for me and it places the subview in a location I do not want and I end up having to rename it.
Quick question: How does this new framework work with MVVM? In iOS 16, I would create a Model struct and a ViewModel ObservableObject class to handle the model logic. Now, models are Observable classes. Where does the ViewModel logic to manipulate the model go? a new class? the existing model class? is MVVM still even relevant?
@@indiekiduk MMm, I think that's a bit theoretical. In every day Swift we put logic in to objects all the time. Functions have containers, and associated data all the time, after all. There's nothing wrong with using View Models and references to data managers, stores. In fact, it's the norm. Shared mutable state better served by containerisation and isolation through things like actors.
I have 3 views. Grandparent Parent Child Child contains the textField component and variable name is textInput. I want to pass the textInput value to parent and from parent to grandparent. Can I use Observable Object?
YOu need to use Bindable if you are injecting an object from another view or the environment. a State object is for a single view only and will not update values in other views.
@@StewartLynch Ah, now I see. Before, I did not run the app and only used the preview where everything looked perfectly. Now that I’ve run the app with @State instead of @Bindable, I’ve got this violet error telling "Accessing State's value outside of being installed on a View. This will result in a constant Binding of the initial value and will not update." Thanks for the explanation!
No. That is not it at all. @State is only used to initialize an observed object if it is only used within that View. If the object is an observed object created elsewhere and is being used in the view it must be @Bindable
I just rewatched that video, and I don’t see where I said that. Can you give me a time stamp? @StateObject -> @ObservedObject but now, @State for an observed object -> @Bindable. @Binding and @Bindable are different
@@StewartLynch at 00.38 second at the begining of video @BIndable is instead of @observedObject if that correct ?it also instead of @EnvironmentObject or any subview of view or instance of struct or class also ? i think all of them one way binding not two ways binding like new @Bindable . about difference between @Bindable , @Binding is clear thanks for your great content
u can inject State objects which are oberved into the environment. As I show at the end of the video, if you want to be alble to update a proprety in an Environment State object, you will need to introduce Bindable into your view and assign the State object to the variable with the Bindable property wrapper. I don’t see where there are any mistakes in my explanation, but if so, I would really like to clear it up.
@@StewartLynch new property wrapper @Bindable is two ways binding but @ObservedObject is one way binding they are not alternatives for each other u said at 38 second of video first minute
I think you are incorrect here. I have a sample project that I would be happy to send to you if you want to reach out to me by email to continue this conversation. It clearly demonstrates the parallels between @State/Observation framework -> @Bindable and @StateObject/@ObservableObject -> @ObservedObject
Hey Stewart! Probably not easy to fix, but I think the arrow at 04:19 is pointing to the wrong variable? Should be 'number', not 'name'. LOVE your content. Thanks so much for producing it!
Oops. Good catch. You are right though. The only way to fix it is to upload a new video and that would break the link. I will pin your comment.
Brilliant explanation, thank you very much
Glad it was helpful!
very clear explanation! Keep up the good work!
Thanks, will do!
I've finally(finally..) grasped the concept of environment and observation🥳 Thank you so much!!
The Observation framework is a huge improvement on the old situation. I expect a fix for the Environment situation in the future ... Great vid!
Always appreciate all your great and intuitive example for walkthrough the Observation framework 🙏
The section at 24:24 is worth its weight in gold. Many thanks. Totally agree with your suggestion to Apple. I was flummoxed until I watched your video.
Thank you Stewart 💯
Have just started using swift coming from react and typescript. Must say the new changes in observation framework really makes it much more simpler. This makes injecting dependencies into child views a lot more maintainable and allows me to write less code. Thank u for this excellent explanation of this new feature! It will save me a lot of time when building new apps! ❤
Glad it was helpful!
Thank you so much.! I’ve been wanting to get on this but really needed to make sure I understood how it worked first and as always you did an excellent job providing that.
Glad it helped!
Very useful introduction to this change.
Awesome explanation Stewart! Its clear, and steady which helps me as a beginner. Keep it going, I’ve just subscribed 🎉
Glad you think so.
Awesome video, as always, Stewart. Thank you so much for sharing :)
amazing content Stewart! Crystal clear explanations, earned my sub for sure!
Welcome aboard!
Thank you Stewart for this very nice introduction to @Observable.
It lays out the new, simpler way , of using @State, @Binding @Environment and @Bindable.
It will be a great improvement over the old ObservableObject.
And as a bonus ContentUnavailableView, really super handy in many contexts.
I'm looking forward to future videos on @Observable in more complicated contexts.
Quick comment on the previous question.
The MVVM pattern with ObservableObject does add a layer between the class with the user data and the user interface. I would imagine that the @Observable macro would work in a similar context.
You can use MVVM with @Observable as well, but there are some limitations. For example, you cannot use @AppStorage within a class that uses @Observable macro. I will eventually cover an work around though.
@@StewartLynchperhaps that’s by design? I.E app storage should not be used in MVVM? I’m just getting into the architecture and have come across MV as this is how Apple build their demo apps.
Great video, thanks! Helped me glue together why, in the apple example projects, they are using @Bindable in the View body 😄
Awesome. I like the way you explain things, Please keep it up!
Thanks, will do!
Thanks Stewart. Great teaching
Thank you Stewart for your fantastic efforts, I want to contribute my humble understanding to observation property wrappers (after experiments with migrating legacy code):
an object declared with @State is equivalent to @StateObject before.
No wrapper before the object (var) is equivalent to @ObservedObject before.
If you need to bind a property of an Observable:
In case the Observable is defined with @State we can use ($)object.property
In the second case, we need to add @Bindable to var and use ($)object.property I hope this helps clarify things.
Excellent video, as always!! Would it be possible to provide a tutorial where data is downloaded from a web service, stored in model objects and displayed in a view? I'm having difficulty saving the retrieved data to the database in a database manager since the model context required for saving the data can only be accessed inside of a view. I would like to adhere to best practices regarding separation of concerns, if possible. Any advice would be greatly appreciated!
I will likely do something like this later in the year.
Thank you so much for this ☺
Awesome as always, thank-you!
Total novice question, but how does this relate to the Swift Data and Model macro? As I’m working on a new app, I don’t mind targeting the latest release, should I ignore this amazing explanation and move straight to using Model?
SwiftData is a persistence layer that already uses the Observation framework.
Thank you very much! This is very nice! It's so confusing as I learn this: Binding, @Binding, @Bindable, easy to fix all these up.
My Xcode 15b6 doesn't auto compile the view body when I type in struct Foo: View { }, compile fixit insert "typealias VIew ...", not var body
Hello! Great video. Just an important question. Why are you using @State for the User custom type at the beginning in the first example, when Apple in their video of WWDC clearly say that you shouldn’t use it with the new Observation Framework? You can just use “user” as a variable without any wrapper in front. @State should be used exclusively if part of the view and if bindings are necessary.
Yup. you are absolutely correct. @State was not necessary until I added the toggle to the isHappy property after which I need to use @State. Thanks for pointing this out. I already have a pinned comment so I can't pin yours to the top. I wish there were a way to edit TH-cam videos and maintain the url.
@@StewartLynch Thanks a lot for your prompt answer Stewart!! ☺️ Anyway I have to say that Apple didn’t make it crystal clear the usage. I mean, when before ios17 I had to use @StateObject, can I know omit any wrapper? And when passing an object that before I had to declare as @ObservedObject in a child view, now I can use nothing too? Is Observation framework managing ownerships automatically? Thanks!
The best way to figure this out is to try it without any macro (not a property wrapper) and see if you get any errors thrown. If you don't then you likely do not need it.
@@StewartLynch Yeah, I suppose that most is done under the hood with the new framework…
@13:55 wish you'd explain how to use the Extract Subview command. You've given so many hints for streamlining work flow, but not extracting subviews. 😜
I seldom if ever use it as I find it easier to do it manually. Half the time the extract subView does not work for me and it places the subview in a location I do not want and I end up having to rename it.
Thank you!
You're welcome!
Thanks!
Thank you very much
How can you propagate a logout or login change from within a subview toggle in the appstate environment object without injecting it in every subview?
Valeu!
Merci Beaucoup
Quick question: How does this new framework work with MVVM? In iOS 16, I would create a Model struct and a ViewModel ObservableObject class to handle the model logic. Now, models are Observable classes. Where does the ViewModel logic to manipulate the model go? a new class? the existing model class? is MVVM still even relevant?
You can use @Observable the same way as you used ObservableObject with MVVM.
MVVM was never relevant to SwiftUI because the View struct is a view model already so you don't need any objects.
@@indiekiduk Not really. It's often better to keep a View as simple as possible, and put related logic out in to another object: the View Model.
@@w0mblemania in Swift logic goes in funcs not objects. That way you prevent the shared mutable state problem Swift and SwiftUI was designed to fix.
@@indiekiduk MMm, I think that's a bit theoretical.
In every day Swift we put logic in to objects all the time.
Functions have containers, and associated data all the time, after all.
There's nothing wrong with using View Models and references to data managers, stores.
In fact, it's the norm.
Shared mutable state better served by containerisation and isolation through things like actors.
I have 3 views.
Grandparent
Parent
Child
Child contains the textField component and variable name is textInput. I want to pass the textInput value to parent and from parent to grandparent.
Can I use Observable Object?
Yes, as long as it is observed in all of the views. You could inject it into the environment.
Helpful video as usual. :) There seems to be a bug at least with Xcode 15 beta 6. Whenever you toggle isLoggedIn. It goes back to tab 1.
Why should I ever consider using @Bindable if @State works just fine in its place?
YOu need to use Bindable if you are injecting an object from another view or the environment. a State object is for a single view only and will not update values in other views.
@@StewartLynch Ah, now I see. Before, I did not run the app and only used the preview where everything looked perfectly. Now that I’ve run the app with @State instead of @Bindable, I’ve got this violet error telling "Accessing State's value outside of being installed on a View. This will result in a constant Binding of the initial value and will not update." Thanks for the explanation!
As far as I get it, I should only use @Bindable in cases where @State is not enough
No. That is not it at all. @State is only used to initialize an observed object if it is only used within that View. If the object is an observed object created elsewhere and is being used in the view it must be @Bindable
@@StewartLynch That is a great answer. Thank you again!
@Binding is not used instead of @ObservaedObject not correct
I just rewatched that video, and I don’t see where I said that. Can you give me a time stamp? @StateObject -> @ObservedObject but now, @State for an observed object -> @Bindable. @Binding and @Bindable are different
@@StewartLynch at 00.38 second at the begining of video @BIndable is instead of @observedObject if that correct ?it also instead of @EnvironmentObject or any subview of view or instance of struct or class also ? i think all of them one way binding not two ways binding like new @Bindable . about difference between @Bindable , @Binding is clear thanks for your great content
u can inject State objects which are oberved into the environment. As I show at the end of the video, if you want to be alble to update a proprety in an Environment State object, you will need to introduce Bindable into your view and assign the State object to the variable with the Bindable property wrapper. I don’t see where there are any mistakes in my explanation, but if so, I would really like to clear it up.
@@StewartLynch new property wrapper @Bindable is two ways binding but @ObservedObject is one way binding they are not alternatives for each other u said at 38 second of video first minute
I think you are incorrect here. I have a sample project that I would be happy to send to you if you want to reach out to me by email to continue this conversation. It clearly demonstrates the parallels between @State/Observation framework -> @Bindable and @StateObject/@ObservableObject -> @ObservedObject
Thanks!
Thank you very much
Thanks!
Thank you again