There’s a bit more going on under the hood than what is apparent in the UI: the file format (the “schema”) that Manuscripts.io uses (which is already available openly actually – we’re going to update it + add lots more repositories of open source code imminently) is 100% compatible with Manuscripts for Mac.
Manuscripts for Mac 1.x has as one of its file formats a “manuscripts-json” file, and we are going to be very soon extending that file format in the 2.0 beta version to a “project bundle” format that includes that kind of a JSON file + figures etc attachments that are present in the manuscript.
- This new file format will be the format that Manuscripts for Mac and Manuscripts.io on the web can exchange, as import / expot actions (it’s very similar to a
.manuscript actually, just in a more text editor readable format).
- Manuscripts for Mac will also seamlessly synchronise your Manuscripts projects with Manuscripts.io (including collaboratively between multiple users), allowing you to write on the offline and entirely 100% privately, and on the web when you want (actually the browser client actually also supports offline writing).
Now, regarding timeline: we are really focusing on getting the core editor component and collaborative editing functions 100% awesome first because when those are super reliable we are really 99% there with the editing experience of the new Mac app as well (the copy & paste, undo behaviours for example are all shared in this new version between the desktop and web versions, and whilst they’re already really better than what Manuscripts 1.x provides, we have many bug fixes and missing features to add).
We’ll probably start distributing really early copies of the desktop app relatively soon (certainly hoping by the end of the year, but this is not a promise but an engineer’s guess!) and quite honestly we are going to listen to feedback first before committing to release schedules (we want to get this right, and not rush).