A one-click product is not easy because it has fewer buttons. It is hard because every hidden decision becomes a default. If the default is wrong, the user has no way to recover. For BGM, the default should match the most common job: make usable instrumental background music quickly.
Instrumental should be the starting point because background music usually sits under something else: voice, footage, conversation, store ambience, or gameplay. Vocals can be offered later, but they require different prompt logic, lyrics, and quality checks. Treating vocal and instrumental generation as the same workflow creates bad results.
Duration should be presented as usefulness rather than a marketing number. A short public MP3 is enough for many users, while longer private tracks and high-quality masters can become premium features. The wording should not shout duration; it should focus on getting a usable BGM fast.
License should be visible before generation. If free tracks become public, users must know that clearly. The trade is simple: free public tracks help the shared library, and paid private options can serve people who need exclusivity.
Good defaults are product taste. They let non-experts get useful results without learning the system. BGMFREE should keep the front screen calm and move complexity into the prompt engine, quality settings, and publishing workflow.