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