深度了解Flutter APP的构建流程

this.project = project

// 配置maven仓库地址，环境变量有配置FLUTTER_STORAGE_BASE_URL就优先用，没就缺省值

String hostedRepository = System.env.FLUTTER_STORAGE_BASE_URL ?: DEFAULT_MAVEN_HOST

String repository = useLocalEngine()

? project.property(‘local-engine-repo’)

“$hostedRepository/download.flutter.io”

project.rootProject.allprojects {

repositories {

maven {

url repository

}

}

}

// 创建app模块中配置的flutter{ source: ‘…/…/’}闭包extensions

// source：用来配置当前Flutter工程的根路径，注意不是Android工程，如果没有配置抛出Must provide Flutter source directory异常

// target：用来指定Flutter代码的启动入口，如果没有配置默认为lib/main.dart

project.extensions.create(“flutter”, FlutterExtension)

//添加flutter构建相关的各种task

//文章最开始提到的构建流程最后执行阶段添加的几个flutter相关的task就是在这里添加：eg,

// app:compileFlutterBuildDebug

// app:packLibsflutterBuildDebug

// app:copyFlutterAssetsDebug

// 后面单独分析

this.addFlutterTasks(project)

// By default, assembling APKs generates fat APKs if multiple platforms are passed.

// Configuring split per ABI allows to generate separate APKs for each abi.

// This is a noop when building a bundle.

// 判断是否根据(abi)分包编译

if (shouldSplitPerAbi()) {

project.android {

splits {

abi {

// Enables building multiple APKs per ABI.

enable true

// Resets the list of ABIs that Gradle should create APKs for to none.

reset()

// Specifies that we do not want to also generate a universal APK that includes all ABIs.

universalApk false

}

}

}

}

//判断编译命令是否添加–target-platform=xxxABI参数，没有就用缺省，有就看这个ABI是否flutter支持的，支持就配置，否则抛出异常

getTargetPlatforms().each { targetArch ->

String abiValue = PLATFORM_ARCH_MAP[targetArch]

project.android {

if (shouldSplitPerAbi()) {

splits {

abi {

include abiValue

}

}

}

}

}

//通过属性配置获取flutter.sdk，或者通过环境变量FLUTTER_ROOT获取，都没有就抛出环境异常

String flutterRootPath = resolveProperty(“flutter.sdk”, System.env.FLUTTER_ROOT)

if (flutterRootPath == null) {

throw new GradleException(“Flutter SDK not found. Define location with flutter.sdk in the local.properties file or with a FLUTTER_ROOT environment variable.”)

}

flutterRoot = project.file(flutterRootPath)

if (!flutterRoot.isDirectory()) {

throw new GradleException(“flutter.sdk must point to the Flutter SDK directory”)

}

//获取Flutter Engine的版本号，如果通过local-engine-repo参数使用本地自己编译的Engine则版本为+，否则读取SDK目录下bin\internal\engine.version文件值，一串类似MD5的值

engineVersion = useLocalEngine()

? “+” // Match any version since there’s only one.

“1.0.0-” + Paths.get(flutterRoot.absolutePath, “bin”, “internal”, “engine.version”).toFile().text.trim()

//依据平台获取对应flutter命令脚本，都位于SDK目录下bin\中，名字为flutter

String flutterExecutableName = Os.isFamily(Os.FAMILY_WINDOWS) ? “flutter.bat” : “flutter”

flutterExecutable = Paths.get(flutterRoot.absolutePath, “bin”, flutterExecutableName).toFile();

//获取flutter混淆配置清单，位于SDK路径下packages\flutter_tools\gradle\flutter_proguard_rules.pro

//里面配置只有 -dontwarn io.flutter.plugin.** 和 -dontwarn android.**

String flutterProguardRules = Paths.get(flutterRoot.absolutePath, “packages”, “flutter_tools”,

“gradle”, “flutter_proguard_rules.pro”)

//新增profile构建类型，在当前project下的android.buildTypes中进行配置

project.android.buildTypes {

// Add profile build type.

profile {

initWith debug

if (it.hasProperty(“matchingFallbacks”)) {

matchingFallbacks = [“debug”, “release”]

}

}

release {

// Enables code shrinking, obfuscation, and optimization for only

// your project’s release build type.

minifyEnabled true

// Enables resource shrinking, which is performed by the

// Android Gradle plugin.

// NOTE: The resource shrinker can’t be used for libraries.

shrinkResources isBuiltAsApp(project)

// Fallback to android/app/proguard-rules.pro.

// This way, custom Proguard rules can be configured as needed.

proguardFiles project.android.getDefaultProguardFile(“proguard-android.txt”), flutterProguardRules, “proguard-rules.pro”

}

}

if (useLocalEngine()) {

// This is required to pass the local engine to flutter build aot.

String engineOutPath = project.property(‘local-engine-out’)

File engineOut = project.file(engineOutPath)

if (!engineOut.isDirectory()) {

throw new GradleException(‘local-engine-out must point to a local engine build’)

}

localEngine = engineOut.name

localEngineSrcPath = engineOut.parentFile.parent

}

//给所有buildTypes添加依赖，addFlutterDependencies

project.android.buildTypes.all this.&addFlutterDependencies

}

/**

• Adds the dependencies required by the Flutter project.

• This includes:

• 1. The embedding
• 2. libflutter.so

*/

void addFlutterDependencies(buildType) {

//获取flutter build类型，值为debug、profile、release

String flutterBuildMode = buildModeFor(buildType)

if (!supportsBuildMode(flutterBuildMode)) {

return

}

// The embedding is set as an API dependency in a Flutter plugin.

// Therefore, don’t make the app project depend on the embedding if there are Flutter

// plugins.

// This prevents duplicated classes when using custom build types. That is, a custom build

// type like profile is used, and the plugin and app projects have API dependencies on the

// embedding.

// 如果插件不是applicationVariants类型，即android library，或者项目根目录下.flutter-plugins文件中安卓插件个数为空

if (!isFlutterAppProject() || getPluginList().size() == 0) {

// 给Flutter Plugin的android插件添加编译依赖

// 譬如io.flutter:flutter_embedding_debug:1.0.

addApiDependencies(project, buildType.name,

“io.flutter:flutter_embedding_$flutterBuildMode:$engineVersion”)

}

// 给project添加对应编译依赖

// 譬如io.flutter:arm64_v8a_debug:1.0.0，来自maven仓库

List platforms = getTargetPlatforms().collect()

// Debug mode includes x86 and x64, which are commonly used in emulators.

if (flutterBuildMode == “debug” && !useLocalEngine()) {

platforms.add(“android-x86”)

platforms.add(“android-x64”)

}

platforms.each { platform ->

String arch = PLATFORM_ARCH_MAP[platform].replace(“-”, “_”)

// Add the libflutter.so dependency.

addApiDependencies(project, buildType.name,

“io.flutter:KaTeX parse error: Expected group after '_' at position 7: {arch}_̲flutterBuildMode:$engineVersion”)

}

}

…省略部分…

//接下来再单独分析核心部分：addFlutterTasks方法

6. 接下来我们再看看flutter.gradle的addFlutterTasks方法：

private void addFlutterTasks(Project project) {

if (project.state.failure) {

return

}

…此处省略一堆属性获取与赋值操作…

// 定义 addFlutterDeps 函数，参数variant为标准构建对应的构建类型

def addFlutterDeps = { variant ->

if (shouldSplitPerAbi()) {

//常规操作：如果是构建多个变体apk模式就处理vc问题

variant.outputs.each { output ->

//确保每个APK都有自己唯一的versionCode，这里就是做这个事情的

//具体可以看官方文档 https://developer.android.com/studio/build/configure-apk-splits

def abiVersionCode = ABI_VERSION.get(output.getFilter(OutputFile.ABI))

if (abiVersionCode != null) {

output.versionCodeOverride =

abiVersionCode * 1000 + variant.versionCode

}

}

}

//获取编译类型，variantBuildMode值为debug、profile、release之一

String variantBuildMode = buildModeFor(variant.buildType)

//依据参数生成一个task名字，譬如这里的compileFlutterBuildDebug、compileFlutterBuildProfile、compileFlutterBuildRelease

//参照文章开始最后执行阶段添加的flutter task名字就是在这里确认的

String taskName = toCammelCase([“compile”, FLUTTER_BUILD_PREFIX, variant.name])

// 给当前project创建compileFlutterBuildDebug、compileFlutterBuildProfile、compileFlutterBuildRelease Task

// 实现为FlutterTask，主要用来编译Flutter代码，这个task稍后单独分析

FlutterTask compileTask = project.tasks.create(name: taskName, type: FlutterTask) {

// 各种task属性赋值操作，基本都来自上面的属性获取或者匹配分析

flutterRoot this.flutterRoot

flutterExecutable this.flutterExecutable

buildMode variantBuildMode

localEngine this.localEngine

localEngineSrcPath this.localEngineSrcPath

// 默认dart入口lib/main.dart、可以通过target属性自定义指向

targetPath getFlutterTarget()

verbose isVerbose()

fastStart isFastStart()

fileSystemRoots fileSystemRootsValue

fileSystemScheme fileSystemSchemeValue

trackWidgetCreation trackWidgetCreationValue

targetPlatformValues = targetPlatforms

sourceDir getFlutterSourceDirectory()

// flutter中间产物目录

intermediateDir project.file(“$project.buildDir/${AndroidProject.FD_INTERMEDIATES}/flutter/${variant.name}/”)

extraFrontEndOptions extraFrontEndOptionsValue

extraGenSnapshotOptions extraGenSnapshotOptionsValue

splitDebugInfo splitDebugInfoValue

treeShakeIcons treeShakeIconsOptionsValue

dartObfuscation dartObfuscationValue

dartDefines dartDefinesValue

bundleSkSLPath bundleSkSLPathValue

performanceMeasurementFile performanceMeasurementFileValue

codeSizeDirectory codeSizeDirectoryValue

// 权限相关处理

doLast {

project.exec {

if (Os.isFamily(Os.FAMILY_WINDOWS)) {

commandLine(‘cmd’, ‘/c’, “attrib -r ${assetsDirectory}/* /s”)

} else {

commandLine(‘chmod’, ‘-R’, ‘u+w’, assetsDirectory)

}

}

}

}

// 项目构建中间产物的文件，也就是根目录下build/intermediates/flutter/debug/libs.jar文件

File libJar = project.file(“$project.buildDir/${AndroidProject.FD_INTERMEDIATES}/flutter/${variant.name}/libs.jar”)

// 创建packLibsFlutterBuildProfile、packLibsFlutterBuildDebug、packLibsFlutterBuildRelease任务，主要是产物的复制挪位置操作，作用就是把build/intermediates/flutter/debug/下依据abi生成的app.so通过jar命令打包成build/intermediates/flutter/debug/libs.jar

Task packFlutterAppAotTask = project.tasks.create(name: “packLibs$FLUTTE{R}_{B}UIL{D}_{P}REFIX${variant.name.capitalize()}”, type: Jar) {

// 目标路径为build/intermediates/flutter/debug目录

destinationDir libJar.parentFile

// 文件名为libs.jar

archiveName libJar.name

// 依赖前面定义的compileTask，也就是说，这个task基本作用是产物处理

dependsOn compileTask

// targetPlatforms取值为android-arm、android-arm64、android-x86、android-x64

targetPlatforms.each { targetPlatform ->

// abi取值为armeabi-v7a、arm64-v8a、x86、x86_64

String abi = PLATFORM_ARCH_MAP[targetPlatform]

// 数据来源来自compileTask任务中间产物目录

// 即把build/intermediates/flutter/debug/下依据abi生成的app.so通过jar命令打包成一个build/intermediates/flutter/debug/libs.jar文件

from(“$compileTask.intermediateDir/${abi}”) {

include “*.so”

// Move app.so to lib/<abi>/libapp.so

rename { String filename ->

return “lib/$abi/lib${filename}”

}

}

}

}

// 前面有介绍过addApiDependencies作用，把 packFlutterAppAotTask 产物加到依赖项里面参与编译

// 类似implementation files(‘libs.jar’)，然后里面的so会在项目执行标准mergeDebugNativeLibs task时打包进标准lib目录

addApiDependencies(project, variant.name, project.files {

packFlutterAppAotTask

})

// We build an AAR when this property is defined.

// 当构建有is-plugin属性时则编译aar

boolean isBuildingAar = project.hasProperty(‘is-plugin’)

// In add to app scenarios, a Gradle project contains a :flutter and :app project.

// We know that :flutter is used as a subproject when these tasks exists and we aren’t building an AAR.

// 当是Flutter Module方式，即Flutter以aar作为已存在native安卓项目依赖时才有这些:flutter:模块依赖，否则没有这些task

// 可以参见新建的FlutterModule中.android/include_flutter.groovy中gradle.project(“:flutter”).projectDir实现

Task packageAssets = project.tasks.findByPath(“:flutter:package${variant.name.capitalize()}Assets”)

Task cleanPackageAssets = project.tasks.findByPath(“:flutter:cleanPackage${variant.name.capitalize()}Assets”)

// 判断是否为FlutterModule依赖

boolean isUsedAsSubproject = packageAssets && cleanPackageAssets && !isBuildingAar

// 新建copyFlutterAssetsDebug task，目的就是copy产物，也就是assets归档

// 常规merge中间产物类似，compileTask产物的assets目录在mergeAssets时复制到主包中间产物目录

Task copyFlutterAssetsTask = project.tasks.create(

name: “copyFlutterAssets${variant.name.capitalize()}”,

type: Copy,

) {

dependsOn compileTask

with compileTask.assets

if (isUsedAsSubproject) {

dependsOn packageAssets

dependsOn cleanPackageAssets

into packageAssets.outputDir

return

}

// variant.mergeAssets will be removed at the end of 2019.

def mergeAssets = variant.hasProperty(“mergeAssetsProvider”) ?

variant.mergeAssetsProvider.get() : variant.mergeAssets

dependsOn mergeAssets

dependsOn “clean${mergeAssets.name.capitalize()}”

mergeAssets.mustRunAfter(“clean${mergeAssets.name.capitalize()}”)

into mergeAssets.outputDir

}

if (!isUsedAsSubproject) {

def variantOutput = variant.outputs.first()

def processResources = variantOutput.hasProperty(“processResourcesProvider”) ?

variantOutput.processResourcesProvider.get() : variantOutput.processResources

processResources.dependsOn(copyFlutterAssetsTask)

}

return copyFlutterAssetsTask

}

// 判断是否是applicationVariants

if (isFlutterAppProject()) {

project.android.applicationVariants.all { variant ->

// 获取是assemble task咯

Task assembleTask = getAssembleTask(variant)

if (!shouldConfigureFlutterTask(assembleTask)) {

return

}

//把前面定义的addFlutterDeps函数调用返回的copyFlutterAssetsTask任务拿到作为依赖项

Task copyFlutterAssetsTask = addFlutterDeps(variant)

def variantOutput = variant.outputs.first()

def processResources = variantOutput.hasProperty(“processResourcesProvider”) ?

variantOutput.processResourcesProvider.get() : variantOutput.processResources

processResources.dependsOn(copyFlutterAssetsTask)

// Copy the output APKs into a known location, so flutter run or flutter build apk

// can discover them. By default, this is <app-dir>/build/app/outputs/flutter-apk/<filename>.apk.

//

// The filename consists of app<-abi>?<-flavor-name>?-<build-mode>.apk.

// Where:

// * abi can be armeabi-v7a|arm64-v8a|x86|x86_64 only if the flag split-per-abi is set.

// * flavor-name is the flavor used to build the app in lower case if the assemble task is called.

// * build-mode can be release|debug|profile.

// 执行flutter run或者flutter build apk的产物apk归档处理

variant.outputs.all { output ->

assembleTask.doLast {

// packageApplication became packageApplicationProvider in AGP 3.3.0.

def outputDirectory = variant.hasProperty(“packageApplicationProvider”)

? variant.packageApplicationProvider.get().outputDirectory

variant.packageApplication.outputDirectory

// outputDirectory is a DirectoryProperty in AGP 4.1.

String outputDirectoryStr = outputDirectory.metaClass.respondsTo(outputDirectory, “get”)

? outputDirectory.get()

outputDirectory

String filename = “app”

String abi = output.getFilter(OutputFile.ABI)

if (abi != null && !abi.isEmpty()) {

filename += “-${abi}”

}

if (variant.flavorName != null && !variant.flavorName.isEmpty()) {

filename += “-${variant.flavorName.toLowerCase()}”

}

filename += “-${buildModeFor(variant.buildType)}”

project.copy {

from new File(“$outputDirectoryStr/${output.outputFileName}”)

into new File(“${project.buildDir}/outputs/flutter-apk”);

rename {

return “${filename}.apk”

}

}

}

}

}

configurePlugins()

return

}

// Flutter host module project (Add-to-app).

// 是不是模块源码依赖方式集成到现有项目，参见 https://flutter.cn/docs/development/add-to-app/android/project-setup

// 是的话对模块也做类似一堆处理即可，不再重复分析了，也是 assets 合并

String hostAppProjectName = project.rootProject.hasProperty(‘flutter.hostAppProjectName’) ? project.rootProject.property(‘flutter.hostAppProjectName’) : “app”

Project appProject = project.rootProject.findProject(“😒{hostAppProjectName}”)

assert appProject != null : “Project 😒{hostAppProjectName} doesn’t exist. To custom the host app project name, set org.gradle.project.flutter.hostAppProjectName=<project-name> in gradle.properties.”

// Wait for the host app project configuration.

appProject.afterEvaluate {

assert appProject.android != null

project.android.libraryVariants.all { libraryVariant ->

Task copyFlutterAssetsTask

appProject.android.applicationVariants.all { appProjectVariant ->

Task appAssembleTask = getAssembleTask(appProjectVariant)

if (!shouldConfigureFlutterTask(appAssembleTask)) {

return

}

// Find a compatible application variant in the host app.

//

// For example, consider a host app that defines the following variants:

// | ----------------- | ----------------------------- |

// | Build Variant | Flutter Equivalent Variant |

// | ----------------- | ----------------------------- |

// | freeRelease | relese |

// | freeDebug | debug |

// | freeDevelop | debug |

// | profile | profile |

// | ----------------- | ----------------------------- |

//

// This mapping is based on the following rules:

// 1. If the host app build variant name is profile then the equivalent

// Flutter variant is profile.

// 2. If the host app build variant is debuggable

// (e.g. buildType.debuggable = true), then the equivalent Flutter

// variant is debug.

// 3. Otherwise, the equivalent Flutter variant is release.

String variantBuildMode = buildModeFor(libraryVariant.buildType)

if (buildModeFor(appProjectVariant.buildType) != variantBuildMode) {

return

}

if (copyFlutterAssetsTask == null) {

copyFlutterAssetsTask = addFlutterDeps(libraryVariant)

}

Task mergeAssets = project

.tasks

.findByPath(“:$hostAppProjectName:merge${appProjectVariant.name.capitalize()}Assets”)

assert mergeAssets

mergeAssets.dependsOn(copyFlutterAssetsTask)

}

}

}

configurePlugins()

}

了解configurePlugins源码：

/**

• flutter的依赖都添加在pubspec.yaml中

• 接着都会执行flutter pub get，然后工具会生成跟目录下.flutter-plugins等文件

• 这里做的事情就是帮忙给module自动添加上这些插件dependencies依赖模块

*/

private void configurePlugins() {

if (!buildPluginAsAar()) {

getPluginList().each this.&configurePluginProject

getPluginDependencies().each this.&configurePluginDependencies

return

}

project.repositories {

maven {

url “${getPluginBuildDir()}/outputs/repo”

}

}

getPluginList().each { pluginName, pluginPath ->

configurePluginAar(pluginName, pluginPath, project)

}

}

到这里我们的addFlutterTasks方法以及走完了

7. 接下来我们再看看上文提到的FlutterTask compileTask，这个FlutterTask作甚的

看入口方法：

void buildBundle() {

if (!sourceDir.isDirectory()) {

throw new GradleException(“Invalid Flutter source directory: ${sourceDir}”)

}

//默认以app为例创建build/app/intermediates/flutter目录

intermediateDir.mkdirs()

// Compute the rule name for flutter assemble. To speed up builds that contain

// multiple ABIs, the target name is used to communicate which ones are required

// rather than the TargetPlatform. This allows multiple builds to share the same

// cache.

// 计算flutter assemble的规则名称列表

String[] ruleNames;

if (buildMode == “debug”) {

ruleNames = [“debug_android_application”]

} else {

ruleNames = targetPlatformValues.collect { “android_aot_bundle_KaTeX parse error: Expected group after '_' at position 12: {buildMode}_̲it” }

}

// 重点执行命令

project.exec {

logging.captureStandardError LogLevel.ERROR

// windows的话就是flutter SDK路径下 bin/flutter.bat文件，unix就是bin/flutter

executable flutterExecutable.absolutePath

// 我们app的build.gradle中配置的flutter { source ‘…/…/’ }闭包，路径，也就是项目根目录下

workingDir sourceDir

// 使用本地自己编译的flutter engine才需要的参数

if (localEngine != null) {

args “–local-engine”, localEngine

args “–local-engine-src-path”, localEngineSrcPath

}

// 类似标准gradle构建参数打印控制

if (verbose) {

args “–verbose”

} else {

args “–quiet”

}

// 追加一堆编译参数

args “assemble”

args “–depfile”, “${intermediateDir}/flutter_build.d”

// flutter 编译产物输出路径

args “–output”, “${intermediateDir}”

if (performanceMeasurementFile != null) {

args “–performance-measurement-file=${performanceMeasurementFile}”

}

// Flutter dart程序入口，默认为lib/main.dart

if (!fastStart || buildMode != “debug”) {

args “-dTargetFile=${targetPath}”

} else {

args “-dTargetFile=${Paths.get(flutterRoot.absolutePath, “examples”, “splash”, “lib”, “main.dart”)}”

}

args “-dTargetPlatform=android”

args “-dBuildMode=${buildMode}”

if (trackWidgetCreation != null) {

args “-dTrackWidgetCreation=${trackWidgetCreation}”

}

if (splitDebugInfo != null) {

args “-dSplitDebugInfo=${splitDebugInfo}”

}

if (treeShakeIcons == true) {

args “-dTreeShakeIcons=true”

}

if (dartObfuscation == true) {

args “-dDartObfuscation=true”

}

if (dartDefines != null) {

args “–DartDefines=${dartDefines}”

}

if (bundleSkSLPath != null) {

args “-iBundleSkSLPath=${bundleSkSLPath}”

}

if (codeSizeDirectory != null) {

args “-dCodeSizeDirectory=${codeSizeDirectory}”

}

if (extraGenSnapshotOptions != null) {

args “–ExtraGenSnapshotOptions=${extraGenSnapshotOptions}”

}
自我介绍一下，小编13年上海交大毕业，曾经在小公司待过，也去过华为、OPPO等大厂，18年进入阿里一直到现在。

深知大多数初中级Android工程师，想要提升技能，往往是自己摸索成长或者是报班学习，但对于培训机构动则近万的学费，着实压力不小。自己不成体系的自学效果低效又漫长，而且极易碰到天花板技术停滞不前！

因此收集整理了一份《2024年Android移动开发全套学习资料》，初衷也很简单，就是希望能够帮助到想自学提升又不知道该从何学起的朋友，同时减轻大家的负担。

既有适合小白学习的零基础资料，也有适合3年以上经验的小伙伴深入学习提升的进阶课程，基本涵盖了95%以上Android开发知识点，真正体系化！

由于文件比较大，这里只是将部分目录截图出来，每个节点里面都包含大厂面经、学习笔记、源码讲义、实战项目、讲解视频，并且会持续更新！

如果你觉得这些内容对你有帮助，可以扫码获取！！（备注：Android）

总结

最后为了帮助大家深刻理解Android相关知识点的原理以及面试相关知识，这里放上相关的我搜集整理的24套腾讯、字节跳动、阿里、百度2019-2021面试真题解析，我把技术点整理成了视频和PDF（实际上比预期多花了不少精力），包知识脉络 + 诸多细节。

还有 高级架构技术进阶脑图、Android开发面试专题资料 帮助大家学习提升进阶，也节省大家在网上搜索资料的时间来学习，也可以分享给身边好友一起学习。

网上学习 Android的资料一大堆，但如果学到的知识不成体系，遇到问题时只是浅尝辄止，不再深入研究，那么很难做到真正的技术提升。希望这份系统化的技术体系对大家有一个方向参考。

2021年虽然路途坎坷，都在说Android要没落，但是，不要慌，做自己的计划，学自己的习，竞争无处不在，每个行业都是如此。相信自己，没有做不到的，只有想不到的。祝大家2021年万事大吉。

《互联网大厂面试真题解析、进阶开发核心学习笔记、全套讲解视频、实战项目源码讲义》点击传送门即可获取！

(img-IHqCnHCA-1713680723377)]

[外链图片转存中…(img-uE4XP05C-1713680723378)]

[外链图片转存中…(img-aaVHlQS3-1713680723378)]

[外链图片转存中…(img-mCouZ1SZ-1713680723379)]

既有适合小白学习的零基础资料，也有适合3年以上经验的小伙伴深入学习提升的进阶课程，基本涵盖了95%以上Android开发知识点，真正体系化！

由于文件比较大，这里只是将部分目录截图出来，每个节点里面都包含大厂面经、学习笔记、源码讲义、实战项目、讲解视频，并且会持续更新！

如果你觉得这些内容对你有帮助，可以扫码获取！！（备注：Android）

总结

最后为了帮助大家深刻理解Android相关知识点的原理以及面试相关知识，这里放上相关的我搜集整理的24套腾讯、字节跳动、阿里、百度2019-2021面试真题解析，我把技术点整理成了视频和PDF（实际上比预期多花了不少精力），包知识脉络 + 诸多细节。

还有 高级架构技术进阶脑图、Android开发面试专题资料 帮助大家学习提升进阶，也节省大家在网上搜索资料的时间来学习，也可以分享给身边好友一起学习。

[外链图片转存中…(img-spiC4OO1-1713680723380)]

[外链图片转存中…(img-vMtGrtXu-1713680723382)]

[外链图片转存中…(img-mgD4xPjJ-1713680723383)]

网上学习 Android的资料一大堆，但如果学到的知识不成体系，遇到问题时只是浅尝辄止，不再深入研究，那么很难做到真正的技术提升。希望这份系统化的技术体系对大家有一个方向参考。

2021年虽然路途坎坷，都在说Android要没落，但是，不要慌，做自己的计划，学自己的习，竞争无处不在，每个行业都是如此。相信自己，没有做不到的，只有想不到的。祝大家2021年万事大吉。

《互联网大厂面试真题解析、进阶开发核心学习笔记、全套讲解视频、实战项目源码讲义》点击传送门即可获取！