Dance2It explores what happens when your movements become musical commands: create rhythms, guide the beat, shape expressive sounds, and conduct a virtual orchestra.
Concept and planned experience · not a product launch announcement
One phone. Rhythm, expression, touch, and motion.
The product concept combines a gesture engine with a musical timeline, touch controls, spatial instrument selection, tactile cues, and optional visual worlds. The core ideas are documented; implementation and release scope remain subject to validation.
Move up, down, left, right, twist, or tilt to trigger instruments or shape effects. Gesture intensity can change volume and accent strength.
Core product direction
Beat by Beat: use intentional movement to trigger beat-aligned musical segments, or adapt continuous playback to your cadence.
Core concept · modes under study
Combine thumb-friendly touch with movement to arm actions, lock an instrument, trigger beats, or adjust expressive parameters.
Core product direction
Explore music that follows your walking or dancing cadence, music that guides your motion, or movement-based rhythmic layers.
Proposed experience modes
Point your phone toward virtual instrument sections, choose one, lock the selection, and direct expression or dynamics.
Core product direction
Feel section boundaries and confirmations; imagine your performance in 2D, 3D, AR, or on an external screen.
Haptics core · advanced visuals future
These browser interactions illustrate the planned controls. They do not read phone motion sensors or generate production-quality musical audio.
Different gestures can map to kick, snare, hi-hat, clap, synth, or effects. Recognition should distinguish intentional movements from noise, avoid duplicate triggers, and support sensitivity calibration.
Try selecting a direction. The control panel will show an illustrative mapping and intensity.
Strict concept: each accepted motion advances one beat-aligned segment. No motion means no advancement.
B3 Strict is a movement-triggered approach to musical progression. B3 Flow is a continuous-playback approach that adjusts tempo and phase to the user's movement rhythm.
Real implementations must preserve musical continuity around vocals, sustained notes, missed beats, and changing cadence. These modes are design proposals, not a claim of finished playback quality.
The B3 Pad is a large on-screen control that can trigger a beat, confirm a motion, arm an action while held, lock an instrument section, or expressively control sound with touch location.
Three potential ways to connect music and movement—whether dancing, walking, running, or performing rhythmic exercises. Actual cadence recognition depends on where the phone is carried; a watch could be an optional input later.
Music adapts to detected movement cadence with smoothing and pitch-preserving tempo adjustment.
Music establishes a target rhythm for the user to follow during movement.
Motion overlays rhythmic accents and effects while the underlying music continues.
Imagine a semicircle of instrument sections. Rotate your phone to select a section; hold the B3 Pad to lock it; then use gestures or tilt to influence its musical expression.
The initial design favors relative angular selection, not absolute physical position tracking. Each instrument needs separate MIDI or audio stems for meaningful independent control.
Distinct tactile cues could indicate entry, exit, boundaries, centers, and the currently selected virtual instrument region.
Use haptic feedback to confirm B3 Pad lock/unlock, beat triggers, musical accents, or loss of calibration confidence.
The phone is the controller and the source of truth. Visual presentation can evolve independently, from a simple on-screen map to animated 3D or supported AR displays.
Selectable instrument regions, highlights, controls, and feedback.
Musicians and groups reacting to musical dynamics and events.
A miniature orchestra viewed through a compatible device camera.
A possible larger-scale, headset-based performance scene.
Render a predetermined scene on a computer or connected screen.
A longer-term virtual concert environment concept.
All symbols are conceptual diagrams, not screenshots. AR requires compatible hardware and displays; it does not project images physically into a room.
A key architectural principle: the phone interprets sensors, touch, selection, and musical state. An external display receives meaningful events, not raw phone coordinates. This lets presentation evolve without changing the musical interaction model.
Native sensor adapters, filtering, gesture classification, and configurable thresholds aim to avoid false triggers.
Orchestra control needs MIDI or independently controllable stems; ordinary stereo tracks do not expose each instrument.
External renderers consume semantic events and state snapshots, while the phone remains authoritative.
Configure gesture sensitivity, handedness, gesture-to-sound mapping, percussion or synth packs, and virtual instrument layouts.
Capture a performance as a timeline of musical and control events, then replay or render it later. Sharing and video export depend on content rights.
Conductor Mode manipulates existing MIDI or multitrack arrangements; Composer Mode could generate and trigger musical phrases later.
Possible future controls for arranging sections, musicians, venues, stage styles, and scenes, including grouped instrument control.
A compatible smartwatch could improve wrist-based gestures or cadence recognition for certain activities; a watch is not required.
Large touch targets, simple calibration, optional AR, haptic guidance, and hands-light experiences help reduce unnecessary screen attention.
The specification outlines a staged plan rather than a confirmed release schedule. The initial goal is a responsive, understandable musical interaction before investing heavily in animation or immersive AR assets.
Gesture recognition, sound injection, basic B3, beat analysis, and touch interactions.
Relative instrument selection, calibration, B3 lock, smooth controls, and tactile navigation.
Timestamped event streams, replay, external renderer sync, and reconnection.
Onboarding, content, QA, analytics, acquisition and retention validation.
3D musicians, immersive presentation, headset experiences, and custom venues where justified.
Not automatically. Retiming and manipulating commercial music can require appropriate formats, APIs, and rights. Some streaming catalogs restrict playback manipulation. The audio source strategy is unresolved.
No. Independent instrument control needs suitable MIDI data or separate stems. Source separation is a possible future method but has quality, processing, and rights limitations.
Both are intended platforms. Device sensors, audio latency, vibration, and AR support vary; exact launch scope and graceful fallbacks need testing.
No external hand-tracking device is planned for core interaction. AR is optional; the phone remains responsible for sensing and control.
This page illustrates the October 2026 product specification and proposed roadmap, not a released feature checklist. Interactive browser controls are demonstrations of interaction ideas rather than the actual mobile music engine.
We're shaping a movement-controlled musical experience and exploring its most compelling uses in play, dance, exercise, and expressive performance.
For product inquiries, testing interest, and potential collaboration, contact Aktingtoons Media.
Email info@aktingtoons.com ↗This link opens your email app; it does not submit information to a server.