DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to show a listening indicator during voice input with Thinking Orbs

Display a pausable listening orb that freezes when recording stops.

Who it is forA developer adding voice input or transcription to an app who needs visible feedback while the microphone is active.

The problemUsers do not know whether the app is still hearing them, and a static icon gives no sign of live activity.

The outcomeA listening orb animates while recording and freezes on its current frame when recording stops.

What you need first

  • Xcode 16 or later with Swift 6, on a Mac
  • An app targeting iOS 17+, macOS 14+, tvOS 17+, watchOS 10+ or visionOS 1+
  • Node, only if you want to run Scripts/differential-sweep.sh (inferred from the README, which says the script runs the original engine under Node)

Steps

  1. Add the Thinking Orbs package to your Xcode project using File > Add Package Dependencies with https://github.com/haplollc/ThinkingOrbs.
  2. Import Thinking Orbs in the view that handles recording.
  3. Place ThinkingOrb(.listening, isPaused: !isRecording) where the indicator should appear, with isRecording set by your recording state.
  4. Optionally add speed: 1.5 to the same call to change the tempo as a multiplier on the tuned speed.
  5. Start and stop recording on a device or simulator and check that the orb freezes when recording stops.

Prompt for your agent

Using the ThinkingOrbs repo (https://github.com/haplollc/ThinkingOrbs), add a ThinkingOrb(.listening, isPaused:) indicator bound to the recording state of <target voice screen>. Return the SwiftUI view code and confirm the orb pauses when isRecording is false.

Caveat. The indicator only shows motion. It does not record or transcribe audio, so your app must provide the recording state.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page