Android learning plan

I have read some materials about Android Application Development in the last two weeks, mainly on the official website and a book on the android kernel. Because the market opportunities for Android are not stable yet, there are many opportunities, but we need to learn and adapt as soon as possible. The official materials are rich and authoritative. I don't plan to buy an Android Application book. If it is a kernel, I think it is necessary to have a Linux Foundation first, but I have never seen the Linux kernel. At this point in time, it seems that time is wrong to learn the Linux kernel, because it is difficult to calm down and focus on a new underlying technology without worrying about market changes; but application technology is still passionate about learning.

In order to have a plan for myself and facilitate supervision, I plan to write down what I learned. I have always felt that this method can make my mind more concentrated, more efficient, and more in-depth in learning. If some netizens come to communicate with each other, they will be more profound.

Http://developer.android.com/training/index.html here is the official website, I have been studying for two weeks, but the time can not be guaranteed, to go to work busy, sometimes go home and other things to deal. Now we need to make a plan to ensure the time is good.

Monday, Wednesday, Friday, every night for 2-3 hours;

Tuesday, Thursday, 1-2 hours a day;

Saturday, 7-8 hours

Sunday, 3-4 hours

In this way, there will be 18-25 hours in a week, and learning results are needed. At present, we will first examine the articles with examples of our own practice.

The document structure cannot be translated solely from the official website theory. You need to add your own practical results, including implementation differences in some details. I learned half of the gettingstarted chapter, roughly browsed the summary of the content of all chapters, analyzed and focused on division, because people have limited energy, we need to put limited effort in the most important places.

Getting started

Here is the basic development environment setup, the construction of the first application, and some necessary framework Introduction: the lifecycle of management activities, support for different hardware devices, use fragments to build a dynamic user interface, save data, interact with other applications, share data, and other basic content. The priority is high, the importance is high, and the complexity is medium.

Building apps with multimedia

Multimedia includes audio input and output, and controls the camera to obtain image and video information. In my opinion, sound must be learned and processed, but there is no need to study in depth; camera control is rarely used. The priority is low, the importance is medium, and the complexity is low.

Building apps with graphics & Animation

Graphics and animation are essential for mastering content, a good app, and graphic interfaces, especially for games. High priority, high importance, and high complexity.

Building apps with connectivity & the cloud

Including wireless connections and network operations, which are relatively independent and are background content. The priority is medium. If network connection is required, the priority is high and the complexity is high.

Building apps with user info & location

Including accessing local data, managing users, and obtaining local data. The priority is high and the importance is high. In general cases, this type of module is limited to local API calls and data management. It is not difficult and the complexity is low.

Best practices for User Experience & UI

After reading the content list, it is related to some basic local operation interface behaviors. There are a lot of content, but they are all very important, the knowledge in this chapter is required for the main part of communication with users. The priority is high, the importance is high, and the complexity is high.

Best practices for user input

For user input, the plan I imagined is rarely used for the time being. From my perspective, it will not take the most part. The priority is low, the importance is medium, and the complexity is low.

Best practices for performance

This includes some techniques for improving the running performance and some in-depth content. For me, I will not focus on this entry level. In the future, I need to study the performance improvement topic. The priority is low, the importance is high, and the complexity is high.

Best practices for Security & privacy

Security-related content requires some underlying knowledge and rich experience. At present, we will continue to learn it later. The priority is low, the importance is medium, and the complexity is high.

Using Google Play to distrize & monetize

After the product development is completed, it is not a concern for beginners. The priority is low, the importance is medium, and the complexity is medium.

The above are all the preliminary judgments I made when I learned Android development only for two weeks. I will learn further insights and make progress.

Of course, getting started ---- building apps with graphics & animation ---- building apps with user info & location ---- best practices for User Experience & UI.

Well, at present, the Getting Started content is completed first. You can check whether two or three learning articles can be written in one week. This article is regarded as the start log.