KunMinX / Jetpack-MVVM-Best-Practice
难得一见 Jetpack MVVM 最佳实践。在 "以简驭繁" 代码中，对 "视图控制器" 乃至 "标准化开发模式" 形成正确、深入理解。
A rare Jetpack MVVM best practice. In code that "uses simplicity to master complexity", you can form a correct and in-depth understanding of the "view controller" and even the "standardized development model". Machine translation by Claude Sonnet 5.5. A wrong translation? Report an error
- Stars
- 8,907 stars
- Forks
- 1,633 forks
- Language
- Java
- License
- Not reported
- Created
- Oct 31, 2019
- Last push
- Feb 7, 2024
- Updated
- Nov 10, 2026
Why these Tags: an agent read the README and quoted it
- Code examples from the readme:
本项目系我为方便开发者们 **无痛理解 Google 开源 Jetpack MVVM 中每个架构组件的 存在缘由、职责边界**，而 **精心设计的高频应用场景**，
An agent gave these Tags from the fixed Tag list in the AwesomeRepos source code. A code check kept each Tag only when its quote is in the text. A wrong Tag? Report an error with the form at the end of this page.
Admitted to the Repository Index on Nov 10, 2026: 8,906 stars on 2026-11-10.
Star History
185 days recorded, May 11, 2026 – Nov 11, 2026 (UTC). Net change +26 stars.
The star count of each day is the latest count minus the net stars of the later days.
Add this Star History to a README
The images follow the light or dark theme of the page that shows them, and update every hour.
Add ?theme=light or ?theme=dark
to the chart address to keep one theme.
Star History chart
[](https://awesomerepos.com/KunMinX/Jetpack-MVVM-Best-Practice) Badge
[](https://awesomerepos.com/KunMinX/Jetpack-MVVM-Best-Practice) Timeline
It gained stars on 24 of the 185 days recorded since May 11, 2026.
Its largest 7 days were Oct 10, 2026 to Oct 16, 2026: 4 stars.
In the 30 days to Nov 11, 2026 it got 11 stars, 175% more than in the 30 days before.
It had 8,881 stars before May 11, 2026 and has 8,907 stars now: 1,093 fewer than 10,000.
- Created on the Repository Host
- Latest push
- +1 stars in one day
- Largest star day recorded: +2 stars
- +2 stars in one day
- Entered the Repository Index: 8,906 stars on 2026-11-10
The timeline comes from the creation date and the releases on the Repository Host, the Admission, the Star History, and the Observations. Star milestones show only when the Star History records the day. The list shows up to 5 stable releases from the latest 10 releases recorded. When none of them is stable, one item counts the pre-releases. On the chart of net stars each day, a solid line marks each recorded release.
Forks and pushes
From 2 Observations, Nov 11, 2026 – Nov 12, 2026. Forks 0. AwesomeRepos saw a new push on 0 of 1 days.
- Nov 12, 2026: no new push
A filled day: the last push time changed since the Observation before it.
Health facts
Measured facts in four separate dimensions, each with a date and a source. AwesomeRepos does not add them into one score. AwesomeRepos reads the weekly commits, the changelog, and the community files each week for the 5,000 visible repositories with the most stars and for each rising repository. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 2 tasks for the maintainers of KunMinX/Jetpack-MVVM-Best-Practice.
Improve the Health Facts of the GitHub repository KunMinX/Jetpack-MVVM-Best-Practice. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/KunMinX/Jetpack-MVVM-Best-Practice. A change to the repository can improve each of the 2 items below. Each item gives the measured fact or score, and a task. 1. A release in the last 365 days Fact: No GitHub release (read on 2026-11-10). Rule: The newest published GitHub release (a pre-release counts; a draft does not) is 365 days old or less. A repository that publishes only tags, or only to a package registry, has no GitHub release. The release refresh reads the 10 newest releases after each push to the repository, and at least each 30 days. The index refresh reads the date of the last push each day. Task: Prepare a release, but do not publish it. Find the changes since the newest release, propose the next semantic version and the release notes, and ask me to publish the GitHub release. If nothing changed since the newest release, skip this item. If the project publishes only to a package registry, add a CI step that also makes a GitHub release for each version tag. 2. A licence Fact: GitHub finds no licence. Rule: GitHub finds a licence file. When GitHub cannot name the licence, the fact says so. Task: Ask me which licence to use. Do not choose one yourself. Then add the standard licence text as LICENSE at the root, so that GitHub can name the licence. Do not change the terms. Fill in only the fields of the template (for example the year and the copyright holder), and ask me for a value that you cannot verify. Rules for this work: - Each file must be true for this project. Do not copy text that does not apply to it. - Do not choose a licence, a contact, or a release version for me. Ask me. - Do not publish a release, change a repository setting, or push to the default branch. Make the changes on a new branch. - Keep each change small, and run the checks of this repository before you finish. - At the end, list each item as DONE, SKIPPED (with the reason), or NEEDS A DECISION (with the question). AwesomeRepos reads these facts again in its next scan. The definitions of the checks: https://awesomerepos.com/health-facts
Maintenance
1 of 4 checks (2 without data)-
Yes: Not archived
GitHub does not mark the repository as archived. Source
-
No: A push in the last 90 days
Last push on 2024-02-07, 1008 days ago. Source
-
No data: Commits in the last 13 weeks
No data: AwesomeRepos has not read the weekly commits.
-
No data: Commits in 26 or more of the last 52 weeks
No data: AwesomeRepos has not read the weekly commits.
Releases
0 of 3 checks (2 without data)-
No: A release in the last 365 days
No GitHub release (read on 2026-11-10). Source
-
No data: The newest release tag is a semantic version
No data: no release.
-
No data: A changelog file at the root
No data: AwesomeRepos has not scanned this repository.
Security practice
0 of 1 check (1 without data)-
No data: A security policy
No data: AwesomeRepos has not scanned this repository.
AwesomeRepos has not asked OpenSSF Scorecard about this repository.
Community files
0 of 3 checks (2 without data)-
No: A licence
GitHub finds no licence. Source
-
No data: A contributing guide
No data: AwesomeRepos has not scanned this repository.
-
No data: A code of conduct
No data: AwesomeRepos has not scanned this repository.
Dependencies in the index
This section shows the packages that connect this repository to other repositories in the index.
The GitHub dependency graph of this repository names 2 direct packages (scanned on Nov 12, 2026). Packages from 1 other repository in the index are among them.
No scanned repository names a package from this repository.
Uses (in the index) · 1
-
GitHub Actions: actions/checkout
Used by (in the index) · 0
None.
Sources: the GitHub dependency graph of each repository, and deps.dev for the source repository of each package (checked on Nov 3, 2026). A dependency graph also names development packages. deps.dev takes most source repositories from package metadata. How the dependency graph is made
Observations
Latest Observation, Nov 12, 2026: 8,907 stars, 1,633 forks, last push Feb 7, 2024, not archived. One of 2 Observations since Nov 11, 2026.