foreword
As a 3-year-old Android developer, I stumbled along the way, stumbled, and did not know how many detours. Here I would like to give you some suggestions for those who embark on the road of Android development, all of which are based on my experience.
I hope that everyone's development road will be smooth and prosperous.
Ten points to avoid pits:
-
Not understanding the Android lifecycle: The lifecycle of an Android application is very important, it determines the behavior and performance of the application. If the developer doesn't understand the life cycle, it may cause the application to crash or cause other problems.
-
Neglecting memory management: Android devices have limited memory resources. If developers do not pay attention to memory management, it may cause the application to crash or run slowly.
-
Does not consider screen size and resolution of different devices: Android devices have various screen sizes and resolutions, if the developer does not take these factors into account, it may cause the application to display abnormally on some devices.
-
Excessive use of broadcasts: Broadcasts are a very useful Android component, but excessive use of broadcasts can lead to degraded application performance.
-
Neglecting User Experience: User experience is very important and if developers ignore user experience, it may make the application unpopular.
-
Network connection not considered: Android applications usually need to interact with the network, and if the developer does not consider the network connection, the application may not work properly.
-
Ignoring security: Security is very important. If developers ignore security, it may lead to application attacks or user data leakage.
-
Failure to consider multilingual support: Android devices are used worldwide, and if developers do not consider multilingual support, it may result in applications not being available in certain regions.
-
Excessive reliance on third-party libraries: Third-party libraries can speed up the development process, but excessive reliance on third-party libraries may lead to application instability or security issues.
-
Failure to test: Testing is very important, if the developer does not test, it may cause various problems in the application.
at last
Give everyone a complete set of Android learning materials.
In the past, I searched all over the Internet, and the things I found were scattered. Most of the time, I just looked at them and then they disappeared. Time wasted, but the problem has not been solved, which is very frustrating.
Later, I compiled a set of materials by myself, not to mention, it's really delicious!
The information is organized, systematic, and comprehensive. It is not convenient for me to release it directly. You can first see if there is anything you can use.
Attached is the free prostitution address: "Android Architecture Video + BATJ Interview Topic PDF + Study Notes"
