Smartphone Development Experience 1

Recently, I have been developing software on Windows Mobile's smartphone. The development process is quite different from that of Windows development.

The smartphone interface is not small, but it does not support the touch screen or the Standard Input Panel (SIP) on pocketpc, so there are no mouse operations, all operations are basically implemented through the keys on the mobile phone and limited function keys. Click the buttons at the bottom of the screen to complete the main functions.

This inconvenient input makes us have a headache. There is no way to make it easy for users to enter information. To improve user input efficiency, we can only try to make users less input (except for those who are quick at hand ), therefore, no input is allowed during the design. The information can be directly displayed from the context-related information, and ComboBox can be used wherever the standby option is used. The basic task is to allow users to select, change, and complete the task.

Another problem is the display efficiency of the interface. Due to the configuration problem of the smartphone, the display capability of the interface refreshing is limited. If it is not handled properly, it may take half a day to display the screen, this should start with the interface design. The cell phone screen is small. If there are too many things on the screen and the display is very slow, the input will be divided into multiple interfaces, the associated information is displayed on multiple interfaces. If you need to display many items on one screen, you must let others know that there are other items to be displayed, add a scroll bar.

If the initialization of the new page is too slow, it will not be displayed first. The previous page will be displayed first, and the next page will be displayed after initialization, you only need to hide the interface that needs to be initialized in the load_form event of the interface. After Initialization is finished, it is displayed, saving the inconvenience of a new interface during initialization.

Multi-threading is used. In actual use, the input time is long. If you do not use this time, it will be a waste of time. After the user interface is displayed, you may have to do some minor operations in the background, in this way, all the users in this province have been input, and they have to wait for half a day before they start to work. For example, during the initialization process of the background database, the database is generally read first. After the database Initialization is complete, the login interface is displayed, and data is initialized in the background, generally, the user reads data during the input process, so that the user does not need to wait too long.

There are still a lot of slow summary. Let's say so much, the first write is a bit messy :)