A long line of--android will go to the study summary

A long line of--android will go to the study summary

I graduated from 14, and I was wondering when did I start Android development? Is sophomore next semester, at that time with the elder's buttocks behind rub a software design competition. At that time, we chose the Android development. I think it's the middle of 12. I belong to the very ordinary type of school, the enlightened is also late. That summer, I intermittent to see the marks video, that will also use paper and pen to watch the video while taking notes, that is the pursuit of the use of the pursuit is not to grasp the number of notes, to read a few episodes of video (there is no feeling very naïve). At that time to the future is also ignorant curiosity, inner is also a conflict and anxious.

Later to learn Java, and then learn software engineering, there are relatively large coding after-class homework. Remember the spring rain doctor just start a business, feel the spring Rain doctor's model is very good, he tried to achieve a set of procedures (Doctor version + Patient edition Java EE background +android version of the app), at that time back to a fashionable name called "Health assistant". Of course, this code is certainly not comparable to industrial-grade code, just to achieve a simple landing, search, add, query function, patients can ask questions in the app, the doctor can answer questions on the web. Did not think, oneself later also entered a mobile medical internet company, feel because really is very wonderful things, once, we do a lot of seemingly unrelated things, who have to know, the future you look back, a lot of things are strung up.

Recall so much, in fact, the main is to do some of the previous Android development ideas to abstract, do a summary. Convenient to look over later.

Android App Architecture

At the beginning of the year, I was in the collection of some open-source apps or frameworks, read the learning source, also wrote a set of Android application framework, of course, some features are not implemented. And I am also planning to write a series of "If I am an architect", write what I have learned in Android application architecture. The visual is going to fare evasion.

Frame Address:

Https://github.com/zhujainxipan/FYForAndroid

What features are generally implemented:

Introduction of support for MVP in the base class

Base class Abstraction:
The design of Baseapplication
The design of Basefragment
The design of baseactivity

Network Base layer:
Picture loading frame Universal Imageloader two-time package
Network request framework Volley two times package (integrated Gson)

Data layer:
Cache Management
Sharepreference Package

Common Component Encapsulation:
Partial third-party controls, such as filtering common components
WebView Component Encapsulation

Tool class:
Common tool Classes

The writing frame brings me thinking

The framework is designed to increase reuse, facilitate project maintenance, unify project development styles, reduce complexity, and improve efficiency.
In fact, whether it is the development of Android applications, or the development of the web behind the scenes are everywhere. In fact, at the conceptual level, they are almost entirely correspondence, knowledge can be linked. The existence of frameworks can help us develop quickly, and frameworks often provide well-packaged tool classes or base classes, or, on third-party integrations, ensure lower coupling with the system, facilitating future replacement of third parties.
If you have the opportunity to do backstage development in the future, in fact, you can do the idea of Android application to understand the framework of Java background, on the ground floor, they can correspond. However, one of the big challenges in thinking is that the service side has a higher demand for network knowledge. This may be the short board for the client.

Android Knowledge Tree

The client is more developed than the user interaction, and is roughly divided into:
Interface rendering Related
Views view, activity, fragment, etc.

User interaction
Click, gesture, sensor, etc.

Network calls
Network request, push, poll, data transfer format selection (JSON, XML, etc.)

Store
Database storage, file storage, cache system, etc.

Processes, Threads
Multimedia related

Common Android Database Solutions and principles

Android commonly used several ORM framework: Ormlite, Greendao, Ormndroid, Androrm, and so on, is intended to study the underlying principle, but suffering from no time, visual also want to fare evasion.

Android Plugin

Plug-in this piece of oneself has been a heart to study, colleague also shared, oneself also saw some intermittently. Originally intended to write several blog, but for some reason oneself again fare evasion.

Analysis of the framework layer

The framework of the 7 chapters of the "Android kernel Anatomy", but also originally intended to write several blogs, but for some reasons themselves again fare evasion.

http://www.woaipu.com/shops/zuzhuan/61406
Http://www.znds.com/tv-967956-1-1.html
Http://www.znds.com/tv-967958-1-1.html

http://www.woaipu.com/shops/zuzhuan/61406
Http://www.znds.com/tv-967956-1-1.html
Http://www.znds.com/tv-967958-1-1.html

A long line of--android will go to the study summary