6-point principles for mobile applications to enrich dynamic effects

If you want to make your mobile apps more lively and smart, rich dynamic effect is indispensable, rich dynamic effect can make your application more dynamic, full of vitality, rich dynamic effect can let your application show efficiency, improve quality sense, rich dynamic effect can make your application full of charm, explore; Rich dynamic effect can let your application reduce anxiety, eliminate waiting feeling, rich dynamic effect can make your application full of flavor, have rhythm, rich dynamic effect can make your application have surprising information organization, neat and efficient.

Here are six simple and common ways-transitions, invitations, transitions, feedback, scaling, adsorption.

Principle I: Transitions

Because the mobile screen space is limited, more content will be hidden behind the screen, or the left side of the screen, the right, the bottom, the transition dynamic performance helps to create a sense of spatial orientation. Transition dynamic is the most widely used type of activity, after all, the iphone, Andoird, WP7 have provided some of the official performance of the API, some simple dynamic effect can be directly called the official API to complete. Android Official 8, the iphone official action 19, WP7 official action 6, the specific platform of the difference between the dynamic effect, follow-up has the opportunity to share.

Principle two: Invite

Directly provide the invitation to inform users of what can be done, the effect of the most intuitive, the best guide. However, attention must be paid to the operation of the invitation must highlight the main functions or tasks, can not be any function to invite users to try, you know, most users use only 20% of your application even good. Invitations cannot be too compelling, and, if not necessary, it is impolite to interrupt the actions that the user is performing.

Principle III: Transition

When the application is loading data, be sure to give the transition, let the user know that the application is working hard, the system-level transition is divided into two-progress bar and Chrysanthemum turn, the progress bar is used in the predictable completion of the progress and the rest of the time, the Chrysanthemum turn is used in the case of unpredictable time remaining. Photo forwarding on the iphone, messages moving from inbox to spam all have a good transition, letting users know that they are currently jumping from one application to another, knowing that jumping from one folder to another avoids the hassle of getting lost.

Not all cases, should be clear to inform the user of course the load progress of the task, such as the iphone with the SMS application, send a message when there is a progress bar, the intention is good, let users know the progress of the message sent. However, because the progress bar will cause a clear sense of waiting, and users worry about leaving the current interface, SMS will send a failure (how users know how to sync and asynchronous?), so can only be silly waiting there. In fact, can let the text message backstage send, as long as the guarantee sends the failure to have the way to inform the user. Similarly, the picture sharing application is the same, the background upload can be.

Principle IV: Feedback

When a task succeeds or fails, there is a way to inform the user. For example Reeder client, will be after you point unread, immediately the bomb layer tells you has marked as unread, after you point statted, immediately the bomb layer tells you, already starred. Feedback needs to be noticed by the user at the right time, to communicate the results of the operation succinctly and clearly,

If a successful class of reminders, often just tell the state on it, the user does not need to perform operations, feedback can disappear. And if the failure of the class feedback, you need to attract attention, can be relatively strong some, the position of feedback can be considered relevance, such as account errors can appear next to the account, password errors can appear next to the password, using the relative warning color and design style.

Principle Five: Scaling

In one inch of gold in a cell phone interface, eager to build a duplex building, a row when two lines. In fact, it is not possible, just need a design idea-----------box. Each function module is a box, when you do not need to use, it is just a box, labeled on the top, you know the inside is a sock, when you need, you can open the box, exposing a lot of double socks.

Like Bluga this input box, when you do not need to input, it looks like an input entry, but when you click, the input of the auxiliary information is out, a larger text composition box, location, picture, send button, you can open the box, edit a rich message.

Principle VI: Adsorption

Adsorption is a very aesthetic design in the grid system, when you drag an application to switch position, the application will be automatically adsorbed to the alignment of the grid position, to ensure that the interface neat and tidy (unlike some of Nokia's mobile phones, widgets can be dragged full screen, like my messy desktop); When you drag a application to another application, you can become a folder, this is also through the style of folders and the effect of adsorption, so that users understand the creation of the interactive folder.

Any dynamic effect, need to go through the scene and the needs of the thinking, in what kind of special situation, solve what kind of problem, not to move, WP7 dynamic effect, I am afraid to see a long time will be tired of it.

In addition to the interface itself, but also need to include vibration, voice, gestures and other factors to consider, good action, with the appropriate sound, reasonable gesture, is the most natural way of interaction.

Starting today, try to improve the quality of your application and let it move!

Author: Elya Girl

Article Source: elya.cc