Cheer you up! It is most important to learn Java well. If you are familiar with all aspects of Java, including syntax, tool chains, JVM, etc., it is only a matter of time before you become familiar with Android development.
The basic knowledge of Android is too detailed, so here are some commonly used libraries:
Basic Android skills: Java knowledge, Four major components of Android (activity life cycle...), Use of various Views (Listview...), Network requests (HttpURLConnection...), Local storage ( sharedpreference, SQLite...)
Commonly used frameworks: Network (OkHttp) Image loading (Glide, Imageloader) There are many android searches on github, you can use whatever you need
Can’t sum it up. I came here gradually. It is recommended to use php/nodejs/py or something like php/nodejs/py to write the backend of a simple app. It is simple after all. Java web is a bit tricky
In terms of Android, in addition to the four basic Android contents, also need the following content: Various types of network development (retrofit, okhttp) Various types of view customization Simple SQLite operations (simple Apps can directly use leancloud and the like) Storage cloud, no need to write backend)
However, none of this is critical, the key is: What needs do you want to achieve.
Demands determine what technology development is used in the project, and requirements determine what content you need to learn. Everything is based on demand. Without real demand, it is basically nonsense.
So: First think about what type of project you want to do and what specific needs you need.
These things are difficult to summarize systematically, but in short, just do it. Learning itself is a process of constantly stepping on pitfalls and climbing up pitfalls. After doing a few shitty works, you will know what to do. In terms of skills, you must at least be able to understand Java syntax, several life cycles of activities, fragments, and some new controls of materialDesign (this is very important, at least it can make your application not look so low). The more important thing is to write more.
Cheer you up!
It is most important to learn Java well. If you are familiar with all aspects of Java, including syntax, tool chains, JVM, etc., it is only a matter of time before you become familiar with Android development.
The basic knowledge of Android is too detailed, so here are some commonly used libraries:
ButterKnife, AndroidAnnotations
Retrofit
Fresco
greenDAO 3.x
Dagger2
RxJava, RxAndroid
Basic Android skills:
Java knowledge,
Four major components of Android (activity life cycle...),
Use of various Views (Listview...),
Network requests (HttpURLConnection...),
Local storage ( sharedpreference, SQLite...)
Commonly used frameworks:
Network (OkHttp)
Image loading (Glide, Imageloader)
There are many android searches on github, you can use whatever you need
I can’t think of so much for now
Can’t sum it up.
I came here gradually.
It is recommended to use php/nodejs/py or something like php/nodejs/py to write the backend of a simple app. It is simple after all. Java web is a bit tricky
In terms of Android, in addition to the four basic Android contents,
also need the following content:
Various types of network development (retrofit, okhttp)
Various types of view customization
Simple SQLite operations (simple Apps can directly use leancloud and the like) Storage cloud, no need to write backend)
However, none of this is critical, the key is: What needs do you want to achieve.
Demands determine what technology development is used in the project, and requirements determine what content you need to learn.
Everything is based on demand. Without real demand, it is basically nonsense.
So:
First think about what type of project you want to do and what specific needs you need.
These things are difficult to summarize systematically, but in short, just do it.
Learning itself is a process of constantly stepping on pitfalls and climbing up pitfalls. After doing a few shitty works, you will know what to do.
In terms of skills, you must at least be able to understand Java syntax, several life cycles of activities, fragments, and some new controls of materialDesign (this is very important, at least it can make your application not look so low).
The more important thing is to write more.
You can refer to the blog http://blog.csdn.net/github_3...
Be diligent and studious. At least you must have the ability to keep learning. This principle is the most basic for any development.
Let a little add up and explore slowly