SpinstackThe record is already on the platter when the Wi-Fi drops. That should not be the moment your listening history loses a play. Vinyl scrobbling can work offline, provided the app treats a spin as something you keep first and something you sync second.
This matters more with records than with most media. A spin has a physical beginning: you chose a pressing, pulled it from the shelf, cleaned it if it needed it, and lowered the needle. The log should be there for that, whether or not the network is.
Offline scrobbling starts with local capture
Strictly speaking, a scrobble is a play event sent to a remote service, so it cannot be delivered while you are offline. But the useful part of scrobbling (what you spun, when, and which copy it was) does not have to wait for a server.
An offline-capable log records the event on the device: the release, the time, and anything you add while the record is still in front of you. When the connection returns, the app reconciles that local history with the places you have chosen to keep it. The network carries the history; it is not where the history lives.
With a few hundred records you might only notice this on a flight, in a basement listening room, or at a record fair with poor reception. With several thousand, and a habit of using spin history to understand the shelves, you notice every gap. You remember playing a record and the library says you did not. That is bad data, not a small annoyance.
What has to work without a connection
Offline logging only holds up when the essential information is already on the device. If every action has to ask a remote database what a record is, the feature stops at the first dead zone.
A local copy of the collection
Your release details, notes, and the fact that you own a particular pressing need to be on the phone before the spin begins. This counts most when several editions share a title, cover art, or catalog number. A useful entry is not just Kind of Blue. It is the copy of Kind of Blue on your shelf.
A queue that survives
A spin logged at 10:42 p.m. should still be there if the app closes, the phone restarts, or the connection stays down until tomorrow. Pending events should be sent as they were recorded, not recreated from memory.
A stable identity for each event
Each pending spin needs enough information to stay attached to the right release. Without it, a later sync can create duplicates, attach a play to the wrong edition, or flatten distinct pressings into one generic album.
A clock you can trust
Offline logging uses the device's time. A wrong time zone or clock gives you a history that is right in content and wrong in order, which you only notice when you go back to revisit a week, a trip, or the last time you checked a record's condition.
Logging offline is not the same as syncing offline
These get bundled together, but they are different jobs. A spin can be logged with no connection. Syncing your collection with Discogs, refreshing prices, and anything else fetched from elsewhere needs a connection at some point. The fair expectation is not that every part of a collection app works forever without the internet. It is that the thing you are doing right now is not thrown away because the internet is missing.
Most collectors will happily wait for a market value to refresh. Waiting to record a record that is playing right now feels backward.
Spinstack is built in that order. After the first sync your collection is stored on the device, so you can browse, search, and log spins with no connection, and iCloud catches up when you are back online. There is no Spinstack server in the middle: your spin log lives on your devices and in your own iCloud. A tagged sleeve works the same way, since the Tap Card opens a copy's pressing, grades, and play history entirely offline.
The trade-off: a clear handoff
Offline logging has one unavoidable cost. Until it reconnects, the app cannot confirm that a spin has reached an outside service. For a while, your local history is complete and its outside copy is pending.
A good app makes that state clear without making you manage it. You should not need a notebook of pending spins, a memory of what to resend, or a worry that tapping twice made two entries.
Duplicates are the usual failure. They happen when someone logs a spin offline, sees no sign that it is waiting, and logs it again after reconnecting. They also happen when two devices record the same session. The fix is not to make offline capture fragile. It is to give every event a stable identity and reconcile it carefully. When a service does reject a scrobble, the app should say why; in Spinstack a scrobble Last.fm refuses tells you the reason and can be sent again with the artist and title corrected.
Manual logging still earns its place. No automatic method always knows whether you flipped the record, replayed one side, or put on a different pressing with near-identical artwork. The record on the platter is the authority, and the log should leave room for what you meant to record.
Build a spin history you can trust
The habit is simple: log the spin when it happens, connected or not. Later is where good collection data goes missing.
Log the exact release in your library, not the first matching title. If you are comparing pressings or watching how a particular copy wears, this is where accuracy counts. A Goldmine grade and the condition notes behind it belong to one physical record, and so does its play history.
Your log serves your own memory first. Sending it to Last.fm, or sharing spins with friends, is a separate decision you can make afterwards. If you want the Last.fm side set up properly, see how to scrobble vinyl listening sessions to Last.fm.
This is where offline support stops being a checkbox. It protects the small facts that make a collection personal: the late-night pull, the record you came back to after months away, the copy you checked after spotting a mark in the groove.
A connection should add reach, not permission
There is nothing romantic about poor reception. The point of offline scrobbling is that the app does not ask a network for permission before it recognizes a spin. Your records are already there, so your history should be too. Log the side, add the note while it is fresh, and let the sync happen when it can.
Questions collectors ask
Will my spins reach Last.fm if I logged them with no signal?
A scrobble can only be delivered once the phone is connected again, so expect the Last.fm copy to lag behind your own log. The spin itself is recorded on the device when you log it. If Last.fm turns a scrobble down, Spinstack shows the reason and lets you send it again with the artist and title fixed.
What stops working in Spinstack when I am offline?
Anything that has to talk to another service: signing in to Discogs, syncing the collection and wantlist, marketplace listings, and fresh price data. Your collection, spin log, wantlist, condition scans and the barcode scanner's local matches keep working, and sync picks up on its own when you reconnect.
Why do I sometimes see the same spin twice?
Usually because it was logged twice: once offline, then again after reconnecting because there was no sign the first one was waiting, or once on each of two devices. Check the log before re-entering a play, and log a session from one device rather than both.