Pebble Production: February Update

Original Article ↗ Hacker News Discussion ↗

Production delays & expectations

  • Some buyers are worried they won’t receive their Pebble before external deadlines (e.g., Fitbit→Google migration), and note repeated slips (Dec→Mar→Apr).
  • A few express frustration that new products (e.g., ring/Index, Duo) were launched while core watch shipments are delayed, making current timelines feel unreliable.

What sets Pebble apart

  • Key differentiators repeatedly cited:
    • Always-on reflective display with high daylight readability.
    • Multi‑day to ~month‑long battery life.
    • Privacy (no forced cloud syncing) and easy access to raw data.
    • Hackability: open SDK, vendor-supported open-source OS, no app‑store gatekeeping.
  • Many like that it’s a “phone companion” rather than a second phone: basic notifications, music control, light health tracking instead of a feature‑heavy, distracting smartwatch.
  • Nostalgia and “charm” of the UI/animations and quirky community apps are major draws, even for people who also own Apple/Garmin devices.

Display technology debate

  • Several comments clarify that Pebble’s screen is not e‑ink but Sharp memory‑in‑pixel (MIP) LCD, sometimes marketed by Pebble as “e‑paper”.
  • Long subthread contrasts MIP, e‑ink, and other e‑paper tech: refresh rate, ghosting, color contrast, and power characteristics are discussed in detail, with some disagreement over terminology but general agreement on the tech trade‑offs.

Alternatives & competition

  • Numerous alternatives mentioned: Bangle.js, Watchy, PineTime, Amazfit, Garmin, Casio solar models, Withings, etc.
  • Opinions split: some argue you can get cheaper hackable/open watches from China; others counter that Pebble’s ecosystem, UX, and openness (including vendor support) remain unique.
  • Some want exactly an Apple‑Watch‑level sensor suite in a Pebble‑like low‑power, e‑paper form factor; current products only partially meet this.

Features & missing features

  • No NFC/tap‑to‑pay is a dealbreaker for some; others propose workarounds (payment straps, rings, DIY embedded card chips) but note regional and reliability issues. Pebble’s founder has publicly deprioritized NFC.
  • Heart rate, steps, and sleep tracking are present on Pebble 2/Time 2, but Apple Health integration on iOS is unclear/limited due to platform restrictions.
  • Left‑handed mode and button‑driven UX receive praise for usability without looking at the screen.

Ecosystem & software updates

  • The reclaiming of the old Android package ID restores many legacy integrations without developer intervention.
  • Built‑in weather API shimming via Open‑Meteo is widely appreciated for keeping old watchfaces functional; Open‑Meteo’s commitment to open access is warmly received.

Hardware durability & environment

  • Discussion of waterproofing cautions: hot water, thermal extremes, and glue/seal degradation likely caused some legacy Pebble failures.
  • Some wish manufacturers would use more robust, marine‑grade materials even at higher cost.

Index ring & voice/AI workflows

  • Mixed views on the Index ring: some are excited about quick voice‑to‑AI workflows and share DIY “airtag‑sized” recorders plus custom agent setups; others don’t see its value over a watch and dislike ring ergonomics.

Pricing, tariffs & manufacturing

  • A few question added per‑watch tariff charges and note the irony of tariffs intended to fight inflation increasing end‑user prices.
  • Someone asks about US manufacturing, but no concrete answer appears.
  • Confusion and mild annoyance around the one‑off nature and quality issues of the cheap plastic “Pebble Duo” run are mentioned.