Support

Build your scene order

Create a story and add your own scene cards. Each holds title, chapter, beat, point of view, location, character names, a 1–10 tension rating, status, goal, conflict, outcome and notes. Use scene actions to move a card earlier or later, duplicate it or confirm deletion. Order is explicit; chapters are labels and do not alphabetically reorder the story. Search finds scene text; status and POV filters narrow the index.

Edit and review

Scene content can be edited until its status is Locked. Change the status and explicitly unlock before editing again. Status does not certify a complete or good scene. Rewrite notes use only these rules: an empty goal, conflict or outcome; Outline status; or a declared tension of 8–10. Missing-field notes rank ahead of outline-stage and continuity reminders; equal priorities retain narrative order. These are drafting reminders. The tension map plots your ratings in scene order.

People stores name, role, want and pressure notes. POV/location coverage counts exact labels entered on scene cards. Character names on cards are free text; deleting a character profile leaves those labels intact.

Save and restore

The Outline save/share menus offer four real UTF-8 file types. Markdown carries story premise, all scene fields and character profiles. CSV has one quoted row per scene and 16 columns, including narrative order, cast as JSON text and review rule names. CSV preserves literal text: import spreadsheet columns as text. JSON is the full portable story backup, with content, ordering, identities and timestamps. TXT is the current rule-based rewrite plan. Technical report labels remain English.

JSON imports always create separate story and record identities; existing stories are preserved. Imported story text and order are retained. The original iOS Codable-shaped scene array, or an object containing scenes and optional people, is also recognized for deliberate structured-data transfer. The iOS app only copies outline text and has no JSON-backup export screen; this does not provide automatic device transfer or plain-text import. Android and iOS purchases/storage are separate.

Save through Android Files to a destination you control. An external provider error can leave an incomplete external file; retry and verify it. Share opens Android’s chooser; delivery depends on the recipient app. Each share gets an independent cached copy. Clear cached shares can invalidate older links; it does not remove private stories or external saves.

Limits and recovery

12 stories, up to 128 scenes and 64 character profiles per story, within a 2 MiB UTF-8 portable-story limit and 8 MiB total private library. Import file limit 2 MiB; share cache 64 MiB. Scene title 120 characters, chapter 60, beat 100, POV 80, location 120; goal/conflict/outcome 4000 each; notes 8000. Up to 32 scene cast names, each 1–80 characters on a separate input line. Story title 80 and premise 2000. Character name 80, role 100, want/pressure 4000 each.

A save commits to the atomic private library before the visible model changes. If writing fails, the prior library stays and the editor keeps its draft. Cancel/discard are distinct. If the private library cannot be read, editing is blocked and original bytes stay in place. Save unreadable library exports up to 8 MiB of raw bytes; Retry opening library reads the file again after external repair. This is not automatic repair or a general power-loss guarantee.

Story timestamps use the device’s local time zone in the interface. There is no cloud sync and Android cloud backup is disabled. Uninstalling or clearing app data removes private records. Keep JSON backups you control. Deleting a story removes its private records after confirmation; independent external files stay.

Contact

maga40@naver.com · Gobling Company · Scene Card Writer Android 1.0.0(1). Include the visible error and version; do not send private manuscripts unless needed.