| Do | Don’t | |----|-------| | Save relationship state per LI. | Force a single canon LI. | | Offer “friendship routes” for non-romance players. | Gatekeep key emotional scenes behind 24h timers. | | Allow replay of romantic chapters. | Use microtransactions mid-confession scene. | | Include a “memories” gallery (CGs, voice lines). | Lock the happy ending behind a paywall. |
A. The “Bite-Sized Beat” Structure
Each dialogue scene must advance either plot or relationship. Example:
Scene 1: Banter (flirt option) → Scene 2: Vulnerability (confide in LI) → Scene 3: Gesture (LI does something protective).
B. Tropes That Work on Mobile
C. Avoiding “Empty Choices”
Every romantic choice should affect future scenes, even in small ways (e.g., different dialogue on next date). False choices kill engagement.
Mobile games are played in 5–15 minute bursts. Structure chapters like soap operas.
Mobile technology has significantly changed the way people interact, form, and maintain relationships. Here are some key points:
| Do | Don’t | |----|-------| | Save relationship state per LI. | Force a single canon LI. | | Offer “friendship routes” for non-romance players. | Gatekeep key emotional scenes behind 24h timers. | | Allow replay of romantic chapters. | Use microtransactions mid-confession scene. | | Include a “memories” gallery (CGs, voice lines). | Lock the happy ending behind a paywall. |
A. The “Bite-Sized Beat” Structure
Each dialogue scene must advance either plot or relationship. Example:
Scene 1: Banter (flirt option) → Scene 2: Vulnerability (confide in LI) → Scene 3: Gesture (LI does something protective).
B. Tropes That Work on Mobile
C. Avoiding “Empty Choices”
Every romantic choice should affect future scenes, even in small ways (e.g., different dialogue on next date). False choices kill engagement.
Mobile games are played in 5–15 minute bursts. Structure chapters like soap operas.
Mobile technology has significantly changed the way people interact, form, and maintain relationships. Here are some key points: