mozilla

Revision 468031 of ডিজাইন নীতিমালা

  • Revision slug: Web/Apps/Design/Guidelines/ডিজাইন_নীতিমালা
  • Revision title: ডিজাইন নীতিমালা
  • Revision id: 468031
  • Created:
  • Creator: towfiqueanam
  • Is current revision? No
  • Comment

Revision Content

 নিচের নীতিমালাগুলো আপনার অ্যাপ এ যোগ করার কথা বিবেচনা করুন যাতে ইউজারদের অভিজ্ঞতার সাথে তা মানানসই বা অনুকূলে থাকে।দয়া করে নোট করুন,এটি কেবল সামান্য কিছু ডিজাইন মূলনীতি যেগুলো অনুসরণ করে আপনি শুরু করতে পারেন এবং কোনভাবেই এটি বিস্তৃত বলা যাবে না।

 

Be consistent

Be consistent in your language. Refer to an action or an item with the same term in your app, and use each term for only one action or item.

Be consistent in your user interface (UI). For example, if you place your back button on the top left corner, it should not appear on the bottom left corner in other screens within your app.

Be consistent in your visual elements. If two elements look the same, they should have the same behavior. If two elements have different functions, they should have distinctively different looks.

Be concise and use appropriate language

The text you use should express the most important information in a concise way. Most users don’t read a lot before they decide to continue or to abandon a task.

Always provide clues and immediate feedback

Provide clues which make the correct steps apparent. For example, a big “+” button to indicate adding items if that’s the correct next step.

Always give immediate feedback when the users take an action. For example, if users click on a “new message” button, lead them directly to the screen for creating a new message. You could also temporarily change the color of the “new message” button and provide a tactile feedback to show that your app understands the users’ command.

If an action takes more than a few seconds, provide a status update. For example, if your app is downloading the new messages, you could show the progress with a loading icon.

Minimize typing

Use selectors, checkboxes, radio buttons etc., whenever you can. Typing on mobile devices is often a slow and tedious task.

Aim for a pleasant first launch experience

People often spend only a minute or two deciding whether to continue or abandon an app. Some of the factors you may want to consider include:

  • provide a quick introduction to your app (and provide an easy way to end it anytime)
  • instant access to features and suggestions
  • minimize initial user input
  • express the most important information in a concise way

Present action choices if possible

If your alert says “Delete all contacts?”, you should provide action labels like “Delete” instead of “OK”.

Also, try to avoid using alerts that only notify about a situation. Give your users a choice of actions to address the situation.

Focus on the main task

Decide the main task of each screen and place features related to the main task in the most prominent places.

Prepare for interruptions

People may use your app anywhere. Prepare for interruptions by saving the user’s work automatically if possible. Ideally, information and tasks should behave normally even without an Internet connection.

Revision Source

<p>&nbsp;নিচের নীতিমালাগুলো আপনার অ্যাপ এ যোগ করার কথা বিবেচনা করুন যাতে ইউজারদের অভিজ্ঞতার সাথে তা মানানসই বা অনুকূলে থাকে।দয়া করে নোট করুন,এটি কেবল সামান্য কিছু ডিজাইন মূলনীতি যেগুলো অনুসরণ করে আপনি শুরু করতে পারেন এবং কোনভাবেই এটি বিস্তৃত বলা যাবে না।</p>
<p>&nbsp;</p>
<h2>Be consistent</h2>
<p>Be consistent in your language. Refer to an action or an item with the same term in your app, and use each term for only one action or item.</p>
<p>Be consistent in your user interface (UI). For example, if you place your back button on the top left corner, it should not appear on the bottom left corner in other screens within your app.</p>
<p>Be consistent in your visual elements. If two elements look the same, they should have the same behavior. If two elements have different functions, they should have distinctively different looks.</p>
<h2 id="Be_concise_and_use_appropriate_language">Be concise and use appropriate language</h2>
<p>The text you use should express the most important information in a concise way. Most users don’t read a lot before they decide to continue or to abandon a task.</p>
<h2 id="Always_provide_clues_and_immediate_feedback">Always provide clues and immediate feedback</h2>
<p>Provide clues which make the correct steps apparent. For example, a big “+” button to indicate adding items if that’s the correct next step.</p>
<p>Always give immediate feedback when the users take an action. For example, if users click on a “new message” button, lead them directly to the screen for creating a new message. You could also temporarily change the color of the “new message” button and provide a tactile feedback to show that your app understands the users’ command.</p>
<p>If an action takes more than a few seconds, provide a status update. For example, if your app is downloading the new messages, you could show the progress with a loading icon.</p>
<h2 id="Minimize_typing">Minimize typing</h2>
<p>Use selectors, checkboxes, radio buttons etc., whenever you can. Typing on mobile devices is often a slow and tedious task.</p>
<h2 id="Aim_for_a_pleasant_first_launch_experience">Aim for a pleasant first launch experience</h2>
<p>People often spend only a minute or two deciding whether to continue or abandon an app. Some of the factors you may want to consider include:</p>
<ul>
  <li>provide a quick introduction to your app (and provide an easy way to end it anytime)</li>
  <li>instant access to features and suggestions</li>
  <li>minimize initial user input</li>
  <li>express the most important information in a concise way</li>
</ul>
<h2 id="Present_action_choices_if_possible">Present action choices if possible</h2>
<p>If your alert says “Delete all contacts?”, you should provide action labels like “Delete” instead of “OK”.</p>
<p>Also, try to avoid using alerts that only notify about a situation. Give your users a choice of actions to address the situation.</p>
<h2 id="Focus_on_the_main_task">Focus on the main task</h2>
<p>Decide the main task of each screen and place features related to the main task in the most prominent places.</p>
<h2 id="Prepare_for_interruptions">Prepare for interruptions</h2>
<p>People may use your app anywhere. Prepare for interruptions by saving the user’s work automatically if possible. Ideally, information and tasks should behave normally even without an Internet connection.</p>
Revert to this revision