The number of users of mobile gadgets around the world is rapidly growing every day, and everyday thousands of IT companies are working on a variety of programs and applications on Android.
Usually a program is made up of many classes. So the logic and computation is distributed among these classes. However, as more classes are developed in a program, especially during maintenance and/or refactoring, the problem of communication between these classes may become more complex. This makes the program harder to read and maintain. Furthermore, it can become difficult to change the program, since any change may affect code in several other classes.
Our developers from [bvblogic] company use the Mediator pattern. Mediator defines an object that encapsulates how a set of objects interact. This pattern is considered to be a behavioral pattern due to the way it can alter the program’s running behavior.
With the Mediator pattern, communication between objects is encapsulated with a mediator object. Objects no longer communicate directly with each other, but instead communicate through the mediator. This reduces the dependencies between communicating objects, thereby lowering the coupling.
Read more about Mediator visiting our GitHub profile. Draw your use of it and make your own contribution to bettering of the system.