My previous post has explained lot about MVP pattern in Android development. This post just want to share my talk in Onebit brownbag session about MVP pattern in Android development.
You can find my talk here.
In this joint brown bag session with Ansvia (Mindtalk), I am talking about a little introduction to one of rising design pattern popular in Android community, Reactive Programming.
MVP or Model-View-Presenter is a pattern that was derived from MVC. It’s now gaining importance in growing Android development since it has many advantages against the basic pattern.
So what’s MVP? It’s a Android development pattern that allows separate the presentation layer from the logic, so we can make this presentation layer more usable by various fragments that has same behavior.
So what does that mean?
MVC is one of the most used patterns that used by web developers to develop their web. Not only because it’s easy to understand, it’s easy to implement once it’s fundamental component is created.
The concept was made to separate bussiness logic and view logic to avoid confusion between these components.
Model is everything that is related to bussiness logic layer such as data and the rules that manages data.
View presents data to user. The key concept of view is template. Provided with many sets of data, view can presents data to user with purpose to make user understand these data.
This my first post at Onebit Engineering Blog. I want to share about my first engineering brown bag session which talking about repository Design Pattern, DDD and Unit Test, and for case study I try to implement all of these using Laravel 5.0.