Stable Chrome
Normal public Web Store build.
Stable details →Status
What is actually current.
Store versions, source-repository state, Android development and compatibility notices are kept separate so one number does not pretend to describe every build.
v0.1.5
Chrome DEV
Published development/testing channel. Not every small local change becomes a store upload.
Chrome DEV →Firefox DEV
Public experimental build for Firefox desktop + Android.
Firefox DEV →Android app
Standalone QoL-integrated app; public release/update flow is still being prepared.
Android details →Repositories exist; full files are still being filled in.
Checking Stable GitHub…
Checking DEV GitHub…
Checking Android GitHub…
When root files are available, this site automatically uses them for features, changelogs and supported demo settings instead of its bundled fallback snapshots.
One place for real breakage.
If a SpicyChat site change breaks a QoL feature badly enough to affect lots of people, the top-of-site status banner can be switched from the normal project update to a compatibility incident.
Known issues also belong in the QoL Discord so users do not have to guess whether a bug is already known.
Open QoL Discord →Why DEV numbers differ
Chrome ≠ Firefox ≠ local dev.
A DEV version shown in a browser store means that exact submitted build. Small local development changes may happen between store uploads, and Chrome/Firefox review/upload timing is separate. The site therefore reads each public distribution independently instead of using one manifest number for everything.