This is EXACTLY what I've been looking for. There are so many tutorials on how to build app x or y, but none go into architecture like this (most of them don't even discuss architecture at all). You're learning how to build that specific app only in those tutorials. THIS teaches the thinking in how to design/ build any app. Really excited to finish this series. Thanks!
I wish i had known about this channel and the essentialdeveloper site earlier, like 3-4 years back. Would have been a different story. Anyhow, better late than never and thanks for such quality stuff. It actually changes the way you approach a problem and think, visualize it before even firing up Xcode to write a single line of code.
This is quality. I love listening to programming advice while working out but so many iOS videos are just “make x app.” I’m beyond that, I can make any of those apps independently, but not quite a full senior yet. This is exactly the gap I need to fill, thanks for the upload. If I’d watched this 3 years ago I could have petitioned to rewrite our app’s analytics layer because hooo boy any time a new view controller was added I had to modify 4 other files just to do analytics without compile errors.
I wish I'd discovered your content years ago. I've studied all kinds of books, tutorials, videos from many authors, and learned a lot from them. However, I feel many of them fall short in using overly simplified, trivialized examples that simply don't translate or scale to the kinds of _real-world_ apps that we get paid to develop. Conversely, any time I watch some of your content, I feel like I can turn around and immediately start improving things in my _actual_ projects. Thank you.
This is a great video especially the manner in which it is delivered. Going through each of the possible approaches to the software design, highlighting where code breaks the SOLID principles and henceforth put forward the possible alternate approaches with merits & demerits. Superb Guys! Please keep up this approach of delivering content. A big 👍
Very interesting topic. At 23:40, can you please explain, how do you implement the name and metadata in the LoginEventEnum or MessageListEventStruct? Thank you
I just saw this video. Great approach and a great topic. Really easy to follow. I loved that you started with an non-optimal architecture and evolved it. I already feel smarter. Thank you!
Hi! I'm currently building an analytics architecture based on this video, but I'm also struggling with those predefined parameters and events names Firebase Analytics suggests me to use. What are the best recommendations to use them without letting my independent modules know anything about Firebase? Hope you can help me with that. Thanks!
Hi Javier, you can use adapters/wrappers to handle communication with the frameworks. So, you decouple your app from the 3rd-party code. Watch parts 2 and 3 to learn more. ✅
Good video! Just reminds me what I experienced with one of my projects. I used enum for types of pollutants. But later changed to use POP to handle the increasing amount of types of pollutants.
Outstanding video! Super useful, thanks very much! Help needed: The only part that was difficult to understand for me was the removal of the AnalyticsManager class at the end. Wouldn't moving the log function into the protocol force you to have many redundant implementations of log in your view controller classes? Can someone shed some light on that part for me?
Hi @@EssentialDeveloper, same here. Still don't get the final implementation. From the first approach, the `class` engines (conforming to `AnalyticsEngine`) all have the `log()` method triggered by the dependency injection `AnalyticsManager`'s `log()` method that would eventually be invoked from the view controllers. How is the last approach different? How would the arrows from view controllers pointing to `AnalyticsEngine` protocol be implemented? Should the view controllers have a property `AnalyticsEngine` so each would be able to call the `log()` method and send each viewcontroller-specific event as param? Would really appreciate your response. Thank you! :)
Hi Karla, that's right, view controllers can have a property `` and call `log()` passing ViewController-specific events. The implementations of the `` are unchanged (e.g., CloudKit and Firebase implementations). The role of the `AnalyticsManager` class presented in the first solution was basically to extract the `AnalyticEventEnum` "name" and "metadata" properties to send to the `` protocol abstraction. The difference displayed in the last solution is: by breaking down the "Analytics Events" into separate types and extracting/grouping the Analytics abstractions (protocols) in the same "module/layer," we don't need an `AnalyticsManager` anymore. From the architecture point of view, such a manager class is not required and add no benefits to the design. As you said, we can inject implementations of the `` protocol in the ViewControllers and call the `log` method directly in the protocol reference instead of injecting and calling the method on an `AnalyticsManager`. Not a significant architectural change, but we removed an unnecessary class while achieving the same goals! Does it make sense now? Thanks for the question! ⛩
@@EssentialDeveloper Hi! Thank you for the clarification and the detailed explanation. Really appreciate that! I'm currently implementing the last approach so thank you so much!
This is a great explanation, but one doubt since AnalyticsEvent is not having event methods other than name and metadata, I am curious to know how ViewController will call specific event. Could you please share some block of code or any thoughts on this?
Hi! The VC doesn't need to create the specific events directly. The VC could only delegate messages like `purchaseButtonClicked()` - and another component - like an analytics event handler - receives the message and creates the specific events ✅
I'm going through alot of your videos including this specific series. This is all *really* quality stuff - thanks! I would say this content is pretty high-value to me - so I'd be happy to support it. Just FYI - If you set up a Patreon - I would contribute to it.
Anyone can help me, what does 11:50 - 12:00 means, I think the `AnalyticsManager` just get the `name` and `metadata` from the `AnalyticsEventEnum`, why we can't make it one module with the `AnalyticsEngine`? even everytime we have new event, the `AnalyticsManger` would just call the properties of the `AnalyticsEngine` name and metadata right? or Caio means since it's concrete `AnalyticsEventEnum` in `AnalytcisManager`, so that the module can't be use for other cases other that `AnalyticsEventEnum`? coz it has to be `AnalyticsEventEnum`?
Dangg... I just reach 19:40 and it's amazing... what a game changer between enum and struct, hmm but what's difference if u have an enum and extension of method that return a value? ah maybe it still depends on the case 11:50 previously ya, it will state param type of the enum and return type is not standarized stated in the enum, so other developers could implement it wrong, okay.. hmm since it's struct based, the value of static method will always in form of `AnalyticsEventStruct`, rather than enum which we can't define it well (i mean the struct will always return `AnalyticsEventStruct`, but if enum use the extension just like struct on 19:40, it cant return a exact form like `AnalyticsEventStruct`)
Hmm i have questions, what if i want to log some event to firebase and some event to cloudkit at the same controller? refer to sundell's MessageListViewController class so maybe let CKAnalyticsManager = AnalyticsManager(engine: CloudKitAnalyticsEngine()) let FBAnalyticsManager = AnalyticsManager(engine: FirebaseAnalyticsEngine()) let messageController = MessageListViewController(message: messageCollection, analytics: CKAnalyticsManager) hmm it wont work, since we will only have 1 MessageListViewController inside `AnalyticsManager` only have 1 engine.. hmm.. maybe need to modify the controller so that MessageListViewController(message: messageCollection, CKAnalytics: CKAnalyticsManager, FBAnalytics: FBAnalyticsManager) hmm but its feel very attached with CKAnalytics param, maybe we need to modify the `AnalyticsManager` coz it supposed to `Manage` right, maybe like... class AnalyticsManager { private let cloutKitEngine: AnalyticsEngine private let firebaseEngine: AnalyticsEngine init(cloutKitEngine: AnalyticsEngine, firebaseEngine: AnalyticsEngine) { self.cloutKitEngine = cloutKitEngine self.firebaseEngine = firebaseEngine } func logCloudKit(_ event: AnalyticsEvent) { cloutKitEngine.sendAnalyticsEvent(named: event.name, metadata: event.metadata) } func logFirebase(_ event: AnalyticsEvent) { firebaseEngine.sendAnalyticsEvent(named: event.name, metadata: event.metadata) } } hmm.. the param seems redundant type of `AnalyticsEngine`, i don't know.. any ideas?
Hi! With the enum approach shown, adding a new case is a breaking change and requires the recompilation of all dependent modules. But with the struct approach, new events can be added without recompiling other modules ✅ Regarding the second question about multiple engines, you can use the Composite design pattern. Keep watching this series and you'll see it in practice!
Hi Chintan, thank you! You'll find the answer in parts two and three: Part 2: th-cam.com/video/C2GyNTN4j4o/w-d-xo.html Part 3: th-cam.com/video/GzFD7R_CI04/w-d-xo.html
How would you write the one-liner for the ViewController in the structs approach? I tried to implement it following the diagram and I can't figure out how to do it.
Hello! Our content is not intended for total beginners - it's for iOS developers with professional experience. If you're familiar with the basics, you can follow this playlist: th-cam.com/play/PLyjgjmI1UzlSUlaQD0RvLwwW-LSlJn-F6.html
Hello and thank you for the lesson, I am in 11 minutes and don't understand why we have to change AnalytisManager when we add some new event to the Enum? Where we have to change code? class AnalyticsManager { private let engine: AnalyticsEngine init(engine: AnalyticsEngine) { self.engine = engine } func log(_ event: AnalyticsEvent) { engine.sendAnalyticsEvent(named: event.name, metadata: event.metadata) } } And second question: if i need to use two engine at the same time should I keep AnalyticManager and have array of AnalyticEngine in
Hello Gulya, 1) You don't need to change the AnalyticsManager. Just the AnalyticsEvent enum extension. 2) You can find the solution for this scenario in pt.3 ✅
Do you have any premium tutorials on udemy or your website? You should create more tutorials! I will definitely buy them. I'm waiting for more from you. Cheers :)
Any course for beginners? Or any recommendation where to start? I looked on your website, and it is a little confusing where to start...at least for me. I'm open to buy an of your courses as long it starts from the beginning for beginners.
Hi! It depends on your level. If you're a beginner but familiar with the basics of programming already, we recommend to you our course "Swift Feed App Case Study" - academy.essentialdeveloper.com . We're covering advanced topics but with an approachable methodology. It's been popular among beginners as well. We believe you'll greatly benefit from it as others have so far. ✅⛩
@@EssentialDeveloper Thank you for the response and sorry for the late reply. I don't have any ios or any unit testing experiences, but I do know the swift language and OOP concepts. Is the course you provided still valid for my case?
This is EXACTLY what I've been looking for. There are so many tutorials on how to build app x or y, but none go into architecture like this (most of them don't even discuss architecture at all). You're learning how to build that specific app only in those tutorials. THIS teaches the thinking in how to design/ build any app. Really excited to finish this series. Thanks!
We're glad to know you're learning from and enjoying the videos! Welcome to our channel and community. 🤝⛩
30 minutes that blew my mind! Great to have tutorials with this sort of level of thinking!
Hey Ramon, thanks for the feedback and welcome to the channel! ✅
I wish i had known about this channel and the essentialdeveloper site earlier, like 3-4 years back. Would have been a different story. Anyhow, better late than never and thanks for such quality stuff. It actually changes the way you approach a problem and think, visualize it before even firing up Xcode to write a single line of code.
Welcome to our channel! 🙂
This is quality. I love listening to programming advice while working out but so many iOS videos are just “make x app.” I’m beyond that, I can make any of those apps independently, but not quite a full senior yet. This is exactly the gap I need to fill, thanks for the upload.
If I’d watched this 3 years ago I could have petitioned to rewrite our app’s analytics layer because hooo boy any time a new view controller was added I had to modify 4 other files just to do analytics without compile errors.
I wish I'd discovered your content years ago. I've studied all kinds of books, tutorials, videos from many authors, and learned a lot from them. However, I feel many of them fall short in using overly simplified, trivialized examples that simply don't translate or scale to the kinds of _real-world_ apps that we get paid to develop. Conversely, any time I watch some of your content, I feel like I can turn around and immediately start improving things in my _actual_ projects. Thank you.
Happy to help!
I really like how you progressively improve the architecture and I learn more that way! Awesome tutorial
This is a great video especially the manner in which it is delivered. Going through each of the possible approaches to the software design, highlighting where code breaks the SOLID principles and henceforth put forward the possible alternate approaches with merits & demerits. Superb Guys! Please keep up this approach of delivering content. A big 👍
Thank you!
This is probably one of the best tutorial on iOS Architecture. Thumbs up for the good work.
Thank you! ⛩
As a professional iOS dev, I can say this is a really, really excellent video
Caio, what a great course! I'm lovin it!
BTW are you brazilian? Your accent is looks like from brazil haha
Thank you, Wender! Yes, I'm Brazilian 🙂🇧🇷
The best tutorial on iOS architecture I've seen till now. Thumbs up. 👍
Glad it was helpful!
Very interesting topic. At 23:40, can you please explain, how do you implement the name and metadata in the LoginEventEnum or MessageListEventStruct?
Thank you
Thanks! They can be associated values in enums and properties in structs, for example.
Trust me! People need to learn these things before learning to program! You created a new way of thinking when we design software.
Thank you so much!
Thank you! Glad it was helpful ✅
I just saw this video. Great approach and a great topic. Really easy to follow. I loved that you started with an non-optimal architecture and evolved it. I already feel smarter. Thank you!
Glad you enjoyed it!
Really good video! Thanks for making this comparison between all the approaches.
Thanks!
I watch again, and it's still beautiful.
Just try to write a sample code in this repo. hope helpful.
github.com/rollr76518/AnalyticsEnginePractice
You are a legend man!
Hi! I'm currently building an analytics architecture based on this video, but I'm also struggling with those predefined parameters and events names Firebase Analytics suggests me to use. What are the best recommendations to use them without letting my independent modules know anything about Firebase? Hope you can help me with that. Thanks!
Hi Javier, you can use adapters/wrappers to handle communication with the frameworks. So, you decouple your app from the 3rd-party code. Watch parts 2 and 3 to learn more. ✅
I can't press the like button more than 1 time! But you think I pressed it 100 times :)))))
Good video! Just reminds me what I experienced with one of my projects. I used enum for types of pollutants. But later changed to use POP to handle the increasing amount of types of pollutants.
good content for a new beginner
Outstanding video! Super useful, thanks very much!
Help needed:
The only part that was difficult to understand for me was the removal of the AnalyticsManager class at the end. Wouldn't moving the log function into the protocol force you to have many redundant implementations of log in your view controller classes? Can someone shed some light on that part for me?
Or would those implementations go in the Analytics Engines at the top?
Thanks! That's it. The implementations are in the top layer. The view controllers would just send `log` messages through the protocol abstraction. ✅⛩
Hi @@EssentialDeveloper, same here. Still don't get the final implementation.
From the first approach, the `class` engines (conforming to `AnalyticsEngine`) all have the `log()` method triggered by the dependency injection `AnalyticsManager`'s `log()` method that would eventually be invoked from the view controllers.
How is the last approach different?
How would the arrows from view controllers pointing to `AnalyticsEngine` protocol be implemented? Should the view controllers have a property `AnalyticsEngine` so each would be able to call the `log()` method and send each viewcontroller-specific event as param?
Would really appreciate your response. Thank you! :)
Hi Karla, that's right, view controllers can have a property `` and call `log()` passing ViewController-specific events. The implementations of the `` are unchanged (e.g., CloudKit and Firebase implementations).
The role of the `AnalyticsManager` class presented in the first solution was basically to extract the `AnalyticEventEnum` "name" and "metadata" properties to send to the `` protocol abstraction.
The difference displayed in the last solution is: by breaking down the "Analytics Events" into separate types and extracting/grouping the Analytics abstractions (protocols) in the same "module/layer," we don't need an `AnalyticsManager` anymore.
From the architecture point of view, such a manager class is not required and add no benefits to the design. As you said, we can inject implementations of the `` protocol in the ViewControllers and call the `log` method directly in the protocol reference instead of injecting and calling the method on an `AnalyticsManager`.
Not a significant architectural change, but we removed an unnecessary class while achieving the same goals! Does it make sense now?
Thanks for the question! ⛩
@@EssentialDeveloper
Hi! Thank you for the clarification and the detailed explanation. Really appreciate that!
I'm currently implementing the last approach so thank you so much!
This is a great explanation, but one doubt since AnalyticsEvent is not having event methods other than name and metadata, I am curious to know how ViewController will call specific event. Could you please share some block of code or any thoughts on this?
Hi! The VC doesn't need to create the specific events directly. The VC could only delegate messages like `purchaseButtonClicked()` - and another component - like an analytics event handler - receives the message and creates the specific events ✅
What tool did you use to draw the class diagrams ?
Hi Medhad Ashraf. We used www.draw.io.
Amazing Video... Can you please recommend any good book for design patterns
Hi Rohit, thank you! You can find our book suggestions here: www.essentialdeveloper.com/book-suggestions
This is excellent! Thank you!
I'm going through alot of your videos including this specific series. This is all *really* quality stuff - thanks!
I would say this content is pretty high-value to me - so I'd be happy to support it.
Just FYI - If you set up a Patreon - I would contribute to it.
Hi Jeff, thanks for the support! We really appreciate it! ✅⛩
Awesome explanation. What tool do you use to draw the diagrams?
Thanks, Amit! We used draw.io
Anyone can help me, what does 11:50 - 12:00 means, I think the `AnalyticsManager` just get the `name` and `metadata` from the `AnalyticsEventEnum`, why we can't make it one module with the `AnalyticsEngine`?
even everytime we have new event, the `AnalyticsManger` would just call the properties of the `AnalyticsEngine` name and metadata right?
or Caio means since it's concrete `AnalyticsEventEnum` in `AnalytcisManager`, so that the module can't be use for other cases other that `AnalyticsEventEnum`? coz it has to be `AnalyticsEventEnum`?
Dangg... I just reach 19:40 and it's amazing... what a game changer between enum and struct,
hmm but what's difference if u have an enum and extension of method that return a value? ah maybe it still depends on the case 11:50 previously ya, it will state param type of the enum and return type is not standarized stated in the enum, so other developers could implement it wrong, okay.. hmm
since it's struct based, the value of static method will always in form of `AnalyticsEventStruct`, rather than enum which we can't define it well (i mean the struct will always return `AnalyticsEventStruct`, but if enum use the extension just like struct on 19:40, it cant return a exact form like `AnalyticsEventStruct`)
Hmm i have questions, what if i want to log some event to firebase and some event to cloudkit at the same controller? refer to sundell's MessageListViewController class so maybe
let CKAnalyticsManager = AnalyticsManager(engine: CloudKitAnalyticsEngine())
let FBAnalyticsManager = AnalyticsManager(engine: FirebaseAnalyticsEngine())
let messageController = MessageListViewController(message: messageCollection, analytics: CKAnalyticsManager)
hmm it wont work, since we will only have 1 MessageListViewController inside `AnalyticsManager` only have 1 engine.. hmm.. maybe need to modify the controller so that
MessageListViewController(message: messageCollection, CKAnalytics: CKAnalyticsManager, FBAnalytics: FBAnalyticsManager)
hmm but its feel very attached with CKAnalytics param, maybe we need to modify the `AnalyticsManager` coz it supposed to `Manage` right, maybe like...
class AnalyticsManager {
private let cloutKitEngine: AnalyticsEngine
private let firebaseEngine: AnalyticsEngine
init(cloutKitEngine: AnalyticsEngine, firebaseEngine: AnalyticsEngine) {
self.cloutKitEngine = cloutKitEngine
self.firebaseEngine = firebaseEngine
}
func logCloudKit(_ event: AnalyticsEvent) {
cloutKitEngine.sendAnalyticsEvent(named: event.name, metadata: event.metadata)
}
func logFirebase(_ event: AnalyticsEvent) {
firebaseEngine.sendAnalyticsEvent(named: event.name, metadata: event.metadata)
}
}
hmm.. the param seems redundant type of `AnalyticsEngine`, i don't know.. any ideas?
Hi! With the enum approach shown, adding a new case is a breaking change and requires the recompilation of all dependent modules. But with the struct approach, new events can be added without recompiling other modules ✅
Regarding the second question about multiple engines, you can use the Composite design pattern. Keep watching this series and you'll see it in practice!
@@EssentialDeveloper Thankyouu guyss, love it
Fantastic Work!
One small doubt. If we remove AnalyticsManager then who will provide the body of log() method and hold actual Object of Engine?
Hi Chintan, thank you! You'll find the answer in parts two and three:
Part 2: th-cam.com/video/C2GyNTN4j4o/w-d-xo.html
Part 3: th-cam.com/video/GzFD7R_CI04/w-d-xo.html
Thanks for the video Caio. Could you outline your approach if you wanted to share events between view controllers/modules?
Hi Ross! We believe you will find the answers you're looking for in the next parts of this series, where we go deeper into this topic. Let us know! ✅
@@EssentialDeveloper Thanks, will do!
Great stuff, thank you so much for sharing this precious knowledge!
Glad it was helpful!
How would you write the one-liner for the ViewController in the structs approach? I tried to implement it following the diagram and I can't figure out how to do it.
Hi Raluca, watch pt.2 and pt.3 to learn more!
Great video ! what tool are you using in this video for diagraming ?
Thanks! We're using draw.io
I think it is www.draw.io/
Architecture is important!!!
Indeed! ✅
Hello!!! Please tell a newbie which playlist to start with?
Hello! Our content is not intended for total beginners - it's for iOS developers with professional experience. If you're familiar with the basics, you can follow this playlist: th-cam.com/play/PLyjgjmI1UzlSUlaQD0RvLwwW-LSlJn-F6.html
Best explanation
Really, really ,really nice - thanks a lot for this video.
Hello and thank you for the lesson, I am in 11 minutes and don't understand why we have to change AnalytisManager when we add some new event to the Enum? Where we have to change code?
class AnalyticsManager {
private let engine: AnalyticsEngine
init(engine: AnalyticsEngine) {
self.engine = engine
}
func log(_ event: AnalyticsEvent) {
engine.sendAnalyticsEvent(named: event.name, metadata: event.metadata)
}
}
And second question: if i need to use two engine at the same time should I keep AnalyticManager and have array of AnalyticEngine in
Hello Gulya,
1) You don't need to change the AnalyticsManager. Just the AnalyticsEvent enum extension.
2) You can find the solution for this scenario in pt.3 ✅
Do you have any premium tutorials on udemy or your website? You should create more tutorials! I will definitely buy them. I'm waiting for more from you. Cheers :)
essentialDeveloper.com
Which app you used to draw diagrams?
Hey, we're using draw.io ✅
What app used to draw it?
Hi! We used draw.io
Any course for beginners? Or any recommendation where to start? I looked on your website, and it is a little confusing where to start...at least for me. I'm open to buy an of your courses as long it starts from the beginning for beginners.
Hi! It depends on your level. If you're a beginner but familiar with the basics of programming already, we recommend to you our course "Swift Feed App Case Study" - academy.essentialdeveloper.com . We're covering advanced topics but with an approachable methodology. It's been popular among beginners as well. We believe you'll greatly benefit from it as others have so far. ✅⛩
@@EssentialDeveloper Thank you for the response and sorry for the late reply. I don't have any ios or any unit testing experiences, but I do know the swift language and OOP concepts. Is the course you provided still valid for my case?
Yes, absolutely! Swift and OOP is more than enough. See you there. 🤝⛩
@@EssentialDeveloper Thanks, just bought your course.
Great video, thanks for your time :)
Oh my God. You explained it in a much much better way. Thank you sooo much Captain 🫡
actually namespacing is not a problem. Nobody restricts you to keep your modules modular with their own namespaces. At least in Swift.
Exactly, it's a problem when they're in the same module! That's another benefit of separating your code into modules in Swift. ✅
Great job!
what's the name the software?
draw.io
This video will help in 2023?
Absolutely!
凄い
Brazuka aqui! rsrs
🇧🇷
cool
"Great." :D