At the Channel level, we're going to provide you with a Creator's text area where you can place anything you want. You could put credits, dedications, forwards, personal bio, etc. You could also put any license info on that page, and list them per Episode.

Interesting suggestion! I think our initial thoughts were to:

a) be friendly to the reader. Provide them with the fore-knowledge of when to return or expect the next piece of story.

b) keep an on-going "tether" to the reader. Not to "cut-them-loose" into an unknown time vacuum, but provide anticipation through a clear expectation.

c) build a TV series mentality, where the next episode appears with some regularity. e.g.: Look for a new episode of "Probable Cause" every Monday.

But I hear you! More options would be good. Please post this suggestion to the Suggestions forum also!

In the Simulator, the Countdown Time is currently set to appear at 6-seconds. This is incorrect. It should appear only if a delay exceeds 20+ seconds. Otherwise you will see the ellipsis. This should be fixed in the Simulator by tomorrow (12/7). :-)

Just as a singular data point:

In my (& Karrie Hyatt's) police procedural story "Probable Cause," I initially had the thesis that I didn't want my reader to wait around too long in-between major story beats, so I picked a rather arbitrary time delay of 2-hours for an "overnight" delay. My "in-story" delays were also artificially short (just seconds). I thought, "who wants to wait around for a whole 5 minutes" while I "drive" from the warehouse to the nightclub. Not terribly logical, but expedient.

So I went through and did another editing pass for timing this weekend. (Isn't it always interesting what you see after you've left your story simmering away on it's own for a bit?!)

Anyhow, I ended up being quite a bit more "aggressive" and putting in much more "realistic" delays for "travel" time and during suspect interviews. I ended up using the knowledge that anything over 20-seconds would display the app's Countdown Timer, so I was OK with having much longer dramatic pauses (as the reader would plainly see the wait time.)

When "driving" from place to place, I now used 30-50 minutes. (Who can get anywhere in LA in just 30-45 minutes these days. Unless you're visiting next door.)

I extended my "overnight" wait times from 2-hours to 10-14 hours.

I also am trying out a tempo thing, where if I have a longish delay (say, after driving to a new location) I give the reader a bunch of dialogue to read at a fairly quick pace. I might slow it down a tad here and there, but I avoid putting in one long delay right after another one. Seems only fair, right?

Also, I'm thinking that a long delay is a perfect time for a mini cliff-hanger. Brutal, yet effective.

What do you think?

Just an interesting "editing" angle: As I go through the stories, I'm trying to be quite careful with pointing out typos because they may be, in fact, intentional!

BTW, some of you have already used the phone's "auto spell-check" and "unique typing personality" to humorous and effective ends!

The Countdown is supposed to appear if there is going to be any delay longer than 20-seconds. Otherwise, you get the elipsis thingie.

The current 6-seconds is way too short and will be changed.

Control + Mouse down, then drag to a last node, will do a copy/paste of a single node

Control + SHIFT + Mouse down, then drag to a last node, will do a copy/paste of the node and the tree below it.

Note that I can't Copy/Paste into a Node somewhere already further up a tree though.

In the next update, we should have the ability to designate who's talking per text line, within a single node. This should make having back-and-forth conversations a lot easier and faster. Trees should look a lot cleaner and be easier to follow, since you could "compartmentalize" a conversation. Nevertheless, it's a good suggestion.

I ended up binge watching the entire series. :-P

BTW, did you catch the Movie?