⚡
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
  • Log in / Log out buttons
  • Action buttons
  • Checkbox
  • Text input
  • Upload image

Was this helpful?

  1. UX requirements

Interactive components UX requirements

This section outlines the UX design requirements for various buttons and input fields within your ⚡️claimr campaigns, ensuring they are user-friendly, accessible, and visually appealing.

PreviousPop-ups UX requirements

Last updated 6 months ago

Was this helpful?

Interactive components, such as buttons and input fields, are essential elements for gathering user information and enabling interactions within your claimr campaigns. Designing user-friendly interactive components is crucial for ensuring a smooth and efficient user experience.

Log in / Log out buttons

Facilitate user authentication and session management.

  • Clear Labels: Use concise and descriptive labels like "Log In" and "Log Out".

  • Visual Distinction: Differentiate the two buttons through color, styling, or placement.

  • Feedback: Provide visual feedback upon interaction, such as a loading state or change in button appearance.

  • Accessibility: Ensure buttons have clear focus states.

Action buttons

Trigger specific actions within the campaign (e.g., "Submit," "Next," "Follow").

  • Clear labels: Use action-oriented verbs that accurately describe the button's function.

  • Visual hierarchy: Make action buttons prominent and visually distinct from other elements.

  • Disabled state: Clearly indicate when a button is disabled (e.g., grayed out, with a tooltip explaining why).

  • Feedback: Provide visual feedback upon interaction, such as a loading state or change in button appearance.

Checkbox

Allow users to select or deselect options.

  • Clear labels: Provide concise labels adjacent to checkboxes, describing the corresponding options.

  • Visual states: Clearly differentiate between checked, unchecked, and disabled states using distinct visual cues (e.g., checkmark, empty box, grayed-out box).

  • Hit area: Make the clickable area surrounding the checkbox large enough for easy interaction.

Text input

Enable users to enter textual information.

  • Clear labels: Provide descriptive labels above or adjacent to input fields.

  • Input field size: Adjust the input field size appropriately based on the expected input length.

  • Placeholder text/hint: Use placeholder text or hints to guide users on the expected input format or content.

  • Disabled state: Clearly indicate when an input field is disabled (e.g., grayed out).

  • Error handling: Provide clear error messages and guidance if input validation fails.

Upload image

Allow users to upload image files.

  • Clear CTA: Use a clear button or label (e.g., "Upload Image") to initiate the upload process.

  • File selection: Provide a standard file selection dialog for users to choose an image file.

  • Image preview: Display a preview of the uploaded image before submission.

  • File validation: Implement file type and size validation to prevent errors.

  • Error handling: Provide clear error messages if file validation fails.

  • Accessibility: Ensure the upload process is accessible to screen readers and keyboard users.

Example: Log in button
Example: Log out button
Example: Active CTA
Example: Disabled CTA
Example: checkbox
Example: Text input in different states
Example: Upload image
Example: Submit uploaded image
Examle: Verification state