Document Suno browser handoff decision
This commit is contained in:
+10
-4
@@ -19,8 +19,10 @@ instructions for Suno.
|
||||
4. User reviews and manually edits every generated component.
|
||||
5. Project versions are saved.
|
||||
6. User presses **Send to Suno**.
|
||||
7. The app opens Suno and fills the appropriate fields. It does not
|
||||
trigger Generate.
|
||||
7. The app opens the Suno Create page in Custom mode and fills the
|
||||
supported title, lyrics and style fields. It does not trigger
|
||||
Generate. If a field cannot be filled, the app reports that result
|
||||
and keeps its approved text ready for the user to copy.
|
||||
|
||||
## Song Controls
|
||||
|
||||
@@ -92,5 +94,9 @@ Normal users cannot view or modify these rules in the initial version.
|
||||
## Initial Boundary
|
||||
|
||||
Suno remains responsible for music generation and playback. The macOS
|
||||
app prepares the project and fills Suno fields only. Generated songs do
|
||||
not need to return to the app in the initial version.
|
||||
app opens the browser-based Suno Create page in Custom mode and fills
|
||||
the supported title, lyrics and style fields only. It never triggers
|
||||
Generate. If Suno changes its interface and a field cannot be filled,
|
||||
the app reports that field and keeps the approved text available to
|
||||
copy. Generated songs do not need to return to the app in the initial
|
||||
version.
|
||||
|
||||
Reference in New Issue
Block a user