Musou: appropriate maturity depends on the job

Musou began as a mobile web application rather than a native app. That reduced cost and complexity while giving real users a way to test the member and coaching workflows. It was enough for what the team needed to learn at that stage.

The content system faced different demands as it grew. A small movement library could begin with hand-entered content. Hundreds of rows, duplicates, inconsistent names, and exposed video links made that approach harder to maintain. The team added import tools, update-and-insert behavior, name normalization, multi-category support, private storage, and temporary viewing links.

The required maturity changed because the operational requirement changed. Scale, privacy, and repeatability justified more capability in that part of the business while other parts could remain simpler.

---