# UCodeUStory/S-MVP

🔥🔥优化版MVP,使用注解泛型简化代码编写，使用模块化协议方便维护，APT过程使用注解解析器利用JavaPoet🌝完成重复模块的编写，利用ASpect+GradlePlugin 完成横向AOP编程+Javassist动态字节码注入+Tinker实现热修复+Retrofit实现优雅网络操作+RxJava轻松玩转数据处理

Repository: https://github.com/UCodeUStory/S-MVP
Canonical: https://ross.abutalabs.com/products/s-mvp
Language: Java
License: MIT
License Family: permissive
Topics: mvp, javassist, gradle, aspectj, apt, hook, javassist-aop, android, rxjava, retrofit2, lifecycle
Last push: 2019-08-23T08:21:00+00:00

## Health v2 (maintenance only)
Score: 23/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 0, release rhythm 8, longevity 100
- inputs: {"age_days": 3248, "days_push": 2567, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1080, forks 125 (observed 2026-08-28T04:03:30.627006+00:00)

## What it is
An optimized Android MVP framework written in Java that simplifies Presenter/View boilerplate using annotations, generics, and APT code generation with JavaPoet. It integrates AspectJ via a Gradle plugin, Javassist bytecode injection, Tinker hot-fixing, Retrofit networking, and RxJava for reactive data handling.

## Use cases
- reduce MVP boilerplate classes in Android apps
- generate Presenter code automatically with annotations
- apply AOP cross-cutting concerns like logging and caching in Android
- inject bytecode without modifying source code using Javassist
- implement hot fixes in production Android apps with Tinker
- coordinate multiple parallel async requests and merge results
- chain sequential network requests without nested callbacks
- bind views with a custom annotation-based BindView

## When to choose
- building an Android app with MVP architecture and less boilerplate
- you want AOP features like method timing logs, memory caching, and login checks via annotations
- you need coordinated parallel or serial async task management
- you want an integrated stack of Retrofit, RxJava, and Tinker hot-fixing

## When to avoid
- starting a new Android project where modern MVVM/MVI with Kotlin and Jetpack is preferred
- the project is inactive and targets older Android SDKs and Java-based tooling
- you want minimal dependencies rather than a full framework with bytecode weaving and hot-fix tooling

## Facets
- artifact type: framework
- maturity: maintenance
- function: web-framework, middleware, developer-tools, build-tool, logging, caching, http-client, concurrency
- domain: mobile-development, android-tools, developer-tools, web-development
- platform: jvm
- tags: mvp, android, aspectj, javassist, apt, annotation-processing, tinker, hotfix, retrofit, rxjava, aop, bytecode-injection, lifecycle, modular-architecture, chinese-documentation, gradle

## Member repositories
- UCodeUStory/S-MVP (main) score 23

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:03:30.627006+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T06:51:26.408921+00:00, confidence not recorded.
  - readme: https://github.com/UCodeUStory/S-MVP (fetched 2026-08-28T04:03:30.627006+00:00, sha 2cc1cb2ad08b)
- Data as of 2026-08-30T08:39:29.467469+00:00.