What's new in 1.4.0: Push notifications You can now leave AudioSnap and we'll send you a push notification the moment your recording is transcribed and summarized — no need to keep the app open. Enable from Settings, or via the in-context prompt after your first recording. Localized in your language Notification titles and messages render in your selected language. Tapping the notification takes you straight to the recording. Behind the scenes A handful of robustness improvements: faster failure detection (e.g. when a recording is too quiet to transcribe), correct date formatting in non-English languages, and improved upload retry behavior.

What's new in 1.3.4: Reliable upload retries Fixed an issue where multiple queued failed recordings could retry at the same time and trigger a server rate-limit, blocking new uploads until the queue cleared. Retries now happen one at a time and recover cleanly. Clearer upload errors When an upload can't complete, you'll now see a clear message explaining why and what to do, instead of a blank screen with no information.

What's new in 1.3.3: Faster failure detection When a recording can't be transcribed — for example, silent audio or a file that exceeds the limit — AudioSnap now picks up the result immediately instead of waiting through a long retry cycle. The right action (Delete or Retry) appears right away. Home list reliability Fixed a rare crash on the Home list that could leave the screen with a runaway scroll. Recordings now render correctly regardless of state. Cleaner short-recording handling Tapping the record button too briefly (under 3 seconds, or before the microphone fully initializes) now shows a short "Recording too short" message instead of queueing a doomed upload that ends with a confusing retry banner.

What's new in 1.3.2: Reliability fix for long recordings A "transcription timed out" banner could remain on the recorder screen for long recordings (typically 15+ minutes) even after the transcript had loaded successfully. The banner now clears as soon as the transcript is available, regardless of how the backend delivered it. Clearer error messages When a recording can't be transcribed, the message now tells you why — too short or too quiet, too long, provider temporarily unavailable, or a generic processing issue. Each error has its own localized explanation instead of a generic "failed" message. Smarter retry behavior For recordings that can't be fixed by retrying the same upload (silent audio, files exceeding the recording limit), the action button now offers to delete rather than retry. Retry stays the default for transient errors.

What's new in 1.3.1: Reliability fixes • Fixed a "transcription failed" banner that could briefly appear over content that actually loaded successfully. The banner now disappears automatically as soon as your transcript or summary is ready. • Error states are now properly scoped to each recording — messages from one no longer linger when you open another.

NEW: Playback speed control Tap the speed pill on the player to cycle through 1× / 1.25× / 1.5× / 2× playback. Speed through long meetings, or slow down to catch every detail. Polished UI across the app A complete visual refresh — cleaner cards, refined typography, hairline separators between rows, and a calmer color palette. The Pro plan card got a glow, the recording timeline got connected steps, the recorder button is bigger and clearer. Smoother recording flow • Bigger, more obvious record button on the Record tab • Clear "RECORDING" indicator with a pulsing dot • Vertical processing timeline (Upload → Transcribe → Summarize) with a connecting line • "View Recording" waits until upload completes — no more accidental errors from tapping too early • Returning from a recording to the Record tab now shows a fresh recorder, not the previous confirmation Reliability fixes • Fixed false "still processing" errors when navigating to a recording before processing fully completed • Fixed blockquote readability in dark mode (Notable Quotes section) • Fixed text alignment, layout, and dark-mode contrast issues across multiple screens