← Pipeline

068 — EmojiPalette

Problem

Developers, designers, and social media managers frequently need the right emoji but face a frustrating workflow: native OS pickers are slow and lack search, web searches return blog-list articles rather than a quick-pick UI, and clipboard managers don't specialise in emoji. Teams that maintain style guides or documentation often need a curated set of approved emoji with consistent skin-tone selections, but no lightweight tool lets them build, share, and copy from a saved palette.

Core Features

  1. Category Browse + Instant Search — Emoji grouped by category (smileys, animals, food, activities, travel, objects, symbols, flags). A search bar filters across names, keywords, and tags in real time (client-side, no API).
  2. Skin-Tone Picker — For emoji that support it, a one-click skin-tone toggle swaps the variant inline and updates the copy target.
  3. One-Click Copy — Click any emoji to copy it (native clipboard API). A brief toast confirms the copy. Supports copying the raw emoji character or its :shortcode: / Unicode code-point.
  4. Saved Palette — Persist a user's frequently used emoji in localStorage. Drag-to-reorder, remove, or add from the browse grid. Export as a JSON or markdown list.
  5. Copy Format Selector — Toggle between raw emoji, :shortcode:, HTML entity (😀), and Unicode (U+1F600) output format.

Target User

  • Frontend developers embedding emoji in UIs or documentation.
  • Social media managers and content creators who need quick access to a vetted set.
  • Designers building emoji-rich prototypes or style guides.

Suggested Stack

  • Framework: Next.js (App Router) + TypeScript
  • Styling: Tailwind CSS + Shadcn/ui
  • Data: Static JSON file of emoji metadata (name, category, keywords, shortcode, skin-tone variants, codepoint) — shipped with the app, no DB needed.
  • Storage: localStorage for saved palettes (single-tenant, no auth).
  • No backend / no DB / no auth required — entirely client-side.

Feasibility Gut-Check (2–3 days)

  • Day 1: Source an open emoji dataset (e.g., emoji-mart data JSON), build the browse grid + search filter.
  • Day 2: Implement skin-tone variants, copy-to-clipboard with format selector, toast feedback.
  • Day 3: Saved palette (localStorage CRUD + reorder), export (JSON/markdown), responsive polish, tests.

Estimated effort: ~16–20 hours. No external APIs, no auth, no backend — pure client-side. Well within the 2–3 day budget.

🧠 Brainstormer Review

Score: 12/15 (Feasibility 5 · Market Fit 2 · Complexity 5)

Rationale: Trivially buildable but the core job-to-be-done (browse + copy emoji) is already served by free, ubiquitous alternatives — emoji-mart, OS-native pickers, Emojipedia, browser extensions. The "saved palette" and "copy format selector" are conveniences, not pain points that drive adoption. No clear demand signal.

Decision: DEFERRED (Market Fit gate override — Market Fit ≤ 2 auto-defers regardless of total).

Rescope suggestion: If revived, narrow to a niche with genuine demand — e.g. a team-curated emoji style-guide tool with org-level sharing (requires auth + shared palettes) or a developer-focused codepoint/shortcode lookup optimized for documentation workflows.