Видео

I mean there is so many points of view

I develop iOS for Cisco.

If you are refactoring messy code you are almost guaranteed to break something.

That’s awesome! Check out this video course I made about ribs too alexbush.podia.com/ribs-architecture-on-ios It’s free but unfortunately unfinished. Hope it helps even more.

we can but that would be breaking single responsibility principle and utilizing an anti-pattern - singleton. Every "module" of your app, in our case viewmodel/viewcontroller combination, is responsible for one part of the app, i.e. screen. App delegate is the place we forced to use to receive incoming deeplink requests therefor it is natural to extend it to also route to other deeplinks/apps thus being consistent with its single responsibility. It can also keep track of context and relevant data for outgoing Paytm request in order to properly process future incoming request from it back into our app. If we call open url from another viewmodel/viewcontroller module in our app we lose track of that. It's a lot of boilerplate, unfortunately, but this approach likely will illuminate a whole set of bugs, issues, and inconsistencies you might have if you open url directly. There is an alternative approach, that I haven't thought of on our call, with having some sort of a manager/handler be a dependency of module that wants to communicate with Paytm. Potentially we can have AppDelegate broadcast any incoming deeplinks and data passed with them as a stream that the handler/manager subscribes to. Then when a specific module wants to open a deeplink and wait for a response from it it can just call openUrl but than sit and wait for the handler to "get a response"/i.e. to get a broadcast message from AppDelegate deeplinks stream. All of this is due to the nature of how UIKit was built and app delegate being the sole receiver of incoming deeplinks. We want to preserve single responsibility principle throughout our architecture as much as possible to make it more manageable, testable, and reusable.

@@InsideiOSDev singleton being an anti-pattern is highly arguable

it does. this is a great use case for it! your relationship of objects is basically something like this in that case: UI/view/viewcontroller -> viewmodel -> builder object

you can even have multiple VMs use the same builder as a source of truth if needed. The builder essentially plays a role of collecting data over time, validating the input, assembling the model, being the source of truth.

That’s one option. Or you can pass them as params to the make method. Typically the rule of thumb is to pass other dependency objects with behavior via the constructor/initializer and data dependencies via the method params. The idea is that things that change less and are less dynamic will be set in the initializer and more dynamic things like user input that happened during runtime will be passed via the method params.

With pain bro

here is more ruclips.net/video/fMqkf1bb23k/видео.html

never heard of it. are there are links to check out to read about it?

Can you explain why you dislike it and how is RIBs not superior to every other mobile architecture out there?

@@InsideiOSDev I never heard about RIB before this video and I do not dislike RIB. I dislike looking at architecture as just applying some "one size fits all" pattern. All projects are different and no single architecture will be the best for all of them. Also thinking that architecture is something you can describe with an acronym just seem very naive to me, I honestly do not know any other developers than mobile developers who thinks of architecture as something you can simply solve by applying a pattern. I did like the video though.

here it is ruclips.net/video/PT7Zsbl5G7U/видео.html

yea, it's a tough one for mobile folks. I recommend looking into www.thoughtworks.com/en-us/insights/blog/bff-soundcloud samnewman.io/patterns/architectural/bff/ medium.com/tech-tajawal/backend-for-frontend-using-graphql-under-microservices-5b63bbfcd7d9 and martinfowler.com/articles/micro-frontends.html It will help you build better mobile apps as you'll have an appreciation of what's going in the backend and will just in general make you a more well rounded engineer.

@@InsideiOSDev thanks very much

yep! this extension is just a "nicety" for readability as you can chain things together with it such as: if someString.orEmpty().isEmpty where if you do coalescing operator you'd have to reserve to: if (someString ?? "").isEmpty neither is better or worse, just your own preference of readability. The idea for this extension method comes from Kotlin kotlinlang.org/api/latest/jvm/stdlib/kotlin.text/is-null-or-empty.html

@@InsideiOSDev Hi Alex. Please pardon the delay getting back to you. Things have been busy, and good, here. The conventional Swift expression of isNilOrEmpty is someString?.isEmpty ?? truecertainly readability in some cases, it would help educate beginning Swift developers on Swift core language features as well as showing the value of extensions. But starting with a C-style if/else (Swift certainly can use if/else, but in this scenario it's an odd use), the beginning developer misses out on the opportunity to learn a core language feature and comes out with an idea that may lead to some odd code just because they don't understand part of the language, which is unfortunate. I hope this helps as you formulate your content and wish you the best.

there are illustrations and visuals about this in my course iosinterviewguide.com/system-design-interview I'm also starting to make more video episode where I screen share and show code or diagrams. Will be revisiting the topic of system design. Stay tuned.

true! this extension is just a "nicety" for readability as you can chain things together with it such as: if someString.orEmpty().isEmpty where if you do coalescing operator you'd have to reserve to: if (someString ?? "").isEmpty neither is better or worse, just your own preference of readability. The idea for this extension method comes from Kotlin kotlinlang.org/api/latest/jvm/stdlib/kotlin.text/is-null-or-empty.html

Glad it was helpful!

yea. That's the goal. it takes a lot of time to produce the videos but ultimately I want to switch to that format instead of just the audio.

here's another video like this! ruclips.net/video/OgUtcCIqLSM/видео.html