Whose life is being destroyed by the registration of mini programs and APPs?

Starting next year, domestic apps will also need to be registered like websites. I think everyone has already heard about this news that has swept the screen, and by the way, so has the mini program.
insert image description here

In the context of increasingly strengthened management, developers will also face some new difficulties and changes.

The introduction of this filing policy seems to be on the premise of maintaining information security and compliance operations, but in fact it brings a series of challenges to small companies and independent developers.

Not only will it prolong the application development cycle, it may also further intensify market monopoly.

Large companies can more easily respond to policy requirements because they have huge resources and professional teams. However, small companies and independent developers lack professional legal support and may be forced to exit because they have difficulty meeting the filing requirements and miss the best time to go online. market.

This will cause the living space of small companies and independent developers to be squeezed, and then a large number of developers will lose their jobs.

Everyone knows that Android application developers have become saturated. If programmers from small companies and independent developers want to avoid being eliminated, the direction of development is nothing more than to advance to intermediate and advanced Android development, or to go deep into the underlying logic of Android and turn to system development.

No matter which path you choose, you can't do without learning the Framework.

Because Framework belongs to the framework part of the Android system and provides API interface services for app development, so if you often do app development, you definitely can't just stay at the level of simply calling the API, but you should have a deep understanding of the principles of the API.

Moreover, learning Framework can also form your own technical barriers, which is of great benefit for moving to framework layer development, vehicle development, multimedia development, and reverse security development.

insert image description here

How to learn Framework correctly?

For those who have been developing Android applications for many years, the underlying implementation is huge and complex, and it is difficult to understand the knowledge points in depth without reading the source code carefully.

In order to help everyone solve this problem, here we have compiled the knowledge points and learning routes about the underlying development technology of Android Framework! And integrated it into a PDF document " Android Framework Source Code Development Revealed ". [Friends in need, scroll to the end of the article to get it! ! !

This document combines code examples to explain each knowledge point in detail, which can not only consolidate the core technical points of the underlying principles, but also master the architectural design methodology that is difficult for ordinary developers to access. Then you will have core competitiveness that is difficult to copy by your peers at work, in a team, and during interviews.

I hope everyone can study according to the Android Framework learning roadmap of the system below, so that the knowledge system established is strong enough!
insert image description here

The document content is shown below:

Chapter 1 System Startup Process Analysis

  • Section 1 Android Startup Overview
  • Section 2 init.rc analysis
  • Section 3 Zygote
  • Section 4 Interview Questions
    insert image description here

Chapter 2 Cross-process Communication IPC Analysis

  • The first section Service can be understood this way
  • Section 2 Binder Basics
  • Section 3 Binder Application
  • Section 4 AIDL Application (Part 1)
  • Section 5 AIDL Application (Part 2)
  • Section 6 Messenger Principles and Applications
  • Section 7 Server Callback
  • Section 8 Obtaining Services (IBinder)
  • Section 9 Full Analysis of Binder Interview Questionsinsert image description here

Chapter 3 Handler source code analysis

  • Section 1 Source Code Analysis
  • Section 2 Difficult Questions
  • Section 3 Handler frequently asked interview questionsinsert image description here

Chapter 4 AMS source code analysis

  • Section 1 Introduction
  • Section 2 Android Architecture
  • Section 3 Communication Methods
  • Section 4 System Startup Series
  • Section 5 AMS
  • Section 6 Analysis of AMS Interview Questionsinsert image description here

Chapter 5 WMS source code analysis

  • Section 1 WMS and activity startup process
  • Section 2 WMS Drawing Principle
  • Section 3 WMS roles and instantiation process
  • Section 4 Working Principle of WMSinsert image description here

Chapter 6 Surface Source Code Analysis

  • Section 1 Creation Process and Software and Hardware Drawing
  • Section 2 Double Buffering and Surface View Analysis
  • Section 3 Overview of Android Graphics Systeminsert image description here

Chapter 7 SurfaceFlinger source code analysis based on Android12.0

  • Section 1 Application Establishes a Communication Bridge with SurfaceFlinger
  • Section 2 SurfaceFlinger startup and message queue processing mechanism
  • Section 3 SurfaceFlinger-VSyns (Part 1)
  • Section 4 SurfaceFlinger-VSyns (middle)
  • Section 5 SurfaceFlinger-VSyns (Part 2)insert image description here

Chapter 8 PKMS source code analysis

  • Section 1 PKMS calling method
  • Section 2 PKMS startup process analysis
  • Section 3 APK Scanning
  • Section 4 APK installation
  • Section 5 PKMS Permission Scanning
  • Section 6 Silent Installation
  • Section 7 requestPermissions source code process analysis
  • Section 8 PKMS interview questionsinsert image description here

Chapter 9 InputManagerService source code analysis

  • Section 1 Android Input input event processing process (1)
  • Section 2 Android Input event processing process (2)
  • Section 3 Android Input event processing process (3)insert image description here

Chapter 10 DisplayManagerService source code analysis

  • Section 1 DisplayManagerService Startup
  • Section 2 Creation of DisplayAdepter and DisplayDevice
  • Section 3 DMS partial on-off screen process
  • Section 4 Brightness Adjustment
  • Section 5 Proximity Sensor Screen Off Principle
  • Section 6 Updates to Logical Display and Physical Display configurationsinsert image description here

at last

Learn your true strength. This means that we need to invest more time and energy in learning and mastering skills, not just to cope with immediate challenges, but also with the goal of long-term growth. Only by truly mastering excellent skills can we stand out in the fierce competition and embrace broader development opportunities.

If you need Framework learning materials, scan the QR code below to get them for free! ! !

Guess you like

Origin blog.csdn.net/datian1234/article/details/132742675