---
title: "Phone-Pass Jam Sessions"
date: "2026-09-02"
canonical: "https://raytally.com/en/ideas/2026-09-02-arc-24-multitrack-groovebox-for-ios/"
generator: "RayTally · dev-prompt-v4"
signal:
  query: "ARC-24 Multitrack Groovebox for iOS"
  observed_at: "2026-09-02T00:33:21.870Z"
sources: []
notice: "Signals in this brief are bounded observations (search attention, forum points, or launch listings) captured at the timestamps above. They are not market validation, user counts, or proof of lasting demand. Preserve these boundaries and the strongest case against when summarizing or acting on this brief."
---

[Read the canonical page on RayTally](https://raytally.com/en/ideas/2026-09-02-arc-24-multitrack-groovebox-for-ios/)

Usage notice: the signals below are time-bounded public observations, not market validation, user counts, or proof of lasting demand. Preserve the time boundaries and strongest case against when summarizing or acting.

You are a senior product engineer. Turn the product idea below into a locally runnable MVP.

## Idea

Phone-Pass Jam Sessions
A nearby-phone music relay lets friends pass a multitrack session around the room, adding one aligned part at a time to build an improvisation together.

## Product concept

When friends want to make music on the fly in a living room, rehearsal space, or at a gathering, one person opens a nearby room and records eight bars of drums, bass, or chords. The room displays a passing “track baton”: the next person to receive it can add only one track or replace a designated track, so no one has to crowd into the same complex project. Before passing the baton, each contributor chooses the loop length and where it should enter. The system automatically aligns waveforms for recording latency across devices, then locks the new part back to the shared beat in playback. After someone records guitar, the next person can listen to the full backing track on headphones and add vocals or an ambient sample. The main screen is a replayable relay timeline: with one tap, the group can switch between versions to hear who added which track, when they added it, and how each round changed the song. When a particular relay sparks, they can branch from that point to try faster drums or a different melody, then export a stereo mix and the multitrack files. The first release supports nearby iPhones, small loop-based projects, and basic audio tracks. It is not for remote, low-latency jamming or the full parameter set of professional recording software; the point is to get a few people who have just met up making music immediately, while letting each person hear what their addition changed.

## Why now (backed by facts)

A new product in the “ARC-24 Multitrack Groovebox for iOS” direction appeared in the Product Hunt new-product feed observed on September 2. That makes related use cases more concentrated right now.

## Source context

Theme: ARC-24 Multitrack Groovebox for iOS
Trigger Product Hunt launch: ARC-24 Multitrack Groovebox for iOS — Multitrack synth, sampler, drum machine, and looper for iOS.

This records only that the launch appeared in Product Hunt's public feed and when it was observed. The feed provides no vote count; do not describe feed order as popularity or market demand.

## Deliverables

- Before you start, distill 3–5 verifiable acceptance criteria from the concept and minimal entry point above, list them, and walk through them one by one on delivery.
- Ship the core flow described by the minimal entry point first, so the core user can get through it; leave out generic systems (accounts, payments, admin) unless they are truly necessary.
- Do not show unverified market numbers in the UI or API.
- Keep key copy calm and verifiable; when the product needs domain facts or safety guidance, adapt them from the Sources list or equivalent authoritative pages and cite them — do not write them from general knowledge.
- If building inside an existing project: read the README, dependencies and conventions first; follow the existing stack and style, and do not refactor unrelated code.
- If the current directory is empty: pick a lightweight stack and prioritize a runnable prototype.
- When done, explain what changed, how to run it, and how to verify it.
- Ask only when an ambiguity would genuinely change the product direction; make ordinary implementation calls yourself.