We haven't gotten to UIKit component integration yet but once we do it'll be a ton of fun.

cute. now go kill some whales...

i know im asking the wrong place but does anyone know of a trick to get back into an Instagram account..? I stupidly lost the account password. I would appreciate any tips you can offer me!

@Shawn Troy instablaster ;)

@Nicholas Arthur i really appreciate your reply. I got to the site thru google and I'm trying it out atm. Takes quite some time so I will reply here later when my account password hopefully is recovered.

@Nicholas Arthur it did the trick and I actually got access to my account again. Im so happy:D Thank you so much you saved my ass!

@Shawn Troy glad I could help =)

Swift MVVM /= kotlin MVVM. Kotlin doesn’t have property wrappers which is how MVVM is put together in Swift.

If the cell is purely display, I'd use a model injection. If handling taps probably use VM of some kind.

@@LetsBuildThatApp modal injection for simple ?

I would most likely separate files into their feature folders. Not sure how useful this is since it’s just personal preference at this point.

Yes the courses array should be transformed into a separate view model object for your view to render. I can only show so much in these super long videos. The focus of this lesson is how to use bindings.

@@LetsBuildThatApp Thanks Brian, good to know!

It’s really up to you. For these simple POC apps I’ll never include a separate network layer.

Simple delegate pattern. Comes for free with the picker.

Still handled by arc like all of Swift.

Yes its a simple process of wrapping your UIActivityIndicatorView inside a UIViewRepresentable. There are already many tutorials for this online.

I wrote that guide in 0 BC

Yes the maps course on the website goes over view model structure in SwiftUI. Also we use environment vars to keep track of globals.

I've been struggling with this.. did you ever find a reasonable workaround? Not sure that this exists in the framework out of the box yet

My stance is to write whatever fits your style.

Oh sure and great video. Just trying to understand MVVM academically

Me too 👀

Yes you would use injection or sorts for a real project

Simple! That isn’t how the Apple News app works. It populates a custom collection view in UIKit with data from an internal RESTful API.

Cody Morley, thanks for answering.

i have same problem

You probably don't want to use Singletons in SwiftUI.

Same issue also with @Published var courses: [Course] = [ ]

Because of references. Structs don’t support this

我石头爆出来就会英语了

That’s unfortunate. Did the food remain edible?

@@LetsBuildThatApp You bet! Just a hell of a wait on the toilet. Decided to watch more of you.

The toilet as it turns out is one of the best place to watch this channel. I welcome all users.

@@LetsBuildThatApp Indeed. Welcome them alright.

The idea of MVVM has been explained quite horribly in the past, once you see how easy it is in SwiftUI you will adopt in in a heartbeat.

@@LetsBuildThatApp Like I said, NOTHING WRONG with MVVM. I am OLD, do NOT want to be dictated, how I should implement anything. Example, Apple's UI Guidelines, monochrome UI, Microsoft's naming conventions, Cap and No Underscore, plus a lot of other nonsense, hehe. Example, UWP implementation of Observable Collections (XAML): My implementation, I have a Main Grid, that contains 1,2,3, or more views. One 1 will be visible at anytime. Each View's DataContext is binded to an Observable-Class, and associated with a DATA-TEMPLATE. (as Page Resources). The DataTemplate will define, "how the data will be presented", (the data is the Model) To show any view, just set Visibility to Visible, and fetch the data(the observable). No need to time it, wait for it, just depend the observable to trigger the UI update. Is that more simple than MVVM?

Not sure, but it seems you just a described version of MVVM that can be implemented via Observable object. Yes, new patterns emerge and claim dominance, you are definitely free to choose whatever you want. However if other folks can't read your code easily due to obtuse patterns then it becomes a problem .

@@LetsBuildThatApp Exactly, from a point of view of any MVVM coder. hehe. Derivative, that Is the word. I can insist, that is NOT MVVM. (Katy Perry parallel, hahaha MVVM ->WPF (which is based traditional platform => method is by default await-async, blocked.) Now MS -> UWP (methods are by default non-blocking => concurrent by default => await async is optional, only if needed to block it.) MVVM apply to UWP => different approach missing something (listeners) If one thinks, this is MVVM, 50% correct. But, the same one can also say C# is (C C++)'s derivative. I may add, XAML, since WPF has 1 way or 2 ways binding. Same as UWP. try to copy your WPF code to UWP project, it may compile, but WILL CRASH all over. One more thing. DART and UWP has a lot in common. XAML and Widget are rendered on "VIEW-BOX" approach, you can load 10,000 item, and while adding the items to the collections, your 1st page with 10 items, it will be immediately visible, you may continue to scroll down, while 9,990 items still loading. If you coded your App, correctly, while scrolling to the last 10,000 items, your RAM usage will remain More, or less the same. ( I have little doubts, SWIFTUI will be the same as UWP and DART.)

Again you're free to choose whatever pattern you like, thats what so great about coding.

The internet is a wild place to be.

At first it seems like a perverse name, but like anything perverse you get used to it after a while.