[Phase 1 outpatient highlights] accurate and efficient Android Application Development

The technical clinic is a BKJIA Community brand topic. A visiting expert is invited every week to answer questions from technical netizens. From popular technologies to cutting-edge knowledge, from technical Q & A to career planning. One topic for each issue, leading the latest and most popular technology!

This special invitationHan Chao, author of Android classic application developmentTo answer questions about Android Application Development. You are welcome to ask questions and discuss them with experts!

650) this. width = 650; "border =" 0 "alt =" "src =" http://www.bkjia.com/uploads/allimg/131228/0U05R503-0.jpg "/>

View the highlights of this outpatient record:Http://doctor.51cto.com/develop-255.html

Participate in the latest technical clinic:OSSIM, a powerful tool for Enterprise Information Security Management

Featured questions and answers from current users for your reference.

Q: Hello, Miss Han! I am a JAVA program developer with ten years of experience. Due to work needs to transform Android system development, I am a beginner at the learning stage. I feel that it is still very difficult to build a profound C language. How can skilled programmers like me turn to mobile development as soon as possible? What are my advantages in transformation? What improvements are needed? What technical breakthroughs do we need? Please do not give answers!
A:Your problem is typical.
First, your language base must be advantageous. Android classic application development is suitable for reading by people without any language barriers.
Second, if you are a Java SE engineer, the Android UI design concept is very similar to AWT, especially in the control and layout organization.
Third, the Android graphics system is quite special. It consists of 2D, 3D, and printable content. This is the original content of the drawing. As described in Chapter 5 of Android classic application development.
Fourth, to transfer data to mobile development, you need to understand the differences between embedded systems and desktops. Android automatically adapts to the features of various small screens, which you need to pay attention to when using the UI.
Fifth, the biggest breakthrough in technology is to turn to system development through Android application development.

Q: Hello, Miss Han. I have not been familiar with android for a long time, but I think android programming is similar to linux programming, is it better to master linux programming first?
A:If you want to develop Android applications, you do not need the Linux technology for the moment. Just learn the Java programming technology. If you want to develop the Android system and focus on the underlying layer, Linux is the local version and Android is the final version.

Q: Hello, Miss Han. Learning about android is just a short time. According to the current situation, android has been on fire for about three years! It will slow down later -- in the long run, which of the following aspects is more suitable for J2ee and android?
A:First, I will not estimate the future trend of technology. I think your estimation is not about the technology itself, but about the content that technology brings to the individual. Second, do not put all chips on one technology. IT is developing rapidly and transformation is the only way for every engineer. Java EE is used on the server side, and Android is used for embedded systems. The two have different application fields. Third, for Java EE Note: J2ee is the old name) for Java system development, it should not be considered that Java EE is higher than Java SE, and Java SE is higher than Java ME, they are the applications of Java in different fields, and there is no difference in technology itself. Engineers who are engaged in JavaEE but only do configuration work are also very elementary. Java SE is the key foundation. To become a well-known engineer, you must never bypass Java SE to directly access Java EE. Java SE programming technology, the class library is similar to Android), there are some special technologies, such as JMX, JAXP, IDL, RMI and so on. Java EE itself is an "increment" of Java SE, focusing on CS architecture, business layer, Bean, etc. The actual Java EE development should be based on Java SE. Of course, some people are indeed away from implementation and talk about Java's architecture and concepts. I personally think This is not the correct method.

Q: Hello, teacher. I have found that more and more people are entering android. Just like java, there are more and more people. Various training courses also began to train android. Therefore, I think that development at the android ui or application layer may fall into the same situation as that of java developers. I would like to ask the teacher how to avoid such a dilemma? What knowledge should we learn to strengthen ourselves? I have seen many teachers recommend android system development or porting. If you choose system-level development and transplantation, you think it would be better to select the specific one, because after all, one person has limited energy, and we should also have specialized skills.
A:Hello, the problem you encountered is a common problem. Let me explain the following in sequence:
First, it can be clearly stated that the incorrect view of "downgrading java developers" is actually "downgrading java developers". The Java system is profound and profound. Besides Java SE, there are also Java ME, java EE and JavaFX involve all aspects of your computer and the network you are using because of the rapid development and training in China, many low-end engineers of Java ME mobile development have developed their technologies for a short term, with a low technical background. As a result, Java ME development is relatively simple in Java systems, their decline is inevitable. This does not mean that Java technology has fallen. If you want to know about Java, you are advised to go to the official website in English.
Second, the "android ui or application-layer development" section is more difficult than Java ME mobile development. However, this section is not too difficult, the content involved in Android classic application development is inevitable. You have learned this kind of application development from the UI Layer, and you will have some transformation directions: "atypical applications" and "system-level applications ", "System Customization ".
Third, regarding "system-level development and transplantation", this is a very promising aspect of development. My other two books, "Android system principles and application development" and "Android system-level in-depth development-transplantation and debugging" are system level. You can refer to the following points:
[*] If you do not carefully lay the Linux foundation, you do not need to think about this part.
[*] If you are familiar with the development of Linux user space, it is easier to develop the Android framework.
[*] If you are more familiar with Linux driver development, it is easier to port Android

Q: follow these questions:
1. Is there any other good method for Android to adapt to the screen except to create multiple Layout sets?
2. How can I develop Android without the underlying development or application development?
3. Is there any development space for Android in the commercialization of commercial application software?
4. How can I quickly transfer to Android for development on other mobile platforms?
A:1. A Layout can be adaptive or arranged and combined. For details, see 3.2 and 7.5 in Android classic application development.
2. there is a future, but you must note that only application development is the foundation for developing typical applications, you can transition to atypical reference development. I will introduce it in other books later.
3. There is no clear prospect yet, and there may be some development in tablet tablets.
4. It depends on your platform. If it is a Java ME application, it is easy to transfer to the Android Application for Android underlying development. It must start from Linux, my previous books "Android system principles and application development" and "Android system in-depth development-porting and debugging" have been emphasized many times.