Reading offline

Books don't need Wi-Fi, and neither does capturing.

When you're offline, an amber banner appears and the capture screen tells you plainly: You're offline. Speak anyway. The capture is saved on your phone and sends itself when the connection returns: on app open, when you come back to it, or within about half a minute of reconnecting. Nothing is lost.

Opening Ruxpin offline or in airplane mode keeps you signed in, and we renew your sign-in once the connection is back. While offline you can still record and write captures, but what is already in your record needs a connection to load, and says so with the same amber note. Adding a source works offline too: it sits in your Library marked Sends when you are back online, you can file entries under it straight away, and it goes up with them when the connection returns. Anything that asks the AI needs a connection: Rux, Search, your reader portrait, Make, and an artifact from Create. Each shows the same amber note, without trying, and comes back when you do.

An entry keeps the day you actually spoke it, not the day it finally sent. So an entry captured on a flight on Monday and sent on Wednesday sits under Monday in your record, and Monday still counts towards your streak. Entries that sent before this change keep the day they landed, since their real day was never recorded.

The queue waits for one other thing besides a connection: your OK to send thoughts to the AI service, given once on the Ruxpin uses AI. screen. If you tapped Not now there, a capture sits safely on your phone with a Waiting for your OK card, and Review and allow asks again. Nothing is sent, and nothing is lost, until you say so.

If a capture looks stuck

Anything still on your phone shows at the top of your Library as a small card, One entry waiting to send (or however many). Tap it for the list: each row says what it is (Voice and its length, Written, or Upload), when you captured it, and why it is still here. Waiting to send means it is between attempts; Waiting for a connection means you are offline; Will try again shortly means our end was slow; Sends after today's limit resets means you reached the day's capture limit; Waiting for your subscription means your free month ended before it could send, and it goes the moment you subscribe. A row that reads Sending, with a spinner, is on its way right now.

A capture that keeps failing on a good connection stops by itself after eight goes and stays on the list as Stopped after 8 tries, or with the reason; a silent recording stops after one. Try again starts it over. It only shows online, since offline the capture sends itself. Swipe a row left to delete it; Ruxpin asks first, because a recording deleted here is gone from your phone too. If one keeps failing and you cannot see why, contact us with roughly when you recorded it, and we'll look.

Occasionally a row reads That took longer than expected. It will try again. That one isn't your connection: it means transcribing or filing the capture didn't finish in time at our end. The recording is safe on your phone and goes back in the queue by itself.

If it couldn't be saved at all

Rarely, a recording can't be written to your phone at all, usually because storage is full, and Ruxpin says so: That recording couldn't be saved to this device. There's nothing queued to retry in that case, so record the thought again once there's room. A typed thought stays in the box, so you can send it straight back.

A thought you are still typing is kept too: leave mid-sentence or lose it to a crash, and the words are back in the box next time. A recording in progress stops and saves itself the moment you leave Ruxpin for the app switcher, a call or Siri, and if Ruxpin gets closed, it opens on that entry next time.