# Design Recommendations

Based on the characteristics of Mini-Programs, we have formulated design recommendations for Mini-Programs. The aim is to fully respect users' right to know and operational rights while establishing a friendly, efficient, and consistent user experience within the Mini-Program ecosystem. At the same time, it seeks to maximize adaptability and support for different needs, achieving a win-win situation for both users and Mini-Program service providers.

# 1. Mini-Program Design Principles

  • Consistency: A unified design language for Mini-Programs emphasizes framework generality and interaction logic consistency.
  • Extensibility: Multiple extension styles are available for selection, with clear operation guidance. The use of controls and interaction methods remains consistent.
  • Lightweight: Systematic design simplifies hierarchy and reduces unnecessary interactions or page transitions.
  • Efficiency: Clear functional structure, simple interaction logic, timely feedback, and adherence to the principle of proximity.

# 2. Mini-Program Design Philosophy

# 2.1 Focus on Usage Scenarios

For Mini-Programs, clearly defining the usage scenarios of Mini-Program users is the top priority in product design. By combining real user needs during usage, the Mini-Program must meet the requirements of being simple, lightweight, and efficient. When designing a Mini-Program, keep the boundaries of requirements under control.

# 2.2 Provide Clear Interactions

In Mini-Programs, dynamic design and one-time use settings need to be well-balanced, ensuring that user operations are simple, understandable, and easy to use.

  • The user path in the Mini-Program must be singular (there can be many functionalities, but the path must remain singular).
  • Design a good one-time use mechanism (provide necessary guidance information for first-time use, reduce strange interaction designs, and adopt interaction patterns familiar to users).
  • Minimize dynamic design and decorative elements (without conflicting with brand tone design).
  • Arrange complex and redundant information clearly so that it is easy for users to understand and use.

# 2.3 Ensure Focused Usage

When users use Mini-Programs, most of the time they are solving specific problems or goals. Therefore, when users operate, try to meticulously and thoughtfully design the processes they need to complete to reduce psychological anxiety and unnecessary resistance.

  • Reduce unnecessary page transitions to lower the cost and anxiety of adapting to different pages.
  • Use options, auto-fill, and user data instead of tedious input and form content.
  • Add skeleton screens to enhance users' psychological sense of security (pre-loading state).

# 3. Mini-Program Design Review

Conducting a design review for Mini-Programs can help designers improve design efficiency and check the completeness and accuracy of various design experience points. Please mark the items as reviewed if no issues are found. Pages that do not meet the design experience standards will affect the overall user experience of the Mini-Program.

# 2.1 Core Experience Focus Points

  • LOGO is clear and recognizable.
  • Function icons are consistent.
  • Image assets are clear.
  • The frequency of non-user-initiated pop-ups on the same page is controlled to no more than two.
  • Navigation is used correctly.
  • Overall color usage on the page is clear and reasonable.
  • Visual elements on the page (ICONs, fonts, spacing, etc.) are consistent.
  • Page animations are used appropriately.
  • Default states of the page are expressed clearly.

# 2.2 Architecture and Flow

  • Information architecture is clear and easy to understand, with explicit guidance.
  • Relationships between navigation elements are clear and easy to understand.
  • Information hierarchy on the page is clear and reasonable, with smooth visual flow and clear focus.
  • User experience paths are consistent for similar tasks.
  • Operation paths align with user expectations.

# 2.3 Interface Presentation

  • Page layout complies with specifications.
  • Basic controls use components.
  • Fonts, font sizes, and colors are consistent.
  • Page color usage provides a good experience and clearly conveys information.
  • Information hierarchy is displayed clearly.

# 2.4 Data and Display

  • Missing data content displays default images/placeholders.
  • Incomplete data display includes truncation and presentation strategies.
  • Consideration of data limit values.

# 2.5 Copywriting

  • No typos exist.
  • Copy is concise, easy to understand, and unambiguous.
  • No obscure technical jargon is used.

# 2.6 Processes and Special Scenarios

  • All operations provide feedback.
  • Loading states are designed.
  • Feedback for failed operations includes explanations and suggestions.
  • Responses to special network conditions (weak signal, timeout, no network) are considered.
  • Responses to various login states (not logged in, after account cancellation, account switching, guest accounts) are handled.
© FinClip with ❤ , Since 2017