Factory Design Pattern in Swift & iOS (2023)

Поделиться
HTML-код
  • Опубликовано: 1 ноя 2024

Комментарии • 19

  • @micahburnside2281
    @micahburnside2281 4 месяца назад +1

    Its better not not have any mistakes so that the person coding along with you doesn’t get told the wrong information while they are learning.

  • @gijoecodes
    @gijoecodes Год назад +2

    Very interesting. First time I’ve heard of it. Normally if I have repetitive code I create an extension of a particular class. This looks so much better. Perhaps I’ll try to incorporate this into my apps. Incidentally, when my simulator stops working. I just quit the app and it gets fixed. For me erasing it means that I would have to log back in.

  • @jsedlacekjr
    @jsedlacekjr Год назад +2

    We use this pattern + coordinators where I work at

    • @iOSAcademy
      @iOSAcademy  Год назад

      Nice

    • @TheSukhreetSingh
      @TheSukhreetSingh Год назад

      Can you give us some examples of what you use factories for in real apps.

  • @dartdragoon5929
    @dartdragoon5929 Год назад +1

    Thanks for the explanation! It's the factory the same as a mapper then?

  • @GleiksonAri
    @GleiksonAri Год назад +2

    Can this Designer Pattern be used in projects with any architecture (VIPER, MVC, MVVM)?

    • @3366Har
      @3366Har Год назад +1

      Конечно, можно. Одно другому не мешает

    • @iOSAcademy
      @iOSAcademy  Год назад +1

      Yes, absolutely

    • @ConernicusRex
      @ConernicusRex Год назад +1

      All architectures are made up of various design patterns. you can use any you'd like they simply may not be best for the job.

  • @emiralkal4548
    @emiralkal4548 Год назад

    is this design pattern same with builder pattern? Or they are something different?

  • @rev_kous9275
    @rev_kous9275 Год назад

    I'm waiting for Clean Architecture implementation in iOS (UIKit/Swift).

  • @victorriurean
    @victorriurean Год назад

    cool

  • @itnadivane
    @itnadivane Год назад

    Are there any cons about making all those factory functions static? In this case you don't need to inject this Factory object into each view controller, and you can use it just like this - ScreenFactory.makeLoginScreen(params: SomeParams)

    • @iOSAcademy
      @iOSAcademy  Год назад

      Static is generally harder to test and has a memory impact. Instance APIs are preferred though its subjective to a degree