MV Design Pattern in iOS - Build SwiftUI Apps Apple's Way (Udemy.com)

I really enjoyed the course — it gave me a lot of new insights, especially in terms of architecture and design approaches. I’m still learning how to build apps. I’ve created a simple training app and am now working on a more complex one. In both projects, I initially tried to follow the MVVM pattern, since it’s mentioned in almost every tutorial on YouTube. My usual process is to write all the logic in the View first, and then gradually move it into a ViewModel. Over time, I started running into limitations: property wrappers don’t work in ViewModels, and I often had to write a lot of boilerplate code or use workarounds that didn’t feel elegant. This led me to explore other architectural patterns, and that’s how I discovered the MV approach, which felt much more logical and flexible for my use case. The only thing I still find challenging is testing. UI tests aren’t always predictable, which was also apparent in the testing lessons from this course. I can definitely recommend this course to beginners, as well as to those who don’t want to overengineer simple features just because they chose MVVM.

As mentioned by others there is a backend piece that isn't covered by the lecture. I was able to get by using the instructor's existing endpoints, but that obviously isn't scalable. Otherwise, it was a solid course where each section added value.

Good content, but there are a fair few occasions where the same thing is said far too many times. It’s video, so if something is unclear we can rewind and watch again. For instance, lecture 23, the instructor explains you can use two different URLs—one for test, and one for dev—about a dozen times. Saying the same thing again and again. Not the only time he does this. It’s great content, don’t get me wrong, but get the impression that the course could be half the length if the script was written, edited, and then filmed. This feels like a 'live' commentary where a single point is made again and again, like in a classroom, rather than a video course where you can rewind and rewatch. Feels like a script editor is required to trim down the content.

Started off fantastic, really liked the explanation of Bindings and the underpinnings of how to decide what objects a view needs, which is mostly addressed when discussing MV vs. MVVM model. Those videos are fantastic and worth the cost of the class. Sections 3-5 are disappointing, at least for me, because you can only code along if you already have a server in place with JSON data that can be read and written, and I don't, and suspect that most people also won't, so most of this I listened to at 2x speed and still didn't find very helpful. The testing is a reasonably good walk through UI testing, and I saw in the reviews that the instructor answered questions about UI testing by saying it's more complete than unit testing. I think for a simple app that is true, but in a complex app, learning how to unit test is very valuable, and the thing I REALLY was looking forward to is learning how to write Unit Tests that would allow me to test and debug my data store, which is CloudKit. UI testing has not been sufficient for me to figure out how to fix my CloudKit data store, since it fails without much information. So overall thus far, the instructor is clearly knowledgeable and engaging, and the project is well thought out and paced well. But I think its utility is limited given its connection to an existing and functioning JSON data store which is not replicable from the course materials, and the fact that UI testing is not likely going to help others (like me) whose particular reason for choosing the course was to learn how to unit test the underpinnings of a project and using the tests to help build a robust data store. If it did that with CloudKit, it would deserve 5 stars without hesitation.

I really like the teaching style of the instructor. I really like VM, less complicated than MVVM. The only thing I didn't like about this course was the inconsistency of the Resource files. For instance, in lecture 9, the Resource files you get don't match the project the instructor used, not even the name of the project; it has different folders, extra files, etc.

This is a good match for what I am needing at this time.

Very good class, but it would be helpful to have the node javascript files so we can set up our own Glitch site (or other site) when following along.

Instructor is clear and concise, provides justification for code used and alternatives where it makes sense.

Great course! I just wished that the issues of using Core Data from background processes were also addressed, adding calls to background services to the BudgetApp for example. It would have been great if CloudKit was also addressed for syncing between devices.

Very nice but I prefer unit testing instead of ui testing. Is there a way to write unit tests for a SwiftUI view function? Why you prefer ui testing.