RIBs VS Mosby

Compare RIBs vs Mosby and see what are their differences.


A Model-View-Presenter / Model-View-Intent library for modern Android apps (by sockeqwe)
Our great sponsors
  • Appwrite - The Open Source Firebase alternative introduces iOS support
  • SonarQube - Static code analysis for 29 languages.
  • InfluxDB - Access the most powerful time series database as a service
RIBs Mosby
4 1
7,397 5,492
0.5% -
3.3 0.0
15 days ago over 1 year ago
Kotlin Java
Apache License 2.0 Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of RIBs. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-05-25.


Posts with mentions or reviews of Mosby. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-08-27.
  • How to start writing reusable components for Android apps?
    2 projects | dev.to | 27 Aug 2022
    Yep, and not only for the app layer. Plenty articles on that matter. I recommend you to read Hannes Dorfmann’s story on MVI since a lot of useful concepts and ideas are there. He elaborates on topics such as how to organise, test, reuse and maintain your code which is not a part of this article but those two topics are strictly related. On the other hand I’m not a fan of tools like Mosby or Moxy because I painfully found out they are rather constraining. Inheriting behaviour, state or plugins from base classes was catastrophic in our cases. Refactors and building custom behaviour for new screens were messy tasks and required much effort. Instead, use lifecycle aware components (again, see Android tools) or setup your architecture the way that you can call your business logic anytime. Some people calls it overhead. I would call it simplicity especially most of us happen to use caching.

What are some alternatives?

When comparing RIBs and Mosby you can also consider the following projects:

Moxy - Moxy is MVP library for Android

nucleus - Nucleus is an Android library, which utilizes the Model-View-Presenter pattern to properly connect background tasks with visual parts of an application.

ThirtyInch - a MVP library for Android favoring a stateful Presenter

EasyMVP - A full-featured framework that allows building android applications following the principles of Clean Architecture.

RoboBinding - A data-binding Presentation Model(MVVM) framework for the Android platform.

AndroidBinding - MVVM for Android

Template for quickly initialize a new project

Villains & Heroes - Android app built with MVP architectural approach and uses Marvel Comics API that allows developers everywhere to access information about Marvel's vast library of comics. :zap:

Moviper - A Mosby based VIPER library for Android

react-native-contacts - React Native Contacts

ios-architecture - A collection of iOS architectures - MVC, MVVM, MVVM+RxSwift, VIPER, RIBs and many others

Theatre - Pet project using Clean Architecture + MVVM + Reactive Extensions + Android Architecture Components. The data are fetched from LondonTheatreDirect API. 🎭