Hi, there. As mentioned previously here is the first part to an architecture we feel is very well suited to mobile apps: ukposts.info/have/v-deo/e11opYhnmWiWkWw.htmlsi=lHkm8Fi1KpZyrjRH

A question doesn’t relate to the topic, but I saw you inject service instance in Login View, so what is responsibility of LoginViewModel? It just keep state of Login View, right? 33:08

Thanks for sharing. Just like Redux, there are major issues with large complex projects where you need multiple pipelines to deal with data and sources of data. Ie, Transports like BLE, WLAN, Sockets, HTTP etc... Where do services, use cases and repositories fit into this model? Events are great, but I've seen projects where there are hundreds of events as side effects with no thought as to the domain of the event... We have a better way to do architecture. I will need to post a video about it.

I struggle to understand most Swift Heroes videos. Mostly watching the videos and not understanding words.

In the future editions, please bring speakers that can speak a better english.

Thank you for putting all the efforts to make this available on UKposts.

Great video Zamzam! Gives a really good picture to help chose/not to chose SwiftUI for upcoming production projects.

thanks!

Sounds like a very interesting topic, but had to stop watching after 10s because of the excessive editing. Very hard to watch when there are all the natural pauses removed from the video.

I think this is a better approach for creating useful components which are reusable too

Grear video, lots of value add

Too good

😮

This is a very interesting and helpful talk. Thank you for sharing.

*promosm*

This is an amazing talk. Thanks for sharing this with us.

30 minutes to say SwiftUI is great? Everyone knows it after 5 years :D

What did I just see? Is this some sort of a joke?

Audio is really bad

This architecture was relevant in the React community a while ago (Redux), but the trend seems to be moving towards simpler architectures like react-query, hooks, etc. I am not sure if the iOS engineering community will follow the same path, as the problem is universal across FE development (state management is complex)

i dont see any benefits of extract to functions, except when where is a switch. Extracted Text with modifiers doesnt make sense because its the same view with the same specs but with more lines of code.

Thanks, from Vietnam 😊

Great presentation, as an iOS developer, I wish to work under your leadership

I was surprised by the dissatisfaction with the timer and the frequent updating of the view. The code does what suppose to do and actually doing that pretty well with hi performance. If you update elapsed time value every second in a loop and display this value in a text view then obviously the Time View with all subviews will refresh every second. Just because it is a struct and its state was changed. At first glance it could sounds scary. However SwiftUI is pretty smart, it checks state of each subview and redraw only view where it's own state was changed. Of course there are a number of criteria that must be met such as avoiding AnyView etc. So if you understand how SwiftUI view lifecycle works it stops being something scary.

Nice "input" 👏

👏👏👍

Why do we have so many speakers nowadays. I'm not talking about her because she knows what she doing but there's so many scammers trying to sell a copy paste course

I love that name....ZAMZAM

very good talk, Thank You Peter!

Бурунов докладывает 🔥

I agree with most of the concepts you’ve talked about, and I’m definitely grateful to you for bringing value to the community. However, correct me if I’m wrong but it seems like you guys are using an anti-pattern called Service Locator, which basically is global shared state to implicitly inject dependencies. This talk has 2 years, so maybe this was already addressed, but I would feel very uncomfortable in using a Service Locator in all of my services. Service Locator has many problems, one of the biggest in my opinion is the lack of errors at compilation time. I much prefer using dependency injection through the initializer. I would say that a true level 4 app done correctly doesn’t need this sort of global shared state to achieve its needs. I was also not convinced by your approach to navigation. But I would have to look at concrete cases to be able to see how you approach for example injecting data that is only available at run time. Being able to control navigation from BE is cool though.

Love this talk. This is a classic problem.

Thanks for the report Peter Friese! Very useful tips. I faced the same problems when I refactored my project from UIKit to SwiftUI. I wish this report was available when I did this. The report would save me a lot of time :)

Great video! I'm curious, is there a particular reason for not using a viewModel? Wouldn't this result in tighter coupling of Views, potentially reducing their reusability?

Nice

Excellent content, Bruno. About the end, I'm gonna quote someone whose name I forgot: "The good software architect is a master at deferring big decisions and leaving options open". So while we shouldn't be doing rocket science within a newborn app, we should definitely be careful with how we're designing our small app now as to not make everyone's lives extra hard when we finally need some restructuring. ;)

We use Reactor Kit in our app with 200K daily active users. It's basically TCA philosophy with Per screen state store. And then on each view only updating if it's required slice within the state is mutated.

Super interesting talk!

I used to be a native zealot for the longest time 😅 But I got a taste of Flutter at my last job. Now I'm in the more middle ground mindset where I think each tool/technology has its place and it largely depends on a various set of needs and requirements. In other words, I think Flutter has its uses and neither Flutter won't replace native and vice versa. Having seen how Flutter has matured in the short period of time, I do honestly think SwiftUI has a lot of catching up to do. These slow once in a year release cycles are really hurting native iOS devs.

Someone make this guy a CEO!

Someone make this guy a CEO!!!

thank you!

Great talk and smooth demo, thank you!

Great insight, thanks Alberto

Amazing talk! I am a huge fan of Shai Mishali's works and talks!

great talk, thanks

At 7:53... Sure but the problem with these sorts of architectures is that any one action could change any piece of state. So not only do you have to assert the correct state changes, but you also have to assert that no other bits of state changed. That's n*m assertions (where n is the number of actions, and m the possible states.) In other words, your assertions grow exponentially with every action or piece of state you add. Not good!

Very Basic and structured way. this is the foundation 👍

the video can be on HD? with 480p I can't see the names/code and structure of the project that is shown in this talk please.