⚡
claimr
  • Getting started
    • Create an account
    • Sign in to your account
    • Reset password
    • Edit profile
  • ⚡️claimr core components
  • Team roles and management
  • Campaigns
    • Create new campaign
    • Campaign settings
  • Groups
    • Create new group
    • Group settings
  • Quests
    • Create new quest
    • Quest settings
  • Tasks
    • Create new task
    • Task settings
    • Telegram tasks
    • X (Twitter) tasks
    • TikTok tasks
    • Discord tasks
    • YouTube tasks
    • Web3 tasks
      • Connect a wallet
      • Transactions count
      • Wallet balance
      • Token balance
      • NFT balance
      • Link3 balance
      • Mint an NFT (721)
      • Mint an NFT (1155)
      • Verify transactions
    • PoW tasks
    • HTTP request tasks
    • Referral tasks
    • Form tasks
    • Poll tasks
    • Events tasks
    • API tasks
  • Widget
    • Publish campaign
    • Widget configurations
    • Widget attributes
    • Integrate claimr widget into your website
    • claimr widget integrations
      • Google Analytics integration
      • Google Analytics Client ID
      • Google Tag Manager integration
      • HotJar integration
  • Rewards
    • Reward settings
    • Custom rewards
  • Events
    • Daily check-ins
    • Challenges
    • Ranks
    • KOLs
  • Codes
    • Secret codes
    • Invite codes
      • Enter invite code task
      • Claim invite code task
    • Gift codes
  • Test users
  • Pop-ups
    • Into pop-up
    • Completion pop-up
  • API
    • API token
    • API methods
    • User token
  • Webhooks
    • Set up webhooks
    • Assign webhooks
    • Webhook scopes
  • SDK
  • Forms
    • Create forms
    • Form settings
    • Pages
    • Blocks
    • Quizzes
  • Data analytics
    • Activity
    • PoW analytics
    • User information
    • Failed actions
    • Issues analytics
  • How to
    • Create X campaign
    • Create Discord campaign
    • Integrate claimr widget into dApp
    • Integrating claimr widget into Telegram mini app
    • Customize user experience with tags and attributes
    • Add custom points to users
  • UX requirements
    • Campaign UX requirements
    • Group UX requirements
    • Quest card UX requirements
    • Quest UX requirements
    • Task UX requirements
    • User progress UX requirements
    • Pop-ups UX requirements
    • Interactive components UX requirements
Powered by GitBook
On this page
  • Understanding Quest cards
  • Quest state indicators
  • Image
  • Quest name
  • Short quest description
  • User progress bar
  • Counters
  • Rewards
  • CTA button
  • Quest blockers and dependencies
  • Countdown

Was this helpful?

  1. UX requirements

Quest card UX requirements

This section outlines the key design elements and considerations for creating effective and engaging quest cards in your ⚡️claimr campaigns.

PreviousGroup UX requirementsNextQuest UX requirements

Last updated 6 months ago

Was this helpful?

Understanding Quest cards

Quest cards serve as the primary interface for users to interact with individual quests within your campaign. Each card should provide a clear overview of the quest's objectives, rewards, and progress, enticing users to embark on the journey.

Quest state indicators

Clearly communicate the current state of the quest: Active, Completed, or Locked.

  • Visual Clarity: Employ distinct colors, icons, or labels to differentiate between each state.

  • Accessibility: Ensure the indicators are easily distinguishable for users with visual impairments.

  • Consistency: Maintain a consistent visual style for state indicators across all quests.

  • Placement: Position these indicators prominently on the quest card.

Image

Provides a visual representation of the quest's theme.

  • Relevance and quality: Choose high-quality images that are relevant to the quest's content.

  • Size and aspect ratio: Ensure the image is appropriately sized and cropped.

  • Accessibility: Provide alternative text descriptions for images.

Quest name

Clearly and concisely conveys the essence of the quest.

  • Clarity: Use action-oriented language and avoid jargon.

  • Length: Keep the title short enough to fit within the card's layout.

  • Hierarchy: Use a larger font size and/or bolder font weight to distinguish the title.

Short quest description

Provides a brief overview of the quest's objectives and rewards.

  • Conciseness: Craft a succinct description.

  • Clarity: Use plain language and avoid technical terms.

  • Enticement: Use persuasive language to encourage participation.

User progress bar

Visually represents the user's progress towards completing the quest.

  • Clarity: Use a clear and easily understandable progress indicator.

  • Visual feedback: Provide updates to the progress bar as the user completes tasks.

  • Accessibility: Ensure the progress bar is accessible to screen readers.

Counters

Display numerical information related to the quest, such as the number of tasks completed or rewards earned.

  • Clarity: Use clear labels and units of measurement.

  • Placement: Position counters near relevant elements.

Rewards

Showcase the rewards that users can earn by completing the quest.

  • Visual appeal: Use high-quality images or icons to represent the rewards.

  • Clarity: Clearly indicate the type and quantity of rewards offered.

CTA button

Prompts users to take action and start or continue the quest.

  • Clarity: Use action-oriented language.

  • Visual prominence: Make the button stand out.

  • Accessibility: Ensure the button is easily clickable.

  • State differentiation: Visually distinguish between active and inactive states.

Quest blockers and dependencies

Display any conditions or requirements that must be met before a user can start or continue a quest.

  • Clarity: Clearly communicate the blockers and any actions the user needs to take. Show any other quests that must be completed before this quest can be unlocked.

  • Visual cues: Use icons or labels to visually distinguish blockers.

Countdown

Displays a timer for time-sensitive quests.

  • Clarity: Use a large, easy-to-read font and clear time units.

  • Urgency: Consider using color or animation to create a sense of urgency.

Quests at different states
Example: Quest card with an image
Example: Quest name, user progress bar, rewards, and counter
Example: CTA buttons for different states
Example: Quest card with dependencies
Example: Quest card with a countdown timer