Read the full PeerClock Metronome manual
Version, devices and scope
PeerClock Metronome plays a regular click and shows an animated conducting pattern. Use one device for individual practice, or open the app on several devices on the same local Wi-Fi network to share timing and playback controls.
This manual covers PeerClock Metronome 1.1.0 (build 13), using PeerClock 0.4.2. The public version was checked on November 15, 2026. It requires iOS 17 or later on iPhone, or iPadOS 17 or later on iPad. The App Store listing also lists Apple Silicon Mac and Apple Vision compatibility; the touch instructions here describe iPhone and iPad, and do not establish testing on those other platforms.
Your first practice session
- Open the app and set a comfortable device volume. Allow Local Network access if you want to synchronize with other devices.
- For a steady-tempo exercise, open Auto Tempo, turn off Increase tempo automatically, and tap Done.
- Drag the large BPM number upward to increase the tempo, or downward to decrease it. Select 4/4 from the row below.
- Tap the circular triangle button. It changes to a square while playing. Follow the clicks and moving dot.
- Tap the square to stop. When peers are connected, this also sends a stop command to them.
For your first group session, connect everyone before starting, wait for the synchronization display, and let one person operate the controls. A regular-tempo start follows the shared beat grid: the first audible click is not a guaranteed count-in or beat 1. Listen for the stronger downbeat before entering.
Connect several devices
- Install a compatible version on every device and connect them to the same local Wi-Fi network.
- Open PeerClock Metronome on each device and allow Local Network access. Leave all devices stopped during setup.
- Wait for the peer count and Synced status. The count represents other discovered peers, not a roster with their names.
- On the device you will operate, choose the tempo, meter and Auto Tempo setup, then press Play.
- Confirm that every device is playing the intended pattern before starting the exercise.
Discovery is automatic using Bonjour. There is no Host, Join, pairing code, IP-entry field or room selector in this app. An internal clock reference is chosen automatically; musicians do not have to select a master.
A device arriving after playback has started is not guaranteed to receive the current playing state and settings immediately. To include it reliably, stop the group, wait for synchronization, check the intended settings and start again from the operating device. Rejoining is also a reason to recheck the whole group.
Practice with Auto Tempo
Auto Tempo increases speed after complete bars, then continues at the target. Stop playback, tap Auto Tempo, and enable Increase tempo automatically. Use the stepper buttons to set:
Read synchronization status
- Standalone: no peers are currently counted; local practice remains available.
- Searching…: peers exist but the app does not currently show a synchronized clock state.
- Synced: the clock library reports a synchronized state.
The adjacent ±x.xms number needs careful interpretation. In this release it is calculated as half of the reported round-trip network delay. It is not a measured difference between the audible clicks, a measured residual clock offset, or a guaranteed error bound.
The automatically selected reference device can show ±0.0ms because its reference quality is reported as zero round-trip delay. That does not prove perfect alignment of every speaker. Use the status and count to diagnose connection state, then listen to the actual outputs. A brief transition while a device joins, leaves or reconnects may require the group to settle and restart.
Advertising, permissions and privacy
The reviewed release is free with advertising. It has no purchase screen, subscription, Restore Purchases action or paid ad-removal control. An interstitial can appear after every 3 locally initiated stops when an ad is ready. A remotely received stop does not increment that counter. Availability varies.
Who processes data, and why
Hakaru Hirose provides the app and uses Google services for advertising, usage analysis and stability diagnostics. Google AdMob can process device identifiers, advertising interactions, IP addresses and diagnostic information to deliver and measure ads. Firebase Analytics handles usage events and app/device information; the app also logs tracking-authorization status and advertising/consent errors. Firebase Crashlytics handles crash reports and associated installation/device information to investigate faults. These services can contact external servers; local clock synchronization does not make the whole app internet-free.
Permissions and choices
Local Network permission enables nearby peer discovery and communication. The App Tracking Transparency (ATT) request concerns tracking and access to the advertising identifier (IDFA). You can refuse it and still use the metronome. Change it in Settings → Privacy & Security → Tracking; refusing tracking is not a switch that disables all advertising or diagnostics. See Apple's tracking controls.
The app requests consent information through Google User Messaging Platform (UMP) and asks it to show a consent form when required. The displayed choices depend on the service's regional and account configuration. Respond to the form if it appears. Version 1.1.0 has no separate in-app privacy-options screen for reopening that form, and no analytics or crash-reporting switch. Contact support about choices you cannot access. The UMP documentation describes the service; its full recommended settings are not all exposed by this app.
Location, audio and saved settings
The app does not request GPS/location permission or record microphone audio. Advertising services may nevertheless infer a general location from the IP address. Auto Tempo settings are stored locally; synchronization exchanges timing and control data between local peers, not recordings. If you email support, your message and email address are available to the recipient for handling your request.
Consult the Google Mobile Ads data disclosure, Firebase privacy information and App Store privacy disclosure. This guide does not establish an app-specific retention period or promise deletion on uninstall. For privacy, retention or deletion questions, contact hirose@hakaru.net.