What pitfalls need to be paid attention to in Android development?

1. The imported class library needs to be in the same directory as the project, so as to avoid conflicts between the resource file and the class library.

2TextViewSetText is int, the TextView's color** is set, and the set getTextSize unit is a problem.

3JSON attribute nodes must not have spaces.

4. Third-party fonts must all be lowercase.

5When the holder is reused in the custom adapter of ListView, if the View Checkbox and other corresponding states display different **, remember to write the situation completely, otherwise there will be a problem of confusion.

6. When uploading, remember to ask the server if there is a limit to the upload file size.

8. When there is reuse, try to move operations such as new objects outside of reuse to prevent OOM

9. Database operation locking.

10. Controls such as dialog, popupwindow, etc., which are displayed with activity, need to be closed when the activity is closed (and turned off before).

11toast to determine whether the format (null, etc.) is encapsulated.

12UI layout test on multiple models.

13New handler should be written immediately after the acquisition of other controls to prevent null pointers.

Want; 15. For some specific edittext that can only be numbers, set the soft keyboard type to numbers, saving the user the step of switching.;

16armeabi-v7a

17. There will be two times to listen to keyboard input: (once up and one down).

18 It is best not to duplicate the name of different types of resource files, otherwise you will occasionally find a null pointer, and Eclipse will extract it to find another control.

19AlarmManager PendingIntent This thing doesn't work in MIUI...

20 part of the system datepickdialog's ondateset is executed twice.

21fragment startactivityforresult **。

Be careful, there are pits everywhere.

1. Learn Android If your English is not very good and the foundation is not solid, it is recommended not to read Google's development documents directly for the time being, then it looks more difficult 2. Before getting started, it is recommended to find a book to learn, and the learning process starts with basic controls, four major components, network access, database, animation design, etc.

Refer to the following: 1. Don't reject new technologies and tools. Versions after Android Studio have basically stabilized enough to support normal work development. In terms of writing efficiency alone, the benefits of Android Studio definitely outweigh the learning costs of Android Studio and Gradle.

JetBrains' IDE has been used and said to be good.

You can read as many books as you like and make more friends like this.

Bit of morality, few and comfortable purposes.

First of all, if the real machine is debugged, try to use the native system to debug, there are many modifications to the domestic customized system, and there may be inexplicable errors. Secondly, the update UI can only be updated in the main thread, which is a mistake that newbies will make.

Don't just update the system.

lest your phone get stuck.

It is best to pay attention to the packager anti-packaging and it is best to set up a network file check.

It is always said that there will be all kinds of pitfalls; Among them, there are many pitfalls connected to the network, which require more practice and more attention;