The iOS version of Aeon Timeline seems robust and full-featured; I can do almost anything with Aeon Timeline on iOS that I can on the Mac, with a few exceptions:
- Screen real estate is cramped on iOS screens, so it might take several screens of information to display what’s available on one screen on the Mac. Don’t get me wrong; the display’s neither crowded nor sparse, and there’s nothing missing, but you might have to tap a couple of times more to see all three of your story arcs, for example.
- Import and export options on iOS are limited—I suspect in large part due to iOS sandboxing.
- I can’t sync with Scrivener.1 For that, I have to get back to my Mac.
Nonetheless, since I do use Scrivener on both platforms, and have built a timeline for my Scrivener project in Mac Aeon Timeline, having Aeon Timeline on iOS is wonderful.
- On the iPad, at least, I can split my screen between Scrivener and Aeon Timeline. Thus, I can see all the information (dates, keywords, arcs, locations, tension) for my Scrivener docs that iOS doesn’t know about—while I’m looking at my Scrivener project. Even on iPhone, that data is now available even if I can’t have Scrivener on the screen at the same time.
- On iPad or iPhone, I can now actually edit that data, and it will get incorporated when I get back to my Mac, sync Scrivener with iOS Scrivener, and then sync Scrivener with Aeon Timeline.
- If you’re an iOS-only user, only titles, labels, and synopses would be synced anyway since you don’t have keywords or custom metadata. I’d suggest creating a timeline in Aeon from scratch, copying and pasting titles. You could still set up your dates, locations, arcs and tension in Aeon.
Thank you, Matt at Aeon Timeline, for this great little iOS app!
- Not syncing with Scrivener on iOS makes sense. Scrivener keeps the desktop project version largely unchanged on iOS, sequestering mobile changes in a special mobile area inside the project. If iOS Aeon Timeline starts messing with it, there’s a real possibility that it might create Scrivener sync conflicts. No one wants that. ↩