Disappointed in DT4 lack of writing/note taking features

I’ve downloaded the beta and have been exploring it, but, to be honest, I was expecting more significant updates to the text editor. The changes feel basic. I was hoping for modern text editing or note-taking functionality—features like collapsible sections, a unified markdown/WYSIWYG editor, and easier ways to insert tables or images. These seem like reasonable additions, especially considering it’s been five years since DT3’s release (September 12, 2019).

After years of frustration with DEVONthink’s text editing capabilities, I’ve shifted most of my note-taking and writing to UpNote (currently $39.99 for a lifetime license on the App Store). I’d love for DEVONthink 4 to adopt similar text-editing features.

For document organization and archiving, DEVONthink remains unmatched. However, adding robust writing and note-taking tools could make it even better and appeal to a broader audience. Right now, it feels like UI/UX design isn’t a priority, as though the development team is entirely composed of engineers.

My dream app would combine DEVONthink’s robust organizational features, the text-editing capabilities of UpNote, and the image management tools of Eagle. Now that would be incredible!

8 Likes

Your opinion is noted, but as has been often discussed, DEVONthink is not a bespoke note-taking application. It is not trying to compete with Typora, iA Writer, Bear, etc., nor are they competing with us. Document creation is added as a convenience, not a core focus of the app.
Also, there is a ton more than text editor work in version 4, and not all of it is AI-related.

10 Likes

What would also be more incredible is to add PDF annotation capability that does not suck

Which means…?

4 Likes

Agreeing with @analogue_man, this is not particularly helpful or useful. Care to elaborate?

1 Like

DEVONthink is my primary note-taking and writing app. I am a professional writer and researcher.

8 Likes

Thank you for your response. It helps me make informed decisions about which tools to integrate.

I want to clarify that I don’t envision DEVONthink as a bespoke writing app, where writing is its primary focus. Instead, I see robust writing tools as a complementary feature that enhances its document management capabilities. This way, DEVONthink can remain true to its core strengths while offering users a more comprehensive experience.

Food for thought :yellow_heart:

2 Likes

Indeed and bear in mind we are listening, even when things don’t always come to fruition for all requests.

1 Like

The gap for me, is the ability to create markdown links to documents and files within DEVONthink’s editor and the loss of that when using an external editor. That is not a fault of DEVONthink, and I “can” still create the links, but the auto-complete suggestions for links is useful within the app.

Maybe DEVONwrite will bridge the gap :wink:

Yes. Disappointed in that after 5 years of development, DT4 beta comes out and is still using the same old PSPDFKIT with its very counter intuitive behavior. Here is an example. I draw a rectangle on a PDF page and an annoying popup widget appears immediately that I don’t really care about. I have to hit ESC every time to get rid of it. If I really wanted to change the color of my rectangle, I can surely double click on it when/if I choose to, thank you very much. The same applies to other annotation shapes… Yet another annoyance is the inability to view page thumbnails…

The point I am trying to make here is that for simple annotations or viewing of PDF page thumbnails, I shouldn’t have to use external PDF apps. I would be a very happy camper if you could provide the same PDF annotation and viewing functionality on MacOS that you’ve already provided on the iPadOS version. Thx

If this was simple to accomplish and also didn’t incur any extra costs to us (which would logically be passed on to you), it would have been done already.

5 Likes

Like in Tools > Inspectors > Content > Thumbnails or where exactly do you want to see page thumbnails?

3 Likes

The next beta will include the possibility to disable this (unless it’s required, like in case of link, text & note annotations).

2 Likes

Just like the iPadOS implementation. I tap or click on the thumbnail icon in the toolbar, the PDF page disappears and the page thumbnails appear.

Perfect. Thank you!

Agree!

Hi Christian, I get what kmn meant about the popup - it is annoying :slight_smile:

I found the update of the MD text editor reasonable or modest.

it works well enough in customizability to use it for some people who craved for a WYSIWYG, in that it allows a semblance of CSS looks. the customizability of font, line height, text width and color, plus link/image preview is something that basically ‘works’.
so, I am happy about that.

still, I think calling it a “WYSIWYG” is a bit euphemistic.

though, it could easily get there IMO, given current state.

what is still missing is something akin to Ulysses editor turning, or at least a way to

a) allow for separate font setting for (at least) headings

b) a way to hide or decently colorize the MD markup, that would already come pretty close to WYSIWYG.

things like foldable sections, I think would bring into the luxury department.
not against it. but I understand Devon’s hesitations to provide such a full-blown editor experience, as this really seems special task & market.

… but, it would be nice sometimes if they would take labels, like WYSIWIG a tack more serious, now they have come to this. :grinning_face:

the fact that they have come here, though, seem remarkable – also in light of prior discussions, which were marked by real tangible deflection from the sentiment of big parts of the user base.

so there is progress, even if there is not perfection :grinning_face_with_smiling_eyes:

Actually the options were renamed in version 4:

And the appearance of images & links is pretty much WYSIWYG.

hey @cgrunenberg

the post was to both acknowledge the progress and substantially react to some user remarks & evaluations, like the one of @iHuman (the OP)

but:

yes. I agree in a way.

besides my personal acknowledgment of (unexpected) progress, I just wanted to additionally point to the “in a way”, which in your reply translates to “pretty much WYSIWYG”

it reflects my opinion & feel that ‘WYSIWYG’ is a holistic concept. either something is 'WYSIWYG, or not (really). of course there can be something like ‘elements of WYSIWYG’.
maybe some people even can subscribe to the notion of ‘more’ and ‘less WYSIWYG’…

but, I think aside from that part, some people (like me) might be wrongly aligned as to expectations when reading announcements like
“Edit Markdown documents with the improved WYSIWYG editor".
that is also bec the bar for MD WYSIWIG by now is one where people don’t expect to see the the MD-markup right on par w the content (or at least where this is optional or by choice).

so I just wanted to point to ambivalent labeling as to the description (in announcements) and general ambivalence involved. like expressed in adjectives like “pretty WYSIWYG”.

the general background of course, contributing to the (perception of) ambivalence and different, sometimes irritated expectational horizons, is a deeper discussion.
and I don’t want to repeat it here, but point to it, bec I think it comes to play when reading (again) of different ‘umderwhelmed’ users as to MD-editor:

DT has this slightly schizophrenic approach of being an environment for notetaking (w/ hardcore users regularly declaring this is where ‘they do it’) and providing a sufficient environment for PKM, journalling etc (plus a lot of explicit scaffolding for that, like templates, editor settings, inline gen-LLM etc), but then it kind of makes a habit of pointing to ‘we are not a notetaker’ whenever non-coding people articulate their wish (need?!) for a modern note-editor experience in the light of this.
in that light, talking of an “WYSIWYG editor” while simultaneously dragging feet about any acknowledgement of user input pointing to increasing need/demand for a ‘modern’ editor-experience just brings about threads like this one.

to give another example of the way I think the ‘schizophrenic’ situation for a larger part of DT-users (excluding those lovers of the original way’ of code-writing) builds up:
DT now in a great move has brought versioning. then, versioning only works when writing in DT. – so, anyone who wants to make use of this great affordance for writing/note-taking is thrown back to an improved but still slightly antique MD-editor (UX-wise). at the same time anyone pointing to painpoints in MD-editing is answered by protocol: ‘Go use a dedicated editor’.

… I think it’s these things that ultimately produce threads like this, produce a cohort of users underwhelmed by the MD-editor – and very strange discussions in the forums, often.

again, I think the new MD-editor is decent, it’s progress, and actually just good enough for me to seriously think about some overdue switching of my textworks into DT. then, there remain ambivalencies, as to the (non-)match of affordances and sometimes talks about DT and the real level of the “WYSIWYG” editor experience.

so, I wanted to reflect both sides & sentiments. something I rarely seen done in the discussions here…