A Typora-like editing mode (edit and preview at the same time)

Sad +1. Maybe choosing Mobile Apps is for business concern, since Mobile Apps will make Sync feature more useful. Anyway, if the mobile app could become a powerful capturing tool to collect ideas, it would still be a big improvement.


I also agree that mobile is low priority. We can already use various md editors like 1writer or IA writer etc and sync with Obsidian. Typora functionality is a top priority for many users.

1 Like

And mobile is a top priority for many other users. Your mileage may vary. That’s why there was a poll. :wink:

No idea how wide the outcome disparity was but the devs gave time, thought and a chance for the community to weigh in before deciding which priority to go with.


Maybe you should look at this website-

1 Like

I think what was meant by low priority is that the mobile app isn’t that high of a priority for some users in terms of demand for their needs, not what the roadmap says.

On a brighter side, the longer the devs delay WYSIWYM mode for us, the stronger the dopamine rush will be when they do release it lol


Yes, mobile is far less important for me. I can use IA writer which uses CloudKit so whatever note I take on IA writer will show up on my desktop and then I can easily put it in a vault. In fact, I have hazel automated so that IA notes go into an inbox folder in my vault. Anyway, I am grateful, and I was aware that a complete rewrite of the editor was on the roadmap as I check the troll board regularly. I think the developers are doing a great job by delivering weekly builds for insiders. Bravo.

It would make sense to move unrelated (to title) issues (about rendering front-matter and about scrolling speed) mentioned in original post A WYSIWYM (Typora-like) editing mode into separate feature requests. Maybe @Konfido or @moderators could do it?

+1, its the only thing i think is missing.

It’s in short-term guys!


+1, its the only thing i think is missing.


As a workaround you could use : Typora like custom CSS
It is not perfect but was enough for me to switch day to day editing to Obsidian. The main weakness of this workaround is for tables, the rest is pretty strait forward.

What do people thin of “In-place” (as in Zettlr and bear) instead of “WYSIWYM”?

1 Like

Can you describe what that means?

I believe that means the markdown formatting gets rendered in the editor while still showing the markdown code…

So an h1 heading is rendered as a heading, but still displays as “# Heading”

That’s said, Bear is going full WYSIWYM with their new editor:

I prefer this approach myself, and think obsidians approach will be perfect- three modes: plaintext, preview and WYSIWYM. I’ve seen the devs say that is the plan


+1 - I really just only would need images being displayed inline but a more viewable presentation during edit would be great.

Essentially I am agreeing with the “preview mode with edit feature”.


Typora is great but it is a jarring experience with all the content hopping around when cursor enters a link or image, the markup suddenly appears, and the current mouse-cursor position is now invalid. This is much higher “cognitive load” to me.

Bear’s Panda editor is a much better target to aim for. For instance, put the URI markup in GUI elements rather than the face-assaulting Typora expansion. Hopefully, the markup can seamlessly accessible to the preview through well design UX.

Recent topical post from the old guard (guy who invented markdown):

the whole point of it is to provide a syntax where the most common HTML tags for prose can be replaced by simple punctuation characters that are meant to be visible to the writer.
~Daring Fireball

As others have mentioned, WISIWYG should be in addition to the purist markdown experience. Personally I would still want the URIs hidden as they really just get in the way. When do you need to see the massive gibberish link (that’s longer than the sentence it is within) to the webpage you are writing about? Especially if you can view said URL with a keystroke.



I use Typora regularly, and have done for the past 3 years, but have not had this experience. If anything, the “cognitive load” is less than with Obsidian because with the latter you have to keep switching between Edit and Preview.


Yeah, don’t get me wrong Typora is great and I’ve used it on/off for a long time; it’s my default app for .md. I tried others like Caret, MoU, Byline, etc but always went back. I just think, if Obsidian devs are building an equivalent, that they could aim higher. Have you played with the Panda alpha for instance?

Also, how do you deal with the problem I mentioned in Typora? If you have two links next to each other and near an image it can be frustrating to change middle links title for instance. Perhaps there is something I’m missing.


I don’t have experience with this, I have not used links and images like that.

Another avenue to consider is something like the Gutenberg editor in Wordpress. This works on two fronts: it’s a web technology and would allow for future Obsidian editor features that are outside the normal scope of markdown. The embedded query block comes to mind as an argument for this. Could also open the doors for plugin devs to create “block-level” plugins.