Spotify won't open-source Car Thing, but starts refund process

Refund process and customer experience

• Refund pathway is opaque: requires going through support chat, potential escalation to “specialty advisors,” and waiting for follow‑up emails.
• Several users report being offered Premium months instead of cash; some insist and eventually get full refunds, others only credits.
• No automatic refunds despite Spotify already knowing owners and billing details; many see this as deliberate friction to reduce payouts.
• Timelines are unclear; some receive immediate refunds, others expect long delays.

Bank details and security concerns

• At least one user was asked by support to email bank name, routing/account number, SWIFT, and a screenshot to process a refund.
• US‑based commenters flag this as risky because routing+account can be used for debits; EU‑based commenters note those details are commonly shared there.
• Many argue a “global” company should know US banking norms and not request this via email.

Why brick Car Thing at all?

• Commenters see bricking a 2‑year‑old product as extreme; some speculate about DRM/licensing constraints, security flaws, or internal disorganization after layoffs.
• Others point out that maintaining legacy APIs and server logic has ongoing cost and complexity, especially with licensing tied to device type.

Use cases and impact

• Car Thing is essentially a dedicated remote/display for the phone’s Spotify app, aimed at cars without CarPlay/Android Auto or with limited controls.
• Some use it in rentals or at a desk as a hardware controller; they’re particularly frustrated by the shutdown.
• People who bought via third parties or in unsupported regions feel especially burned, as they may be ineligible for refunds.

Open source, hacking, and e‑waste

• Many urge Spotify to open‑source firmware or at least release flashing tools; others note likely third‑party licenses make that difficult.
• Device has already been rooted; projects exist to run custom software (even Doom), though hardware (500 MB RAM, Qt/EGLFS stack) is limiting.
• Significant anger at deliberate e‑waste; proposals include laws against bricking, mandatory open hardware/firmware after EOL, and repealing DMCA 1201.
• Some argue e‑waste from such small devices is minor compared to appliances, but others stress the principle and precedent.

Comparisons and broader criticism

• Google’s handling of Stadia (automatic refunds, enabling controller reflashing) is widely seen as superior.
• Logitech is cited as a positive counterexample: long support, open‑sourced server for old devices, generous hardware policies.
• Spotify is criticized for user‑hostile behavior (e.g., aggressive downgrade behavior, podcast ads even on paid tier) and perceived focus on profit over trust.