Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


Alfonz - Arch Module

Base classes for MVVM architecture (based on Architecture Components).

The purpose of this module is to simplify implementation of MVVM architecture. MVVM binder is based on Data Binding Library from Google. This module provides 4 abstract base elements (Activity, Fragment, View, ViewModel) which make up view and view-model layers of MVVM architecture.

This Arch module is basically a wrapper for Android Architecture Components library. It provides some additional features and convenient methods. If you are interested in MVVM architecture, you can check my talk about MVVM which I presented at STRV Android Meetup. See the video record or slides for more info. Alfonz Arch module uses a similar approach which I describe in the presentation.

AlfonzActivity provides some convenient methods for setting up ActionBar and managing Fragments. It implements LifecycleOwner to handle lifecycle changes.

AlfonzBindingFragment takes care of view-model and data binding initialization and binding view and view-model layers in a layout. It implements LifecycleOwner to handle lifecycle changes.

AlfonzView represents an interface which serves as a communication bridge between XML layout and Fragment. It is usually used for:

  • Event callbacks, invoked from XML layout using data binding

AlfonzViewModel is automatically retained during configuration changes. It implements android.databinding.Observable for registering observable callbacks. It also provides LiveData event bus for sending events from view-model layer to view layer. The bus is usually used for:

  • UI-related operations which cannot be done via data binding, e.g. show a dialog or a toast
  • Android-related operations which have to be performed from view-model layer, e.g. starting an activity

If you want to have Activity with its own ViewModel, use AlfonzBindingActivity. This module also contains a few useful binding adapters and conversions. You can find them in BindingUtility class.

How to use

First of all, it's good practice to create base classes for Activity, Fragment, ViewModel in your project so you can share global methods or fields. Your base classes will extend Alfonz base classes.

public abstract class BaseActivity extends AlfonzActivity {
	// add whatever you need...
public abstract class BaseFragment<T extends BaseViewModel, B extends ViewDataBinding>
		extends AlfonzBindingFragment<T, B> {
	public void onCreate(Bundle savedInstanceState) {
		getViewModel().observeEvent(this, ToastEvent.class, toastEvent -> showToast(toastEvent.message));

	public void showToast(String message) {
		Toast.makeText(getActivity(), message, Toast.LENGTH_LONG).show();
public abstract class BaseViewModel extends AlfonzViewModel {
	public void handleError(String message) {
		sendEvent(new ToastEvent(message));

Now you can implement classes which will represent a screen. I will show you how to use this Arch module on a very simple Hello World example.

Let's start with Activity. You can choose which action bar indicator you prefer to use.

public class HelloWorldActivity extends BaseActivity {
	public void onCreate(Bundle savedInstanceState) {

Create an Activity layout. Toolbar in the layout must be identified as R.id.toolbar. If you are going to switch fragments in your Activity using replaceFragment() convenient method, create a layout container with R.id.container_fragment identifier for it.


	<include layout="@layout/toolbar" />

		android:layout_weight="1" />


Now let's create a View. It will have just one event callback method.

public interface HelloWorldView extends AlfonzView {
	void onClick();

View interface will be implemented by a Fragment. We have to specify which ViewModel class will represent our view-model layer, we have to inflate our binding layout and implement View methods. You can call getViewModel() from the Fragment to access a ViewModel instance. You can get a binding object via getBinding() call. View should stay as dumb as possible and should not have any logic. AlfonzFragment also provides onBackPressed() method which can be overridden to handle back button press.

public class HelloWorldFragment
		extends BaseFragment<HelloWorldViewModel, FragmentHelloWorldBinding>
		implements HelloWorldView {
	public HelloWorldViewModel setupViewModel() {
		return ViewModelProviders.of(this).get(HelloWorldViewModel.class);

	public FragmentHelloWorldBinding inflateBindingLayout(@NonNull LayoutInflater inflater) {
		return FragmentHelloWorldBinding.inflate(inflater);

	public void onClick() {

Create a Fragment layout. View is bound in the layout in BR.view variable, ViewModel is bound in BR.viewModel variable. You have to define these variables in the layout. Use view for invoking event callbacks and viewModel for accessing observable properties exposed by the ViewModel. I recommend not to use complex data binding expressions. It is not possible to test it. All the logic should be in the ViewModel.


		<variable name="view" type="com.example.ui.HelloWorldView" />
		<variable name="viewModel" type="com.example.viewmodel.HelloWorldViewModel" />


			android:onClick="@{() -> view.onClick()}" />

Finally let's create a ViewModel. The best thing about the ViewModel is that it is persisted so you don't lose state or data during device configuration changes. You don't have to use retained Fragments anymore. ViewModel instance is automatically removed after a Fragment is completely gone. I recommend to implement the ViewModel as plain Java for better testability. Never ever use Activity Context in the ViewModel. If you need the Context, use Application Context, it is safer. You can use AlfonzBundleViewModelFactory and AlfonzBundleViewModel to pass Application Context and Bundle data to the ViewModel.

public class HelloWorldViewModel extends BaseViewModel {
	public final MutableLiveData<Integer> state = new MutableLiveData<>();
	public final MutableLiveData<MessageEntity> message = new MutableLiveData<>();

	public void loadData() {
		// show progress

		// load data from data provider...

	public void updateMessage(String text) {
		MessageEntity m = message.getValue();

	private void onLoadData(MessageEntity m) {
		// save data

		// show content
		if (message.getValue() != null) {
		} else {

Communication from ViewModel to View layer is done via LiveData event bus. LiveBus is a part of AlfonzViewModel and it is basically a map with LiveEvent instances for each event type. New instance of LiveEvent is created automatically inside the bus once the specific event is observed or sent for a first time. So event should be delivered even if an observer is not active. ViewModel has no direct reference to Views. LiveData events can be observed by more Fragment instances, but each event will be delivered just once to the first observer. This is intentional, because actions like show a dialog or start an activity should be run just once.

public class SnackbarEvent extends Event {
	public final String message;

	public SnackbarEvent(String message) {
		this.message = message;
// observe event in Fragment
getViewModel().observeEvent(this, SnackbarEvent.class, snackbarEvent -> showSnackbar(snackbarEvent.message));
// send event in ViewModel
sendEvent(new SnackbarEvent(message));

AlfonzViewModel has just one lifecycle method onCleared() which is called when ViewModel is no longer used and will be destroyed. Sometimes it could be useful to have in ViewModel the same lifecycle methods as Activity or Fragment provide. ViewModel can implement LifecycleObserver to accomplish this.

public class HelloWorldViewModel extends BaseViewModel implements LifecycleObserver {
	public void onStart() {
		// load data
		if (message.getValue() == null) loadData();
// register observer in Fragment

There are also a few useful binding adapters. You can use following XML attributes in your views:

  • onClick
  • onLongClick
  • visible
  • invisible
  • gone
  • imageBitmap


  • Android Architecture Components
  • Android Support Library
  • Data Binding Library

Samples and download

See the main README file.