No video :(

Validating Form in SwiftUI Using MV State Pattern

Подписаться 23 тыс.

Просмотров 3,1 тыс.

50% 1

In this video, Mohammad Azam will demonstrate how to validate a form in SwiftUI using MV State Pattern.
Related Videos:
1. Stop Using MVVM for SwiftUI
• STOP Using MVVM with S...
2. Client/Server Apps in SwiftUI Using MV State Pattern
• Client Server SwiftUI ...
#iosdev #swiftui
Support my work and get my courses:
azamsharp.com/...
Gist: gist.github.co... Check out my courses at
azamsharp.school/

Опубликовано:

4 сен 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 13

@hamslammula6182 2 года назад

Hi Mohammad, I appreciate your dedication to this paradigm. However, what seems unconvincing is the fact that your examples of the MV pattern consist of quite simple tasks that would mainly be applicable in simple apps. You would convince many more people if you could show an app which communicates with a backend for things like authentication and CRUD actions while using the MV pattern.

@azamsharp 2 года назад

I have given many different ways of validation. If your form is big then you can move it to a different struct. Also, check out the video description, where I have added few links for MV pattern with networking etc. I found that with MVVM even simple apps were getting complicated. With MV pattern (Apple pattern), it becomes easy. The only way is to try it out and see if it fits your needs. There is no way for me to create large apps, because what will be large for me 200K lines of code might be small for others.

@azamsharp 2 года назад

Here is upcoming seminar from RayWenderlich website: www.raywenderlich.com/35112528-is-mvvm-right-for-swiftui-live-seminar-coming-soon

@Notkdenben 2 года назад

@@azamsharp I actually really like the simplicity of this architecture as a beginner. You said this was an “Apple pattern”. Could you link me to some example or documentation where I could see Apple implementing this pattern? Of course I’ll be checking out your content as well. Thanks in advance.

@azamsharp 2 года назад

@@Notkdenben Most of the samples Apple has published uses the same pattern. Now, I am not saying that we should blindly follow Apple for architectural advice but after making hundreds of apps I came to realize that whenever I used MVVM I was fighting SwiftUI. This was because SwiftUI already had MVVM built-in so, in most cases we don't need any extra layer for binding. You can check out the following: developer.apple.com/documentation/swiftui/food_truck_building_a_swiftui_multiplatform_app developer.apple.com/documentation/swiftui/fruta_building_a_feature-rich_app_with_swiftui

@Notkdenben 2 года назад

@@azamsharp thanks for the reply! I will check those out!

@L1ST3Reda 11 месяцев назад

Thank you for this :) What about select lists that contains objects (i am coming from react native, maybe i am wrong here). Does this way of checking apply to more complex fields as well?

@Ivoshevo 2 года назад

To keep the view clean, where do we keep the business logic of the app. In the V by adding extensions or in the M. On the other hand let's say some data needs to be referenced will it be appropriate to add the logic on the M or in a V I think that is a good reason for VM when we need class references. As for me the MVVM is just to keep code clean the only problem is needing a VM for each V. I wish one VM could be used for all Vs. Just my own small ideas. I am still a junior iOS developer not even having a job but still learning. Thank you for the video

@azamsharp 2 года назад

Can you give me an example of a particular scenario?