Perhaps I've Sold iA Writer Short 🤔

[Bmosbacker]

As a result of this decision, I decided to give iA Writer one more try. My reason for doing so was three-fold: 1) iA Writer just released improvements to the library, which make organizing writing much more manageable; 2) there is no subscription, and I already own it; and 3) to determine if my problem with iA Writer was due to design decisions that don’t fit my needs and preferences or if my problems with iA Writer are due to a lack of understanding how to use it.

Regarding the third issue, given the recent update, I believe that most of my problems with iA Writer may have been caused by a lack of understanding of how to use it properly.

For instance, I knew I could create and see a table of contents in the preview window. However, I did not realize I could turn scrolling off for the preview window. This is important because, on a long document, the table of contents in the preview window is not helpful if it scrolls out of view as you type. I discovered I could turn scrolling off for the preview window so that the table of contents remains visible as I work on a long document. This means the table of contents can be an always visible “outline” of my long articles. And, iA Writer is working on an outline feature.

Secondly, I was frustrated by how prominent the markdown syntax is. I still would prefer to have it fade into the background. However, I started using Focus mode while typing. This makes most formatting fade into the background so that it is no longer distracting.

As you can see in the screenshot below, I can see the table of contents as I type further down in the document, and in Focus mode, the markdown syntax is no longer distracting.

Additionally, I believe I can avoid exporting or printing my presentations. I will experiment with using preview mode on the iPad when giving a presentation.

If I can make iA Writer work for all of my writing and presentations except for book projects (in Scrivener) and formal reports (Pages), I will gain the following benefits over using Ulysses:

• No subscription
• Transferable “standard” markdown so I don’t lose proprietary functions when exporting from Ulysses.
• I don’t have to create a complex exporting/archiving workflow like I was attempting with Ulysses + DEVONthink.

I’m not prepared to declare that a writer will be my default app for most of my writing. I need to give this more time, but I am cautiously optimistic.

[alvinc]

You can refer to their blog articles which explain the design very well. Although their designs and functionality may not be for everyone, they know what is writing. Not just making things beautiful.

I remember Oliver studied philosophy? As a sociology graduate, I am glad to see humanistic technological development.

[brookter]

If you are still intending to index the files in DT3 for long term storage, be aware that – as far as I can tell! – their content block system (although a very neat idea in itself) won’t be understood by anybody but iA Writer, so you’ll either have to use standard Markdown for those elements, or export the files to Markdown in a separate stage if you want them to be rendered properly. I think that’s the extra step that you’re trying to avoid, isn’t it?

Content blocks are when you simply use the unadorned path of the image, file, etc. E.g.

image.jpeg "This is an image but only iA Writer can see it"

instead of

[This is an image that iA Writer and everybody else can see](image.jpeg)

[Bmosbacker]

@brookter

won’t be understood by anybody but iA Writer, so you’ll either have to use standard Markdown for those elements, or export the files to Markdown in a separate stage if you want them to be rendered properly. I think that’s the extra step that you’re trying to avoid, isn’t it?

It’s never as easy as it should be. I was not aware of that. But, I’ll continue to experiment, and if there is a standard markdown syntax, I can use that instead of content blocks, with the exception of the table of contents, I’ll give that a go.

[brookter]

I like iA Writer a lot and it has a lot to recommend it. I’d be happy using it all the time (apart from Scrivener) if it I didn’t find BBEdit’s text manipulation features so useful.

Essentially, I keep everything that isn’t in Scrivener in DT3/DTTG and edit short files in-app, resorting to the external editors:

• BBEdit when I want to make multiple changes over multiple files in one go using regular expressions
• IA Writer when I feel like a change.
• Typora, Obsidian, Emacs, and Ulsysses when I succumbed to trying them out again…

[Bmosbacker]

@brookter

Essentially, I keep everything that isn’t in Scrivener in DT3/DTTG and edit short files in-app, resorting to the external editors:

That’s an interesting idea, one I had not considered. I’m not sure that is what I want to do, but it is worth further thought given that I use DEVONthink for all of my research articles.

[brookter]

DT3’s editor has come a long way over the last couple of years. It’s obviously not as flexible or as cosmetically appealing as IA Writer, say, but it does the basics well, and in some cases better than IA Writer.

For example: your desire for quick navigation of headings in long documents is a built in feature as it displays a clickable outline by default:

The only reasons I don’t use it for everything outside
Scrivener is that they still haven’t included Typewriter Scrolling (despite my asking for it every year since about 2011 as Jim from Devonthink support who posts on here will attest as he’s been fielding the requests since then… ^[1]) and an inability to control the margins of the editing window. Other than those minor complaints, it’s more than good enough for daily use – it’s worth looking at the Help files under 'Markdown Documents` to see the full range of what it can do.

---

1. Just kidding Jim – I know how long the Wish List of Doom is… ↩︎

[bx987]

I have the same problem with DT3. For a while, I would enter returns at the bottom of the page to simulate Typewrite Scrolling. Eventually, I gave up. Now I use Ulysses whenever I need to write anything longer than a paragraph.

[Synchronicity]

@Bmosbacker

I was frustrated by how prominent the markdown syntax is. I still would prefer to have it fade into the background.

For all of iA Writer’s talk about the importance of writing, I think their heavy-handed rendering of markdown codes comes out of a programmer mindset.

For a programmer, the codes are the central thing. For a writer, the prose is the central thing, and markdown codes are mere markups intended to disappear from the final work. It’s okay to see them during the writing process, but in a fainter shade. They shouldn’t fight for attention visually with the words and punctuation the way they do in iA Writer.

[Tellerman]

I guess it depends on the nature of the content, but I’ve never thought about or been disturbed by a hashtag while writing. That the sentence doesn’t “sit” right, feels excessive or unnecessary/lacks rhythm or fails to convince me, on the other hand…. But when it does, life is good and the hashtags are a mere reference of literary excellence At least for some time…

[Bmosbacker]

@alvinc

they know what is writing. Not just making things beautiful.

I concur. I find myself nodding in agreement when I receive their blog posts.

[Bmosbacker]

One of the limitations for me is that, as far as I can determine, the TOC function is not available in the mobile version of DT. I frequently use my iPad for writing so I need near feature parity between Mac and mobile versions of my writing apps.

[brookter]

Yes, I think you’re right. It’s one of the frustrations that there simply isn’t any program which is perfect across both devices for everything you want to do… They all lack something here or there…

Having said that… I don’t know whether you’ve seen that the Scrivener developers have a new app in beta – it’s not as heavyweight as Scrivener, and it can use iCloud for syncing (the major complaint many have with Scrivener on iPad, it seems).

Full details are not publicly available yet and those of us who are beta testers are not allowed to discuss more than is already in the public domain, but…

Given your need for TOC, and outlining/better navigation, you may be interested in this section from the public announcement:

Not Scrivener then: something new. But not entirely new. I’d long been toying with the idea of an alternative, more minimal take on Scrivener. This was a chance to create an app pared back to hone in on the principles on which Scrivener was originally built:

1. Work on a long text by splitting it into smaller sections.
2. Use an integrated outline for an overview and easy restructuring.
3. View research alongside writing.
4. Export or print with the option of changing the document’s appearance.

(My emph.) Something New: Beta Testers Needed | Literature & Latte)

They aim to release Mac, Windows and iOS versions at the same time.

[Mathew_T_Mitchell]

Their webpage states:

Before the end of 2024, we’ll be launching a new writing app on macOS, Windows and iOS.

As a beta-tester do you have any reason(s) to believe this won’t hold? That is, pretty fair to assume this would be available before Jan 2025?

I tried signing up for the beta, but it seems they have more than enough people right now.

[brookter]

They (understandably) don’t talk about precise deadlines, because it raises expectations that can’t always be met. The latest (public) announcement was this, on the forum, from Keith, the developer six days ago (A suggestion for the LitLat team - #7 by KB - General - Literature & Latte Forums)

Yeah, we aren’t trying to be coy, it’s just that we know from experience that if we talk about things too early, it just causes frustration. The problem is that delays inevitably occur, so if we reveal a bunch of stuff and get everyone excited, and then say, “whoops, sorry, it’s going to be three months late”, people understandably get annoyed at having their hopes got up and the excitement abates.

So we’ll start talking about it once we know it’s nearly ready for release, which, as you note, will most likely be next year now.

A little later on the same page:

let’s just say that our commitment to releasing it on Windows, Mac and iOS simultaneously is the reason for the delay until next year.

Quite how long into the new year – they haven’t said, of course.

[Mathew_T_Mitchell]

Many thanks for this info. As they stated:

Yeah, we aren’t trying to be coy, it’s just that we know from experience that if we talk about things too early, it just causes frustration.

But they also made the announcement in October 2023, and at that time with a pretty precise release date. Essentially they hoisted themselves by their own petard. That said, I know making these statements regarding releases are hard. I’ll just assume it arrives whenever it arrives … likely before 2030. It does sound like a very interesting development though!

[Bmosbacker]

Yes, I did see that. I am definitely interested, but, and I don’t fault them for this, but it took forever for them to release the iOS version. I fear that it will take a long time before we have a good working version of the new Scrivener. I hope I’m wrong.

I should add, that the description provided sounds perfect for my use case. I am hoping they will release such an app at the end of the year or the first of next.

[brookter]

The issues with the iOS app were unfortunate, and largely out of Keith’s control.

If I remember correctly – if someone knows better, please correct me – they contracted a developer to write the app, who was unable to complete the job (because of family illness, I think, but I could be wrong), then another developer was taken on, and that also fell through. In the end Keith taught himself iOS programming to get the app done – thus reliving the beginnings of Scrivener, when he taught himself programming because nobody had written the app he wanted for his own novel. (He was a Primary School – which I think translates to Kindergarten in American — teacher at the time.)

Their reluctance to commit to firm dates is a result of that searing whatever can go wrong will experience, I think.

[Bmosbacker]

Yes, I’d read something like that some time ago. I was not criticizing, merely noting how long it took. Frankly, I am amazed and impressed with his work, especially if he taught himself programming. He is one smart “kindergarten teacher!”

[brookter]

I didn’t think you were criticising, but the story is remarkable and worth retelling, I think. I’ve always felt an affinity to Scrivener, partly because Keith’s story shows exactly the same talent, gumption, and perseverance that I don’t…