PinnedPublished inProAndroidDevSingle Responsibility PrincipleA class should have one and only one reason to change.Sep 5, 2020Sep 5, 2020
PinnedPublished inProAndroidDevOpen-Closed PrincipleA class or module should be open for extension and closed for modification.Sep 6, 20202Sep 6, 20202
PinnedPublished inProAndroidDevLiskov Substitution PrincipleThe derived class must be usable through the base class interface, without the need for the user to know the difference.Sep 6, 2020Sep 6, 2020
PinnedPublished inProAndroidDevInterface Segregation PrincipleThe clients shouldn’t be forced to implement the methods that they do not use.Sep 6, 20202Sep 6, 20202
PinnedPublished inProAndroidDevDependency Inversion PrincipleOne should depend upon abstractions, not on the concrete implementation.Sep 6, 2020Sep 6, 2020
StorybookA library that helps you create a list of components by scanning compose functions that are marked with @Preview annotation.Nov 16, 2023Nov 16, 2023
Published inProAndroidDevS.O.L.I.D. PrinciplesWhat are the S.O.L.I.D. principles and why you will need them in your project?Sep 5, 2020Sep 5, 2020
Published inGlobantMay the power of Coroutine be with you…Using Coroutine to get rid of callbacks & asynchronous programming with ease.Apr 13, 20201Apr 13, 20201
Published inProAndroidDevClean Architecture for mobile: To be, or not to beRetrospection of Clean Architecture’s impact on mobile application development.Apr 13, 20202Apr 13, 20202
