caravan-bitcoin/caravan

Make Caravan/Coordinator Components Mobile Friendly and Responsive

Open

#294 opened on May 29, 2025

View on GitHub
 (6 comments) (0 reactions) (2 assignees)TypeScript (102 forks)auto 404
@caravan/coordinatorgood first issuehelp wanted

Repository metrics

Stars
 (85 stars)
PR merge metrics
 (PR metrics pending)

Description

Overview

This issue will track the work needed to make the Caravan Coordinator UI components mobile-friendly and responsive. This includes ensuring proper layout, readability, and interactivity across different screen sizes — especially phones and tablets.

Motivation

  • Improve accessibility and usability on mobile devices
  • Ensure better UX for users using Caravan on-the-go
  • Support onboarding of new users from non-desktop platforms ( as per the long term vision )
  • Align UI with modern responsive design principles

Scope

We will audit and progressively refactor components under the src/components/ directory and related layout files to support responsiveness. This may include applying flex/grid layouts, media queries, scalable typography, and collapsible menus.

Components Likely to be Affected (Initial Targets)

  • Navbar.jsx
  • Footer.tsx
  • WalletInfoCard.jsx
  • RegisterWallet/*
  • Coldcard/*
  • CreateAddress/*
  • ClientPicker/*
  • NetworkPicker.jsx
  • QuorumPicker.jsx
  • Help.tsx
  • Disclaimer.tsx

Subtasks

  • Audit all src/components views on mobile sizes
  • Add responsive layout to WalletInfoCard (wrap address lines, etc.)
  • Adjust tables in RegisterWallet for horizontal scroll or stacking
  • Ensure Coldcard flow pages do not overflow on narrow screens
  • Add responsive utilities using styled-components/tailwind/custom breakpoints
  • Test across major mobile browsers

cc: @bucko13 @jbrauck-unchained

Contributor guide

Research direction
Audit the listed components for mobile layout issues. Use media queries and flex/grid to make them responsive. Test on various mobile browsers.
Tech stack
typescriptreact
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ReactCSS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65