What's happening in the Android environment

Don't say Android studio's interface looks better than eclipse, but I chose Eclipse. Many of the tutorials we've seen about Android development are based on the directory structure under Eclipse, and for the first time in this area, the directory structure of Android Studio is somewhat confusing at the beginner stage. Classic is always classic. It's not too late to change when we're familiar with it, after all, Android studio is pretty eye-pleasing.

Talk about the environment to build it, the specific process I will not repeat. A few complaints: one is Google moved out of the celestial Android after most of the API from the official website is down, so in the beginning of the time is not less than the computer, the site is the wall is what do not do what, urgent what does not come. So the SDK words or people looking for similar, perhaps others have, or have the conditions to buy a VPN bar, since to learn this thing, Google's things are not FQ is really inconvenient. Two is run as, not recommended with their own simulator, x86 notebook architecture to simulate the Android environment of ARM architecture, do not know how people feel, I am feeling suppressed. So the best, either with the real machine to tune, or with an independent Android simulator to tune, I use the night God Simulator, not bad, comparable to the real machine, of course, this kind of online simulator a lot of search, yours faithfully choose it yourself.

The most important point, Java to understand, not necessarily say how much Java to master, but at least even if it is watching video tutorials or reading, we can feel not to listen to the heavenly book on the line. Programming this thing, but also depends on knocking, knocking in the study will not be targeted, learned to go on knocking. Do not think of their own Java to learn about the first to get started, the light to see whether or not to practice the end or not, do not think Java Foundation is not enough to retreat, all a shoulder to carry a head who fear who. In fact, the most important thing is to insist, just at the beginning will be all kinds of burn, teeth passed on steady, personal advice or to set an idea, such as want to do what kind of app, day and night to learn, do, do the process is the process of learning, so there are goals, the goal is you insist on the power. Of course, can not be impatient, first get started to understand the development mechanism (dozen good piles), at least to get started with a little bit of your app, will not learn to check, completed also learned.

My personal learning route is summed up like this: Get started----"complete app--in the simplest way" from the perspective of design mode to optimize the architecture--------the optimization by some mainstream framework

Summarize some of the issues you want to solve for your app: 1, code optimization for design pattern angle 2, domain recognition algorithm implementation 3, node. js for engine acceleration in content search 4, distributed storage, and optimization of storage policies (index Establishment) 5, the interface frame to beautify it

What's happening in the Android environment