awesome-repositories.com
Blog
MCP
awesome-repositories.com

Discover the best open-source repositories with AI-powered search.

ExploreCurated searchesOpen-source alternativesSelf-hosted softwareBlogSitemap
ProjectMCP serverAboutHow we rankPress
LegalPrivacyTerms
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
sockeqwe avatar

sockeqwe/mosby

0
View on GitHub↗
5,439 stars·834 forks·Java·Apache-2.0·13 viewshannesdorfmann.com/mosby↗

Mosby

Mosby is a presentation layer framework for Android applications designed to manage application state and user intents. It functions as an architectural tool that implements both Model-View-Intent (MVI) and Model-View-Presenter (MVP) patterns.

The framework utilizes a unidirectional data flow to maintain a single source of truth, ensuring that state updates remain predictable by processing intents through a single logic path. It separates business logic from the view layer to decouple presentation logic from Android Activity and Fragment classes.

The system provides capabilities for state management and navigation coordination, syncing application state with screen transitions.

Features

  • Android State Management Frameworks - Provides a framework for managing complex UI state in Android apps using a single source of truth.
  • Android App Architecture Patterns - Offers structural design patterns for organizing Android applications to separate business logic from the user interface.
  • Android MVP Frameworks - Provides a framework implementing the Model-View-Presenter pattern specifically for Android applications.
  • MVI Integration - Acts as a presentation layer framework for Android supporting both MVP and MVI architectural patterns.
  • Logic and Presentation Separation - Isolates business logic and data fetching from visual Android components to simplify development and testing.
  • MVP Implementations - Provides an implementation of the Model-View-Presenter pattern to separate business logic from the view layer.
  • Presenter Patterns - Uses presenter patterns to move complex logic out of Android Activity and Fragment classes for better testability.
  • Unidirectional Data Flow Architectures - Implements a unidirectional data flow architecture to ensure predictable state updates via processed user intents.
  • Android - Implements an opinionated framework for managing reactive screen state in Android using unidirectional data flow.
  • UI Navigation Coordination - Coordinates transitions and logical flows between different Android user interface pages to ensure correct data display.
  • State-Driven Navigations - Coordinates navigation triggers based on state management actions to preserve application state during transitions.
  • Advanced Development Frameworks - Model-View-Presenter and Model-View-Intent library.

Star history

Star history chart for sockeqwe/mosbyStar history chart for sockeqwe/mosby

How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.

AI search

Explore more awesome repositories

Describe what you need in plain English — the AI ranks thousands of curated open-source projects by relevance.

Start searching with AI

Frequently asked questions

What does sockeqwe/mosby do?

Mosby is a presentation layer framework for Android applications designed to manage application state and user intents. It functions as an architectural tool that implements both Model-View-Intent (MVI) and Model-View-Presenter (MVP) patterns.

What are the main features of sockeqwe/mosby?

The main features of sockeqwe/mosby are: Android State Management Frameworks, Android App Architecture Patterns, Android MVP Frameworks, MVI Integration, Logic and Presentation Separation, MVP Implementations, Presenter Patterns, Unidirectional Data Flow Architectures.

Which projects share features with sockeqwe/mosby?

Projects with overlapping indexed features include: antoniolg/androidmvp — This project is a reference implementation of the Model-View-Presenter architecture for Android applications. It… airbnb/mavericks — Mavericks is an opinionated Android state management framework that structures screen-level state as a single… janishar/android-mvp-architecture — This project is a reference implementation of the Model-View-Presenter (MVP) architecture for Android applications. It… tommylemon/android-zblibrary — Android-ZBLibrary is a mobile framework providing core primitives for Android development, including a… android10/android-cleanarchitecture-kotlin — This project is a reference Kotlin Android application template and a set of sample implementations demonstrating… jessyancoding/mvparms — MVPArms is an Android application framework based on the Model-View-Presenter pattern. It provides a foundation for…

Projects sharing features with Mosby

These projects share indexed features with Mosby. Shared tags can include platform or build tooling; verify the primary use case before treating a result as a replacement.
  • antoniolg/androidmvpantoniolg avatar

    antoniolg/androidmvp

    5,900View on GitHub↗

    This project is a reference implementation of the Model-View-Presenter architecture for Android applications. It serves as a structural example of how to separate business logic from the user interface through a presenter-based framework. The implementation focuses on a clean architecture approach, using presenters to mediate all communication between the data model and the view. It employs a passive view pattern and interface-based decoupling to isolate the user interface from domain rules. The architecture incorporates interactor-based domain logic and layered separation to reduce systemic

    Java
    View on GitHub↗5,900
  • airbnb/mavericksairbnb avatar

    airbnb/mavericks

    5,934View on GitHub↗

    Mavericks is an opinionated Android state management framework that structures screen-level state as a single immutable object and processes user actions through a unidirectional data flow. It enforces state immutability to prevent unintended mutations and simplify debugging, while managing state subscriptions and cleanup based on Android lifecycle events to prevent memory leaks. The framework uses a ViewModel-driven architecture where business logic and state management are encapsulated in ViewModels that survive configuration changes. User actions are handled through dedicated intent object

    Kotlin
    View on GitHub↗5,934
  • janishar/android-mvp-architecturejanishar avatar

    janishar/android-mvp-architecture

    4,425View on GitHub↗

    This project is a reference implementation of the Model-View-Presenter (MVP) architecture for Android applications. It focuses on separating business logic from the user interface by decoupling data logic, UI presentation, and view layers. The implementation distinguishes itself through the inclusion of a boilerplate generator that automatically creates the activity, presenter, and view files required for the MVP pattern. It utilizes a compile-time dependency injection framework to manage object lifetimes and a reactive programming workflow to handle asynchronous data streams and event propag

    Javaandroid-architectureandroid-mvp-architecturedagger
    View on GitHub↗4,425
  • tommylemon/android-zblibraryTommyLemon avatar

    TommyLemon/Android-ZBLibrary

    5,604View on GitHub↗

    Android-ZBLibrary is a mobile framework providing core primitives for Android development, including a Model-View-Presenter framework for structural architecture, a network request wrapper, and a local data persistence layer. It also includes a library of reusable interface elements and a background task manager to maintain user interface responsiveness. The framework decouples business logic from user interfaces through its MVP implementation and manages external service integration via tools for HTTP communication, JSON processing, and response caching. The library covers a broad set of ca

    Javafastjsonglideokhttp
    View on GitHub↗5,604
Compare all 30 related projects→