16 Big questions about the non-smooth user experience in mobile apps

Combined with the experience of mobile development in the past few years, we have listed 16 problems which lead to user experience, and hope that we can draw lessons after reading.

Perfect products exist only in the virtual, but this does not affect our pursuit of perfection, those problems may not all be caused by developers, but this does not affect us to think about making the ultimate product.

(1) When registering, it is sometimes difficult to receive the verification code, causing a group of users blocked in the registration phase.

A) Reason: SMS channel is not stable; many SMS messages need to be audited by a third-party channel company before they can be issued.

b) Solution:

This problem can not be solved completely, only alleviate.

One, this is a common problem, any platform will encounter, because of too much spam, so that the supervision department will be regularly checked, unless the third-party channels, direct docking operators.

Second, because it is a universal problem, so the product can not be used as a reliable, timely information channels.

Third, the mitigation plan: can simultaneously docking two third-party platform, alternately uses;

Four, mitigation: SMS arrival is not guaranteed order. This will cause the user to obtain the verification code again if they have not received the verification code for the first time. After a while he received a text verification code, but there is no guarantee that this text message is for the first time, or the second time. So the generation verification code for short intervals is guaranteed to be the same.

(2) The user turnover rate is very high when the information is filled in the registration period;

A) Reason: Fill the information too much, some information is very sensitive, users do not want to fill out, such as real name, SHENFA card number, bank card number.

b) Solution: Use the process, when necessary, to guide the customer to complete the information gradually, after establishing a trust relationship with the user, it is required to fill in sensitive information.

(3) Refresh the information flow, loading speed is particularly slow;

A) Reason: The picture in the information flow is too large;

b) Solution: A, using thumbnails, B, picture lazy loading; c, image cache.

(4) Some problems are exposed in the 3G network:

A) Reason: testing phase only in the intranet test, and intranet network situation must be better than 3G network.

b) Solution: Build a pre-release environment in the external network, or set up the test environment directly in the external network.

(5) Special power consumption on the Android side:

A) Reason: The test was also missed because some services were not closed in time.

b) Solution: Test needs to focus on performance testing, power consumption testing as one of the performance indicators.

(6) Some buttons in use need to be pressed more once to effect:

A) Reason: The button touch area is too small;

b) Solution: Testing and developers can not easily miss the interaction of the place, found as soon as possible to improve; In addition, such problems require the designer to develop a set of interaction specifications.

(7) long-time use of the app will result in the Flash back;

A) Cause: A typical memory exhaustion issue.

b) Solution: Developers need to do a good job of memory detection at the end, the tester should pay attention to the problem of flash-back in the test process, and cannot give up easily because it cannot be reproduced; the developer provides exception logging, which cannot be easily discarded because the test cannot reproduce the problem.

(8) the page switch feeling too slow;

A) Reason: Get the data from the server on the previous page before jumping to the next page.

b) Solution: Jump to the next page, render part of the content, and get the full amount of data, after all the data is obtained, then the remaining content is loaded.

(9) Upload avatar too slow

A) Cause: The picture is not scaled, cropped, and compressed.

b) Solution: Product and design make an estimate of the picture, define the maximum size of the picture, and the quality of the picture. Most of the time do not need high-quality pictures, uploading large images not only waste user traffic, but also occupy the server bandwidth and server storage space.

(10) When registering, for some mobile phone number segment is not supported;

A) Reason: The new number of mobile phone number is constantly appearing, and the client to the mobile phone number test is not considered.

b) Solution: The client does a relatively loose inspection, more stringent inspection by the server side.

(11) Emoticons cause some input to cause the service side exception or the client flash back;

A) Reason: the database only supports 3byte utf-8, while the emoji is 4bytes.

b) Solution: Consider the Android and iphone interpretation of emoji, it is recommended not to allow the upload emoji. We need to study this!

(12) The text display offside, covering the other areas;

A) Reason: The text content is longer than imagined.

b) Solution: Product and design to communicate the word number and length of the string, consider the layout in the extreme case. In fact, the product has to specify the length and the rules for all the input content.

(a) GPS positioning is not allowed, positioning time is too long;

A) Reason: GPS positioning accuracy of about 10 meters, and under the mask (cloudy with clouds, inside the car, indoor) positioning is very difficult, and slow.

b) Solution: The testers conduct outfield testing in a scenario close to the user's environment.

(14) applications often flash back;

A) The reason: most of the problems of development, such as access to invalid address, array out of bounds, no variable initialization began to use.

b) Solution:

First, this kind of problem mainly relies on the programmer own custom and the quality, strengthens the code specification.

Second, in the case of sufficient time, do a good job of code walk.

Third, it will be more difficult to encounter such problems on-line, all of the problems of the flash-back class to do in the application of logging, as well as the ability to automatically send logs.

(15) The user always presses "login", but is unable to login.

A) Cause: it was due to a server-side exception that could not be processed. And the client has no error prompts, causing the user to be very confused.

b) Solution: Any error situations, (expected arrival, not expected) have a hint to the user.

(16) After the launch, the design and product said that some areas of interaction is not and design discrepancies.

A) Reason: Before the launch, the design and product did not seriously use the full functionality of the app.

b) Solution: After the development is complete, the design and the product first must carry on the comprehensive trial to the product, and the signature made his mark, then by the test.

Finally, in the team I ask to be sure to check the following points before the product goes live:

1. Is the app equipped with the necessary features: statistics, log collection and sending, version detection and automatic updating, user feedback;
2. Ensure that the Product manager and designer have experienced the app and signed made his mark. Make sure the app embodies the vision of the product and design, without the wrong understanding.
3. Check for abnormal records on the client side of the test with the system crashing. Attention must be paid to frequently occurring anomalies.
4. Remove all debug code. (Annotated code block for//debug)
5. Clear all code in warning;
6. Confirm that the connection is a formal server.
7. Change the log level to only log critical issues.
8. Do a memory monitor, pay special attention to the list page and picture processing display page. operate multiple times to see if the memory is recovering or growing.
9. Estimate the power consumption of the application.

16 Big questions about the non-smooth user experience in mobile apps