Your course is excellent, beats all others I've seen hands down! Your course/videos clearly show how to use the different items with thoughtful examples and explanations. This video explains what I found to be the most confusing, when to use @StateObject and @ObservableBbject. Looking forward to the Environment video. Thank you for taking the time and effort to create this course, it sets the gold standard!

I am SO happy I found your channel. Amazing quality. Great clear communication, sympathy for newbies, explaining everything, quality mic, everything. Thanks for all your hard work!

Nick. I am a CTO who was trying to learn Swift for fun. I had visited a lot of material and I find your approach to be the best. Beats even the paid materials by a long distance. My best wishes and do let me know how we can help contribute to you besides referring. You should be hitting at least 100K viewers.

Not only describe the concept in a straightforward way but also tells the use cases of real projects. GOD bless on you.

your boot camp is incredible awesome!!!

This was very well explained! Thank you Nick!

Dude these tutorials are amazing! Keep up the good work!

I love the way you explained the diff between @state and observable object. So abundantly clear

I have watched over 10 different tutorials on youtube around this concept, you have explained this concept much much much better and cleaner and underestandable than any other tutorial. Thanks a lot!

I have been watching your videos for a few days now. I also watch some others content creators as well. Out of all the ones I watch I find yours to be excellent and unique. You are the first person to actually make videos explaining each thing in great detail. All the others just build apps that get followed with maybe some explaining. Thats great too but this is helping me learn so much better.... So Thank You for making all of these and I hope you never stop!

Amazing explanation! Love all your videos. I was a little confused before and this kinda cleared everything up.

Thank you Nick. You explained how to use @StateObject and @ObservedObject perfectly.

Best explanation of these property wrappers. I’ve spent months trying to grasp managing state and it has been so confusing. This tutorial wasn’t so overly complicated like so I actually grasped the concepts. This entire channel is GOLD!

What a great video. Perfect pacing, perfect explanations, and I like how you reinforce important concepts. Thanks again.

Your explanation techniques is unique and simple..I love it. 👍

Man really solved my doubt about @StateObject and @ObservedObject. Please make sure videos like these. It’s amazing

Brilliant video! Wonderfully clear and perfectly explained👍👍👍

Omg, you gave me the missing piece I was looking for! Thank you so much! Great content!

Wonderful for understanding state, stateobj and observable object. Thanks a bunch

First video I watched from you. Great explanation, easy to understand. Now I have to watch your other videos too :)

Great explanation! Thank you👍👍👍👍

What a well done video ! Kudos to you !

This video explains a lot about the @ObservableObject and @StateObject. I literally learned what those are and how they are used. Thanks a lot for this video. :)

Great video. Thanks Nick.

thank you it's by far the best explanation i found for this subject!

You're the best, dude! I've been doing this Hacking with Swift course, but I was so confused with the fundamentals, and you are explaining it so simply! I'm very grateful. Thanks.

Excellent video. Wonderful explanation. I knew most of this stuff but I learned many small details.

Great explanation. Thank you so much!

Thank you so much! I finally got it. Amazing video)

Perfect, perfect, perfect! Every day I learn from your videos. You were not the first in my path, but by far the best. I have never understood complex topics so easily, as I began to understand with you. Clear beautiful speech allows me to understand you (English is not my native language). I'm very happy that I found you. I feel that one mug of coffee will not be enough)) The material costs a whole mountain of mugs of coffee

Brilliant - you just cleared up for me, why my app reloaded data at times, when I did not want it. And what to do about it. Many thanks.

Awesome! 👏

Thanks from the bottom of my Heart Mate ❤💚

Very well explained !!

Proud coffee member on a monthly basis now🥳. Please do not stop teaching!

please don't stop you make life easier and more simple ♥

Dud you're amazing! Thanks a lot!

Great vid as always. Keep it up! Loving this content and leaving comments to make your YT algorithm better!

Top quality course 😍

All courses are amazing. You are the best.

Another great video, Nick! This is probably the most crucial one to date in the Bootcamp series, IMHO. I have a feeling I'll be coming back to it again several times. I've watched a lot of the WWDC videos, but they still left me a bit confused on what the difference was between @StateObject and @ObservedObject and when to use one over the other. In fact, I think I had them backwards in my head, but this video has helped them click into place.

Excellent lessons !

Great explanation, thanks

Wonderful explanation!!! Thank you so much for investing your time making this videos.

keep doing what you doing man

Sooo good explanation thanks mate🎉👍

This video saved my life. Thank you.

There are so many great ideas in this video thnk you

Great, your teaching method is very understandable and helps me a lot, thanks a lot

Really well explained :)

I started working on SwiftUI and I got stuck at @State and @StateObject, I found your video on the @StateObject, I found this very helpful and now I am planning to learn SwiftUI from your playlist instead of other platforms. Thanks for creating excellent content.

great tutorial, keep up the good work

very well explained!

Thank you! You are our lifesaver❤

Once again I must thank you for this video. It explains things so well where as other videos, that got me started, excluded key points and ended up in a mess when I attempted to create the project I have been tasked with. I am just about to embark on updating my app and feel confident that this has got me over the rather confused situation I had ended up in. I almost feel guilty for getting all your tutorage for free and hope you are generating some revenue from this marvellous series. Thank you once again!

You do such an absolute great job explaining the code. I will now have to give you the title, SMSMI (supreme master swift mentor and instructor). Thanks for a world class video. Bob

Great video! Thanks.

Great Video. Thank you !!!

This is one the best and the most interesting SwiftUI course... so thanks You so much.

Another excellent video. Thanks very much. It’s very well explained.

sir congratulations you have the best course covering swiftui

Thank you so much for great explanations

The Best! Thanks!

thanks man, fantastic video

Thank U! I am new on programming

Thanks a lot very clear with an exhaustif example

I discovered you a few ago . I think that your videos is useful very .Thanks.

Oh man you are a great teacher love from Pakistan

Very Good!!!

We ❤️ to hang with u here! 🥳

thank you very much

Additional notes for Swift beginners: * At 14:08. If the code is too long, you can remove ': FruitViewModel' from the var declaration, because type of the var is always FruitViewModel.

Super! thx man

Hey Nick, thanks for another amazing video. I said that many times but will say here again; I watched bunch of tutorials about @ObservableObject, @ObservedObject and @StateObject but this is the first time I understood the logic. Your teaching method is just awesome.

Finally i got clear concept of why, when and where we can use Identifiable, ObservaleObject, @StateObject, @ObservedObject. Thank you Nick

you are the best

Hey Nick, thank you for the amazing video - it is very handy. I have maybe a dumb question. If you refactor the entire List into a separate struct and then use the reference to this struct in your home view. Where should @StateObject be? In the home view, right?

My brain is burning lmao thanks for videos bro btw

I love it!!!!!!!!!!!!!!!

Nick i've finished both swift and swiftui bootcamp, came back to this vid to grasp a little bit more on this, thank you for your good work, please let us know if you have a site to "Buy you a coffee" or somehow retribute some of the knowledge you've given to us.

Thank you your video. How to use button delete instead onDelete() for List ?

😋👏👏👏 Very good 👌

Nick, thank you so much for your lessons, do you have core data lessons? i did't find it

underrated

Thanks again for an excellent video. You did (as always) and excellent job explaining classes. I do have a question though, in SwiftUI what is the difference between structures and classes; they look pretty similar at first glance (I don't know if classes can also be used to create views but other than that one may think they can be used interchangeably).

can you make a video on firebase or Vapor

This is about a ShoppingList app I am working on. I select certain items by tapping on a check box from MasterList and append to a viewModel class instance with the selected Items. I want to populate the list on the next View when a button on ToolBar status on the master List View is clicked. I have separate viewModels for MasterList and SelectedList. But the selected List does not show any items in the second View though items are appended. How do I initialize the selectedList ViewModel on the child view. Thanks for the bootCamp videos. For now, I am passing the selected Items array in NavigationLink and initializing the selectedListViewModel with this array in View2. Is there a better approach?

I know there is a back button, but in general since the one in video is deprecated to dismiss a screen use @Environment (\.dismiss) var dismiss then in Button just write dismiss()

Is it common and good practice in iOS Dev to pass viewModels around like that? Shouldn't RandomScreen (and each screen) basically have it's own ViewModel? And both ViewModels would access data from a common data storage which would be located lower in the general app architecture?

this is beyond me, I'll have to start all over, or get 'boot' out. haha... I started back at Bootcamp #1 🤣

towards the end, what if you wanted to pass data from 1 fruit in the array into the next screen.? instead of passing the whole array

quick question. If I wanted to ensure that the data persists when that application is closed , would I need to save the information in coreData?

hey Nick, since naviagtionBarItems is going to be deprecated do you ming making a video addressing that and how to go around it in the future thank you so mcuh !

Yo! So is it possible for the SecondView to update the information regarding the fruits (eg. changing the fruit count) in the first view?

OMG thx so much.I have been struggling about how the fuck updating data works

Nick, we all need your help about initialization of StateObjects. Please, can you explain about initialization of it? When my view getting parameters on init, which I need to initialize StateObject? What i have to do? I heard somewhere, that initialization of StateObject in init of view - is not good idea. But it's very often case. I'm looking information about it, but nothing ...

where have you been all this time

Two years has passed from now and I just watched this video. Things have changed and I don't know if the reloaded items issue when onAppear method is called (28:34) it's still being a problem or we don't need to worry about anymore. If someone could answer my question would be useful

Nice video Thanks for taking time and making these videos. Is there any example to checl When to use @StateObject and @ObservableObject. I want to check how @Observable object behaves when view is reloaded.

Great video, as all the others. But: isn't the rule of thumb to use @ObservableObject when you pass in your view model from the outside (i. e. you pass the view model into the view as a parameter) and to use @StateObject when you create the view model inside the view (as you do in the sample code)? So @ObservableObject var fruitViewModel = FruitViewModel() is actually a no-go?