Android app architecture design 01, androidapp

Android app architecture design 01, androidapp
1: This article has been excerpted,

12345

-Consistency of requirements, designs, and codes during development-the entire program has a uniform style, such as a dialog box style, button style, tone, and other UI elements-the specific and unified structure of the entire program, for example, when different modules access the network, their calling methods are the same. For example, asynchronous access uses callback to notify the results. The same functions should be extracted into common modules. -Developers can execute the intent of the requirement personnel and the designer well. -Complete documents, Requirement documents, design documents, test documents, and process documents are provided.

2:

How to maintain conceptual integrity

2345

-The system guarantees that the product owner must establish an absolute technical authority-the technical owner (SE, SL) must strictly implement the project requirements and design, must go deep into coding details-maintain continuous communication with all personnel at different stages and encourage developers to give comments. -Involve developers in the design, but do not decide the design.-reuse modules through continuous feedback and communication.

3: during the development process, we must ensure the consistency of some of the unified resource font colors,

2345

-The system guarantees that the product owner must establish an absolute technical authority-the technical owner (SE, SL) must strictly implement the project requirements and design, must go deep into coding details-maintain continuous communication with all personnel at different stages and encourage developers to give comments. -Involve developers in the design, but do not decide the design.-reuse modules through continuous feedback and communication.

What are the ideas and principles of Android architecture design?

Rlei analyzes the Android Design Philosophy:
After understanding Intent, you can understand the Android philosophy (all applications are equal. For a simple example, apps in iOS need to be implemented by themselves to integrate SNS, such as facebook, twitter, and sina weibo (iOS5 only integrates twitter ); on Android, you only need to broadcast a share content intent. Starting from understanding how Intent works, you can understand how Activity Manager, Package Manager, and Services are important Android components.
In addition, the Binder is a core component of the Android architecture. Android's Intent-based message transmission is decoupled from components/applications. The following basic information is Binder IPC. In this regard, Android is actually a glorious part of the failure to carry forward BeOS and Palm OS 6 (sadly reminded os6.
MVC (Content Provider, Activity, Layout, Adapters) is relatively basic and is not unique to Android.
The abstract of data access by the Content Provider is also interesting. Ideally, the content provider allows the client to access data in a semantic manner using Uris (URIs themselves represent data hierarchies and query conditions ), the structure of the following database table can be changed without affecting the client code. Of course, content provider will be exposed to SQL implementation details by a variety of complex where clauses.
As for Android permission management, it is actually relatively simple. It mainly uses the ready-made Linux security model to isolate processes from each other. API-level permission management is similar to JVM.
Billy Cui focuses on the design of the permission system:
Android permission system is based on Linux, but many control modules are added.
In general, the permission system is divided into the following parts:
1. userid: inherited from linux. For Multiple apps, you can use the same userid through shareuid, which is mainly responsible for directory access permissions, for example, a private directory can only be accessed by the same uid application.
2. installation level: system level or app level, which is determined based on the application installation location. The application installed under system/app is system level, you can obtain more permissions, such as the permission to silently install the application.
3. permission: This is the most important permission control. Generally, developers are mainly engaged in developing applications. the use-permission declared in xml determines whether it has access permissions when accessing the corresponding api or resource, such as the commonly used android. permission. INTERNET.
4. signature: signature is an important part of the Android permission system. For system signature applications, there are some special functions, and shareuid and other features also require the same signature as the basis. In addition, permission often uses signatures when setting/customizing their permissions. For example, only my own applications can access my own public APIs.
In addition, Android has set uid with special features in the uid, such as system/media, which will be used when configuring system-level services.
Dong zhaohui believes that Android is mainly based on the idea of component collocation:
Speaking of the design ideas and principles of the Android architecture, I understand that components are mainly used together. In the user's opinion, all modules or components can be reused and simplified ...... remaining full text>

Android mobile app development process?

First, you need to understand the android app development languages (java, c ++). Second, I saw some steps about app software development on the kickoff Network: 1. application planning, 2: architecture design, 3: interface design, 4: data operation and storage, 5: Business implementation, 6: page Jump. Of course, this is just a simple summary. If you want to know more details, you have to find resources online. Comments in July: Like! Awesome! Awesome! I never liked it!