Thanks for the awesome and complete design video. @pallav, Can you make a video similar to this detail level but with full MVVM components, clean architecture and protocol-oriented design. That shows the interaction between models, Views, Viewmodels, coordinator, NetworkManager, and Notification manager, etc.. (for example Shopping cart). This will help a lot for developers to repair for interviews as well as their daily coding.
Nice explanation Pallav.I like your videos. Just a thought, for bigger projects the AnalyticsEvent enum will keep on expanding which will be harder to maintain in future.Also, I think it violates the open/close SOLID principal. Can event details resides with different entities/views itself so that it will scalable always and easy to remove as it won't be coupled.
Thank for this nice video, have one question where we have to store API key (such like clever tap API key), generally we are using hard coded. Means putting in P-List. My suggestion : 1. we can ask in API but before that API we can't track events 2. when we have to update API key means refresh API key ... should we have to or not? Thank You
Awesome Content...Please do upload more videos like this-- Suggestion Loading Post from Api if the internet is available else load cached posts like instagram
I was interviewed on the same topic. I have couple questions I could answer well. can you please check any thoughts around 1.How to do you restrict the parameters values. i.e, if it is [string:Any] then we can pass any object that can be very big like Data, Image Data etc, So how do we restrict it with primitive data types 2.What is the serialisation type you use , since JSON having performance issues to scale Can you please help with this
Normally we make models as structs. However, models are pass to different viewModels. Lets take example of user model. This model properties updates on different viewModels. So is it ok to use struct for userModel because we are making models everytime we change value
Very Informative. But I have one doubt , when to use AnalyticsEvent.parameters and "params" in func track(event: AnalyticsEvent, params: [String : Any]?)
Hello Sir, I have almost 1.5 years of experience in iOS development. Just wanted to know if I try go for an interview now, what are the major topics my interviewer will expect me to know.
First and foremost, thank you for these videos, they are of great help!. Just have one question I don't understand the part of having it a singleton, if you are calling it from viewModels and you want to test those, would you use dependency injection sending the singleton as the dependency, or just calling the shared instance from the viewModels. I just don't get why it wouldn't be a problem when the singleton is called during tests. Is it because it doesn't have any services yet, since they are only inserted in the appDelegate? so it doesn't really matter?
Enum for event is very bad idea. When your app has a ton different event to send. Xcode will even have difficulty to render the file that contents thousand of events
This is one of the best System Design Video for Mobile Application I have seen. Everything covered and nicely explained. Keep up the good work!!!
Completely agree!
Thanks for the awesome and complete design video. @pallav, Can you make a video similar to this detail level but with full MVVM components, clean architecture and protocol-oriented design. That shows the interaction between models, Views, Viewmodels, coordinator, NetworkManager, and Notification manager, etc.. (for example Shopping cart). This will help a lot for developers to repair for interviews as well as their daily coding.
Thanks for the suggestion, we’ll look for it 🙂
I am studying for system design interviews and this video came at the correct time :) Thanks. Great video
Nice explanation Pallav.I like your videos. Just a thought, for bigger projects the AnalyticsEvent enum will keep on expanding which will be harder to maintain in future.Also, I think it violates the open/close SOLID principal. Can event details resides with different entities/views itself so that it will scalable always and easy to remove as it won't be coupled.
If you keep the events in the view itself, do you think it will a reusable code?
Nice One, but we can also use builder design pattern here to track multiple parameters of user's choice.
Thank for this nice video, have one question
where we have to store API key (such like clever tap API key), generally we are using hard coded. Means putting in P-List.
My suggestion :
1. we can ask in API but before that API we can't track events
2. when we have to update API key means refresh API key ... should we have to or not?
Thank You
Very Good Pallav, Great Job, Appreciated !!! It would be excellent if we can cover Instagram System Design for Home screen
Nice work! Great explanation..
Can you tell pointers to Fernando Martin?
Awesome Content...Please do upload more videos like this-- Suggestion Loading Post from Api if the internet is available else load cached posts like instagram
I was interviewed on the same topic. I have couple questions I could answer well. can you please check any thoughts around
1.How to do you restrict the parameters values. i.e, if it is [string:Any] then we can pass any object that can be very big like Data, Image Data etc, So how do we restrict it with primitive data types
2.What is the serialisation type you use , since JSON having performance issues to scale
Can you please help with this
pallav appreaciate your video on this, Do we need initailize method part of abstraction?
Normally we make models as structs. However, models are pass to different viewModels. Lets take example of user model. This model properties updates on different viewModels. So is it ok to use struct for userModel because we are making models everytime we change value
Very Informative. But I have one doubt , when to use AnalyticsEvent.parameters and "params" in func track(event: AnalyticsEvent, params: [String : Any]?)
Please make a video on higher order functions
Very helpful, thanks!
Hello Sir, I have almost 1.5 years of experience in iOS development. Just wanted to know if I try go for an interview now, what are the major topics my interviewer will expect me to know.
First and foremost, thank you for these videos, they are of great help!. Just have one question
I don't understand the part of having it a singleton, if you are calling it from viewModels and you want to test those, would you use dependency injection sending the singleton as the dependency, or just calling the shared instance from the viewModels. I just don't get why it wouldn't be a problem when the singleton is called during tests. Is it because it doesn't have any services yet, since they are only inserted in the appDelegate? so it doesn't really matter?
I like a a lot your video. May Allah protect you and give you lots of success.👍.
Enum for event is very bad idea. When your app has a ton different event to send. Xcode will even have difficulty to render the file that contents thousand of events
Bro you are awesome.
Waiting from two weeks for the New Video
Thanks for the Great Video
Awesome
where is new video on this week?