Android Application Development Rules

Application Rules
1. do not impede the voice calls and messaging services of mobile phones.
2. Do not damage or try to weaken or expand the hardware, firmware, software, and OEM components of the device.
3. Do not abuse the operator's network or cause any problems on the network.
4. Do not disappoint users' trust

To meet the needs of mobile users
Applications should meet the following requirements:
1. Strong responsiveness, stability, and security
2. simple and intuitive user interface, easy to use
3. Avoid obstacles during use.
4. The server should work around the clock (remote services or servers can be used at any time)
5. Contains "help" and/or "about" pages for feedback and support

Uidesign suggestions
1. Save and use the screen space reasonably. Displaying too much information on the screen at a time will make users get bored.
2. The menu type and buttons of the workflow on the user interface should always be consistent, and the behavior mode of hardware should be fully tested.
3. There should be a large enough touch mode "Click Area", and the distribution should be reasonable.
4. Use a large and easy-to-read font, And the Icon size should be as big as possible.
5. Use standard controls, such as quick contact icons, content providers, and search adapters to work closely with other applications.
6. When designing a user interface with a large number of Guangxi users, the local nature needs to be fully considered. Some comments may be longer than other languages,
7. Reduce the number of buttons or clicks in the day,
8. Do not assume that a certain input mechanism (for example, a specific key or keyboard must exist) can be used on all devices.
9. When designing the default use case for each screen, you can use only the thumb to meet your needs. For some special use cases, you may need other buttons and enter

Method, but use the thumb up whenever possible by default
10. Adjust the image size properly for the device. Do not use oversized resources or components. Even if they can be adjusted properly, they consume valuable resources.

Device resources, and loading is slow. In addition, you can also consider removing unnecessary information, such as exif or iptc metadata, and using similar

ImageMagick or PNGOptimizer. In addition, the nine-cell image rendering tool can also help optimize Android image files.
11. For the sake of "friendly" user interface, we need to assume that the user did not really read the application license agreement when installing the application, if your

The operations to be performed by the user program will result in the user to pay or disclose the user's private information. Therefore, you can consider notifying the user again before execution.

Design Stable, responsive mobile app highlights related websites (http://android-developers.blogspot.com)
1. Do not perform operations that consume a large amount of resources in the main UI process, and use Asynchronous tasks or threads for too complex operations.
2. Use efficient data structures and algorithms to meet the responsiveness needs of applications and enjoy a pleasant User Experience
3. Use the loop with caution. Check the code repeatedly and perform performance tests.
4. Record the status of the application at all times. The Android Activity stack can support the application well, but you still need to pay special attention not to go beyond these statuses.
5. Remember to save the application status because it may be suspended or terminated at any time. If your application is suspended or closed, the user cannot enter

If the app token can be returned in a "beautiful" manner, the APP must not praise it.
6. Quick Start and quick return. You cannot give the user a thumbs up to wait for the application to start. On the contrary, you need

A clever balance between them, because your application may be suspended (closed) at any time without warning)
7. Use the progress bar to inform the user of the Operation during the execution duration. However, you can consider handing over these heavy tasks to the server, instead of finishing the operation on the device.

Because they may be significantly battery, which is unacceptable to many users.
8. before a long operation, make sure that the operation is successful. For example, if your application needs to download a large file, check the network connection, file size, and available space before execution.
9. minimize the usage of local storage space because most devices have limited resources. If possible, use external storage. it should be noted that the SD card neck may be removed or replaced by the user at any time, and your application needs to handle such events smoothly
10. You need to know that calling the content provider through data and crossing the aidl obstacle requires performance consumption. Therefore, use such operations wisely.
11. make sure that the resource consumption of the application matches the target user. Gamers should be able to accept that games with complex plotting functions consume a lot of their power, the applications used at work do not consume unnecessary batteries, and must be lightweight enough to satisfy those who are traveling all day because they often do not have the time to charge their devices.