Element alignment:
- All elements should be left aligned (all interfaces should follow the left alignment, and the left margin should be 24 pixels (the "about" page can be an exception ))
- Friendly tip: when there are few application pages, it is easier to fix this problem. When there are many pages, it is troublesome to fix this problem. Therefore, we recommend that you avoid this problem when starting development;
Element interval:
- Element interval (the horizontal or vertical intervals of all elements should be the same. It is recommended that the interval be 12 pixels or a multiple of 12 pixels)
Floating button:
- The interface should avoid floating buttons, which should be placed in the AppBar;
- In special cases: For the login/Registration button, if the keyboard of the input method does not block the button, you can allow exceptions; otherwise, the two buttons may also be placed in the AppBar (ISVs will change the Registration button to the link form for repair );
- Any reserved floating button cannot change its color after being clicked. Multiple buttons should be left aligned, and a single button should be center aligned and stretched to fill the horizontal space;
Return/close:
- For Windows Phone, you do not need to close the button. The shutdown is completed by the Control Key of the hardware device. The following three keys cannot appear in the WP7 application;
Default icon:
Unified button icon:
- WP7 comes with some standard buttons, such as the submit, confirm, send, and favorite buttons. Refresh operations generally require the buttons to appear in the application bar;
Search keyboard:
- The search function is implemented by using the search keyboard. For details, refer to Bing search.
- Friendly prompt: Set the InputScope attribute of the text box to Search;
Panoramic/pivot View:
- Do not use switch controls or horizontally adjustable controls in pivot/panoramic views. Because the sliding of the horizontal control will affect the sliding operation of the Internal Control, we recommend that you use a separate page for this operation;
Tile image:
- Tile images should be designed to be 2D, not 3D.
- Shadow effects/black and white backgrounds/out-of-light/meaningless images/unclear images displayed in black or white are not allowed on Tile.
- Tile should be clearly visible under any circumstances
Resource Configuration: 3: 1: 1
Performance Optimization suggestions:
- Page navigation
- 256 MB and 512 MB
- Memory release and monitoring
- GC Utilization
- Delayed Data Loading
- Serialization
[Reference: Wei Xiaowei] It feels good;