惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

人人都是产品经理
人人都是产品经理
宝玉的分享
宝玉的分享
小众软件
小众软件
有赞技术团队
有赞技术团队
月光博客
月光博客
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
MyScale Blog
MyScale Blog
Engineering at Meta
Engineering at Meta
Stack Overflow Blog
Stack Overflow Blog
H
Hackread – Cybersecurity News, Data Breaches, AI and More
N
Netflix TechBlog - Medium
D
Docker
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
MongoDB | Blog
MongoDB | Blog
WordPress大学
WordPress大学
J
Java Code Geeks
罗磊的独立博客
V
Visual Studio Blog
雷峰网
雷峰网
H
Help Net Security
T
The Blog of Author Tim Ferriss
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
大猫的无限游戏
大猫的无限游戏
F
Fortinet All Blogs

博客园 - 包建强

MindSpore开源项目分类(截止到2024.2.3) 开源自己编写的半人工标注平台PaddleOCRLabel(.NET Winform版本) Appium自动化测试框架研究(2)——搭建IOS环境 2019,我在几个新的技术领域的尝试和心得 Flutter中高级培训 1.9 From Native to HTML5 1.8 Double-Opening and Virtual Machine 1.7 All components require plug-in? 1.6 Why only in China? 1.5 A better alternative thing: React Native 1.4 The usage of plug-in 1.3 History of Android Plug-in Programing 1.2 Why need pluggable? 1.1 What is the plug-in? Chapter 8 The Simplest Plug-in Solution Chapter 7 Resources in Plug-In(1) Android插件化的兼容性(下):突破Android P中灰黑名单的限制 Android插件化的兼容性(中):Android P的适配 Android插件化的兼容性(上):Android O的适配
Chapter 1: Plug-in programing from past to the future
包建强 · 2018-08-28 · via 博客园 - 包建强

      It is the best time. Although the internal API of Android not allowed to be modified by google play, but in China, we download App in the domestic markets, and Google Play is rarely used. The major application markets are allow this. Therefore, each major companies of domestic internet industry has their own plug-in frameworks. With this open environment, we can do many things with Android plug-in framework.

     It is the worst time. With the popularity of plug-in technology in China, for the interviews with major internet companies, plug-in technology will be general topic to be asked about. It is difficult for the Android developers not to be familiar with ‘reflection’ and ‘newProxyInstance’, but to master the principles of ‘ClassLoader’ and ‘Resources’.

     1.1 What is the plug-in?

     1.2 Why need pluggable?

     1.3 History of Android Plug-in Programing

     1.4 The usage of plug-in

     1.5 A better alternative thing: React Native

     1.6 Why only in China?

     1.7 All components require plug-in?

     1.8 Double-Opening and Virtual Machine

     1.9 From Native to HTML5  

Summary

     In this chapter, we review the history of Android plug-in technology which is basically divided into two parts, static agents and dynamic replacement. All plug-in frameworks are based on them. After the history review, you will find that plug-in technology is not accomplished at one stroke, and it has also experienced a process of gradual improvement from scratch.

     Plug-in technology is not only used to fix bugs and dynamically release new features. In the process of researching plug-in technology, we have developed the Android virtual machine and double-opening technology. This is a new technology area that can get rid of the Android native system limitation, and run the app more faster.

     React Native is also mentioned, which also fixes bugs and dynamically releases new features, similar to Android plug-in technology. Which technology to be selected depends on whether the R&D team is based on H5 or Android, and depends on whether it will released to Google Play.