Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Have we talked about MVVM lately?

21,511 Aufrufe • vor 1 Jahr •via X (Twitter)

12 Kommentare

Profilbild von Damjan Dabo
Damjan Dabovor 1 Jahr

It’s funny how most examples of moving away from MVVM still put important logic in the views, logic that really should be tested, but usually isn’t. Then again, for indie devs… who’s testing anyway? 😅

Profilbild von Alex Fallah
Alex Fallahvor 1 Jahr

I’d like to see you talk about the pros and cons of mvvm. Besides “here’s a guy who made an article. This is trendy” “here’s a fancy code snippet”. Mvvm helps separate business logic from view logic. None of the code samples you show or in the article are great examples of it.

Profilbild von MO
MOvor 1 Jahr

No magic here. A lot of code requiring testing is basically just dumped in the View. Loading state can’t be unit tested; Snapshot test becomes more complex. This approach is similar to the original idea of just putting everything in a single file.

Profilbild von Eric Ampire
Eric Ampirevor 1 Jahr

the UI shouldn't have logic, the ViewModel or call it what you like is intended to ensure that the UI can only be responsible for displaying things on the screen that's all, by putting the logic in the UI, this logic becomes strongly coupled to the UI and reduces code reuse, as very often several UI components share the same logic.

Profilbild von Kendall Gelner ᯅ
Kendall Gelner ᯅvor 1 Jahr

I also agree with this, from what I can tell this is a better approach.

Profilbild von Alzea | Orenji Studio
Alzea | Orenji Studiovor 1 Jahr

I don't care. MVVM rules!

Profilbild von Dark Mouse Software
Dark Mouse Softwarevor 1 Jahr

When you have a delegate (like didFinishPlayingAudio or didEnterRegion), do these still have to be used in a class? I've been creating the Class (I call AppManager), which I insert as an EnvironmentObject.

Profilbild von Musca
Muscavor 1 Jahr

Great idea to post snippet of your YouTube video here on X 👌🏻

Profilbild von Himanshu Kumar
Himanshu Kumarvor 1 Jahr

Architectural patterns in codebases can bring elegance. When chosen well, they enhance maintainability and testability. This deserves ongoing discussion.

Profilbild von Lonnie Jordan
Lonnie Jordanvor 1 Jahr

If you use UIKit then use MVVM. not necessary with SwiftUI.

Profilbild von Marc Stibane 📯
Marc Stibane 📯vor 1 Jahr

"The magic is in the environment" - except that you cannot change an environment value, then use NvigationLink to push a new view on the stack, because for SwiftUI these are siblings - the pushed view is NOT a subview of the first and doesn't receive the changed value. Bummer!

Profilbild von Average European Citizen
Average European Citizenvor 1 Jahr

Sean, MVVM is not an architecture, is a presentation pattern, it belongs in the presentation layer.

Ähnliche Videos