Thinking about the android framework
My framework is to divide android into three modules: 1, core; 2, sys
The core layer contains common processing, sending email, http, cache, log, netstate, sensor, sms, utils, etc.
The sys layer is divided into activity interaction layer, helper assistant layer, service layer, widget layer, adapter layer, data bean layer, constants layer, etc.
Thinking about android service module
Personally, android services can be divided into the following categories: 1. Database query for functional modules; 2. A series of processing for functional modules after actively obtaining data from the Internet; 3. For passively obtaining data from the Internet kind of processing (push data)
So if they are unified, simple, and can be linked with activity to achieve hierarchical management of code, instead of using aysnctask to integrate code and logic processing, what should we do?
Thinking about android native service and java service
Native service is the service of the android system itself. As an application developer, learning it will certainly make you more familiar with the android system, but what is the benefit to you? Can I define the native service by myself, and then call the .so file through it? How is the .so file of Baidu Map called?