Why MOMENT builds its own MomentSoundEffect
2026-06-05 product-development note focused on sound engine and iOS native shell. MOMENT keeps speed high while locking ownership and product-quality boundaries.
Decision
On 2026-06-05, the priority is sound engine and iOS native shell. This is not housekeeping. It is boundary work that makes MOMENT behave like a more dependable product. The sound engine track moves spatial tone, tails, and realtime listening checks into the product asset layer. The iOS native shell track keeps Swift screens and OS adapters as execution layers rather than decision owners.
Execution
- Main surfaces: sound engine, iOS native shell, Rust Core.
- File axis: `.vscode/settings.json`, `Flutter/moment_ops_desktop/lib/features/home/presentation/models/home_nav_item.dart`, `Flutter/moment_ops_desktop/lib/features/home/presentation/pages/ops_home_screen.dart`, `Flutter/moment_ops_desktop/lib/features/moment_sound_effect/presentation/pages/moment_sound_effect_lab_page.dart`, `Flutter/moment_ops_desktop/macos/Runner.xcodeproj/project.pbxproj`.
- Keep implementation speed, but avoid leaving temporary product judgment inside the UI shell.
Product Bar
The value is not the raw amount of work. The signal is that UI polish, Rust contracts, sound experiments, and data boundaries are compounding in the same direction. MOMENT moves quickly while building a structure that can survive the next platform and the next version.
Next Bar
The next change is judged by user-facing calm: playback should feel immediate, transitions should stay quiet, and each product decision should have one owner.