Moxy

Moxy is a library that help to use MVP pattern when you do the Android Application. Without problems of lifecycle and boilerplate code!

Main idea of using Moxy: See what's happening here in the wiki.

Capabilities

Moxy has a few killer features on other ways:

Presenter stay alive when Activity recreated(it simplify work with multithreading)
Automatically restore all what user see when Activity recreated(including dynamic content is added)
Capability to changes of many Views from one Presenter

Sample

View interface

public interface HelloWorldView extends MvpView {
	void showMessage(int message);
}

Presenter

@InjectViewState
public class HelloWorldPresenter extends MvpPresenter<HelloWorldView> {
	public HelloWorldPresenter() {
		getViewState().showMessage(R.string.hello_world);
	}
}

View implementation

public class HelloWorldActivity extends MvpAppCompatActivity implements HelloWorldView {

	@InjectPresenter
	HelloWorldPresenter mHelloWorldPresenter;

	private TextView mHelloWorldTextView;

	@Override
	protected void onCreate(Bundle savedInstanceState) {
		super.onCreate(savedInstanceState);
		setContentView(R.layout.activity_hello_world);

		mHelloWorldTextView = ((TextView) findViewById(R.id.activity_hello_world_text_view_message));
	}

	@Override
	public void showMessage(int message) {
		mHelloWorldTextView.setText(message);
	}
}

Here you can see "Github" sample application.

Wiki

For all information check Moxy Wiki

Android studio templates

In order to avoid boilerplate code creating for binding activity,fragments and its presentation part, we propose to use Android Studio templates for Moxy.

Templates located in /moxy-templates

References

[EN] Android without Lifecycle: MPVsV approach with Moxy

[RU] Moxy — реализация MVP под Android с щепоткой магии

[RU] MVP на стероидах: заставляем робота писать код за вас

[RU] Moxy. Из чего состоит и как этим пользоваться

[EN] MVP on steroids - how we force the robot to write code for you

Integration

Base modules integration:

dependencies {
  ...
  compile 'com.arello-mobile:moxy:1.1.1'
  provided 'com.arello-mobile:moxy-compiler:1.1.1'
}

If you want to see generated code, use apt instead of provided dependency type:

dependencies {
  ...
  apt 'com.arello-mobile:moxy-compiler:1.1.1'
}

For additional base view classes MvpActivity and MvpFragment add this:

dependencies {
  ...
  compile 'com.arello-mobile:moxy-android:1.1.1'
}

If you planing to use AppCompat, then you can use MvpAppCompatActivity and MvpAppCompatFragment. Then add this:

dependencies {
  ...
  compile 'com.arello-mobile:moxy-app-compat:1.1.1'
}

ProGuard

If you are using ProGuard you might need to add the following option:

-keep class **$$PresentersBinder
-keep class **$$State
-keep class **$$ViewStateClassNameProvider
-keepnames class * extends com.arellomobile.mvp.*

License

The MIT License (MIT)

Copyright (c) 2016 Arello Mobile

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

SelfHarmony/Moxy