Developers: WeaponZhi, hiyangyue, xiaweizi, foxlee

AI Geek Workshop - Public account, welcome to follow us if you are interested in AI!

An ultimate App. A learning project to help you enhance your ability to independently develop the business layer of Android applications. This development framework enables rapid application building. You can also use it as a tool app for reference in your daily development.

Package Building Methods:

gradlew cleanLib
gradlew buildLib -q -Dbundle.arch=x86
gradlew cleanBundle
gradlew buildBundle -q -Dbundle.arch=x86

• -q represents the clean mode, displaying only the packaging results of the plugin.
• In -Dbundle.arch, use x86 for emulator debugging and armeabi for physical device debugging.

In Case of App Crash on Physical Device:

1. Check the logs in Logcat and locate the error.
2. If there are no obvious error logs, or if the error is PushReceiver ClassNotFoundException, please determine the CPU type of the physical device and package accordingly.

You can obtain the CPU type through:

adb shell
cat /proc/cpuinfo  

For example, Redmi Note 3:

Processor	: AArch64 Processor rev 2 (aarch64)

The corresponding packaging command should be changed to:

# For '.so' files, differentiate CPU architecture. 
# Generally, use 'x86' for emulators and 'armabi armeabi-v7a arm64-v8a' for physical devices.
gradlew buildLib -q -Dbundle.arch=arm64-v8a
gradlew buildBundle -q -Dbundle.arch=arm64-v8a

Script Packaging Method:

buildAll        # Full packaging
buildBundle     # Package only the Bundle if Lib remains unchanged
buildAll q d    # Equivalent to adding '-q' and '-Dbundle.arch=x86'
buildBundle q d # Equivalent to adding '-q' and '-Dbundle.arch=x86'

If there are errors during packaging, you can first execute gradlew cleanBuild and then retry the packaging process.

For detailed packaging command parameters, please refer to the Small documentation: Small Documentation

TDD requires writing test code before writing the actual code for a feature. Then, you write only the code necessary to pass the tests. This process helps in producing concise, usable, and high-quality code, ultimately accelerating the development process.

TDD indirectly assists programmers in writing well-designed code. To ensure testability, the classes and methods in the code must strictly adhere to the Single Responsibility Principle.

Furthermore, with the encapsulated MVVM framework, you can test the entire page logic by performing unit tests only on the ViewModel layer methods, constructing empty View and Model parameters.

This project utilizes a highly encapsulated MVVM framework and databinding for efficient development. This framework allows for rapid business logic development while abstracting the underlying databinding technical details. As a result, even developers who are not deeply familiar with MVVM and databinding can develop smoothly by following the framework's flow.

Moreover, this framework facilitates effortless unit testing. The specific development process of MVVM and unit testing operations will be supplemented in subsequent development stages.

This project will integrate, encapsulate, and redevelop the most widely used, professional, and popular technologies in the current Android landscape, applying them to practical scenarios. The currently planned technologies for introduction include (bolded items indicate secondary development or fully self-developed libraries):

• DataBinding + MVVM Development
• Component-Based Development
• Small Plugin Framework
• Databinding
• Custom Server
• Custom Gradle Plugin
• Integrated Official Sharing for QQ, WeChat, and Weibo
• Cross-Platform Push Notification Service
• UMeng Statistics
• OkHttp + Retrofit + RxJava
• Refresh List Library Extended from RecyclerView
• Component-Based Controls
• Unit Testing
• Integrated Debugging for Components
• Instant Messaging
• Video Service
• Material Design
• Glide

• [func] do sth: Feature development
• [fixbug] #xx# do sth: Bug fix, where #xx# is the issue number
• [docs] do sth: Documentation
• [chore] do sth: Build-related modifications
• [test] do sth: Adding test code
• [optimize] do sth: Optimizing parts of the code
• [style] do sth: Code formatting, removing blank lines, etc., not related to functionality

Set DEBUG to true in gradle.properties to enable the integrated debugging environment. Set the corresponding modules you need to debug to true.

For instance, if you need to debug the mine and message modules, set DEBUG, DEVELOP_MINE, and DEVELOP_MESSAGE to true, and then re-sync Gradle.

When DEBUG is set to false, it represents a full package compilation or Release mode, where all modules are added by default, ignoring the individual configuration boolean values of the modules below.

开发人じん员：WeaponZhi，xiaweizi，hiyangyue，foxlee

AI极客研修けんしゅう站-作者さくしゃWeaponZhi的てき公おおやけ众号，对AI有ゆう兴趣的てき童わらわ鞋欢迎むかえ关注~

一いち个极致的App。学がく习项目め，帮助你提升ます独自どくじ开发 Android 业务层的能力のうりょく。基もと于该开发框かまち架か，可か以快速そく构建应用，同どう时你可か以当做一个工具ぐ App，以供你平时开发参考さんこう。

整せい包つつみ打だ包つつみ方式ほうしき：

gradlew cleanLib
gradlew buildLib -q -Dbundle.arch=x86
gradlew cleanBundle
gradlew buildBundle -q -Dbundle.arch=x86

其中 -q 代表だいひょう整せい洁模式しき，只ただ看み到いた插件的てき打だ包つつみ结果信しん息いき。

-Dbundle.arch 中ちゅう，如果是ぜ模も拟器调试，则是x86，如果是ぜ真ま机つくえ调试则是armeabi

如遇真ま机つくえ启动奔溃

请先检查Logcat下した的てき日び志こころざし，并定位ていい到いた对应的てき错误。若わか无明显的错误日び志こころざし，或ある者もの是これPushReceiver ClassNotFoundException的てき错误，请先确定真ま机つくえ的てきCPU的てき类型，并根据すえ类型进行相しょう应的打だ包つつみ。

通つう过

adb shell
cat /proc/cpuinfo  

的てき方式ほうしき获取CPU类型，比ひ如红米まい note 3：

Processor	: AArch64 Processor rev 2 (aarch64)

对应的てき打だ包つつみ则更换为

#so版ばん， 区分くぶんCPU架か构，一般いっぱん模も拟器使用しよう x86，真ま机つくえ使用しよう armabi armeabi-v7a arm64-v8a
gradlew buildLib -q -Dbundle.arch=arm64-v8a
gradlew buildBundle -q -Dbundle.arch=arm64-v8a

脚本きゃくほん打だ包つつみ方式ほうしき：

buildAll        全量ぜんりょう打だ包つつみ
buildBundle     只ただ打だ包つつみBundle，Lib没ぼつ改あらため变
buildAll q d    相当そうとう于加-q 和わ -Dbundle.arch=x86
buildBundle q d 相当そうとう于加-q 和わ -Dbundle.arch=x86

打だ包つつみ如果出で现异常つね，可か以先输入 gradlew cleanBuild，再さい重じゅう新しん执行一いち遍へん打だ包つつみ流りゅう程ほど 详细打だ包つつみ指令しれい参さん数すう请参考さんこうSmall文ぶん档:Small文ぶん档

它要求ようきゅう在ざい编写某ぼう个功能のう的てき代だい码之前まえ先さき编写测试代だい码，然しか后きさき只ただ编写使し测试通どおり过的功こう能代のしろ码，通つう过测试来推动整せい个开发的进行。这有助じょ于编写うつし简洁可用かよう和わ高だか质量的てき代だい码，并加速そく开发过程。

测试驱动开发会かい反はん向こう帮助程ほど序じょ员编写うつし设计性せい良好りょうこう的てき代だい码，为了保ほ证代码的可か测性，要求ようきゅう代だい码中的てき类和方法ほうほう必须严格遵循单一性せい原げん则。

同どう时，通つう过已经封装そう好こう的てき MVVM 框かまち架か，可か以只通どおり过单元测试 ViewModel 层方法ほう，构造空そら的てき View 和わ Model 参さん数すう，从而测试整せい个页面めん逻辑。

通つう过高度ど封ふう装そう的てき MVVM 框かまち架か，配合はいごうdatabinding进行高だか效こう开发，通つう过该框かまち架か，可か以快速そく的てき进行业务逻辑的てき开发，对 databinding 底そこ层技术进行ぎょう隐藏，即そく使つかい程ほど序じょ员对 MVVM 和わ Databinding 理解りかい不ふ深ふか，按照框かまち架か流りゅう程ほど也可以顺畅开发。

并且通どおり过该框かまち架か，可か以轻松まつ的てき进行单元测试，MVVM 的てき具体ぐたい开发流りゅう程ほど和わ单元测试操作そうさ，将はた在ざい后きさき续开发过程ほど中ちゅう补充。

我わが们将在ざい项目中ちゅう集成しゅうせい、封ふう装そう和わ二に次じ开发现在 Android 领域使用しよう最多さいた，最さい专业，最さい热门的てき技わざ术，并实用よう在ざい项目中ちゅう，目前もくぜん计划引入的てき技わざ术有(加か粗そ字体じたい为二次开发或者完全自主开发库)：

• DataBinding+MVVM开发
• 组件化か开发
• Small 插件化か框かまち架か
• Databinding
• 自じ建けん服ふく务器
• 自じ定てい义 Gradle 插件
• 集成しゅうせいQQ、微ほろ信しんじ、微ほろ博はく官かん方かた分ぶん享とおる
• 全ぜん平台ひらだい推送服ふく务
• 友とも盟めい统计
• OkHttp + Retrofit + RxJava
• 通つう过 RecyclerView 拓つぶせ展てん的てき刷新さっしん列れつ表ひょう库
• 控ひかえ件けん组件化か
• 单元测试
• 组件化か集成しゅうせい调试
• 即そく时通讯
• 视频服ふく务
• Material Design
• Glide

注ちゅう：首くび页数据すえ样式参考さんこう于慕课网组件化か视频 https://coding.imooc.com/learn/list/84.html 使用しよう项目MVVM重おも新しん实现 感かん谢 qndroid 老ろう师

• [func] do sth：功こう能のう开发
• [fixbug] #xx# do sth：Bug 修おさむ改あらため，#号ごう内ない为 issue 编号
• [docs] do sth：文ぶん档
• [chore] do sth：build相しょう关的修おさむ改あらため
• [test] do sth：添加てんか测试代だい码
• [optimize] do sth: 优化部分ぶぶん代だい码
• [style] do sth: 格式かくしき化か上じょう的てき格式かくしき化か、删除空白くうはく行ぎょう等とう，无关功こう能のう

在ざい gradle.properties 中ちゅう DEBUG 为 true 则打开集成しゅうせい调试环境，需要じゅよう哪几个模块联调，就把下面かめん的てき对应模も块置为 true。

比ひ如我要よう联调 mine 和わ message 模も块，就把DEBUG、DEVELOP_MINE和わDEVELOP_MESSAGE置おけ为true，然しか后きさき重おも新しん同どう步ふ一いち下かGradle即そく可か

DEBUG 置おけ为 false 的てき时候为整包つつみ编译或ある者もの可か以理解りかい为Release模も式しき，将はた默だま认添加てんか所有しょゆう模も块，忽ゆるがせ略りゃく下面かめん模も块的单独配置はいち布ぬの尔值。

待まち补充

未完みかん待まち续，目前もくぜん正せい迭代中ちゅう...