Learning Path: SOLID Principles for Android

These five letters can do more for your effectiveness a developer than anything else when working in an object-oriented language. Dive deep and learn what SOLID really means.

Get more development news like this

S is for Single Responsibility Principle

The Single Responsibility Principle (SRP) states the following: A class should have only one reason to change.

O is for Open/Closed Principle

The Open/Closed principle states: Software entities should be open for extension, but closed for modification.

L is for the Liskov Substitution Principle

The Liskov Substitution Principle was introduced by Barbara Liskov in 1987. Find out what it states inside!

I is for the Interface Segregation Principle

The Interface Segregation Principle instructs developers to make fine-grained interfaces that are client-specific.

D is for the Dependency Inversion Principle

The Dependency Inversion Principle states that we as developers should follow two pieces of advice…

Next Up: SOLID Principles for Android#1: S is for Single Responsibility Principle

General link arrow white

About the content

This content has been published here with the express permission of the author.

Realm Team

At Realm, our mission is to help developers build better apps faster. We provide a unique set of tools and platform technologies designed to make it easy for developers to build apps with sophisticated, powerful features — things like realtime collaboration, augmented reality, live data synchronization, offline experiences, messaging, and more.

Everything we build is developed with an eye toward enabling developers for what we believe the mobile internet evolves into — an open network of billions of users and trillions of devices, and realtime interactivity across them all.

4 design patterns for a RESTless mobile integration »