[WYSIWYG] Ability to switch to markdown editor

Thanks for reaching out and sharing your thoughts on Quire’s transition to a WYSIWYG editor. We understand that this change may be challenging, especially if you preferred the full Markdown support in our previous version.

Our aim with this update is to create a more intuitive and user-friendly writing experience for everyone. While full Markdown support won’t be returning, we acknowledge its importance and are working on reintroducing some of the most commonly used Markdown syntax in the new editor.

We truly value your feedback and welcome any suggestions on how we can enhance the editor to better suit your needs. If there are specific Markdown features you rely on, we’d love to hear about them as we continue improving the experience.

@vickyp Is there any timeline for this? The current editor is disruptive to our workflow and the list of bugs that we uncover is only growing.

Hi Peter,

Currently we're working on fixing the bugs as fast as we could, while keeping optimizing the new editor as our priority.

Unfortunately, we cannot promise a clear timeline when we will finish optimizing as it's an ongoing project here at Quire.

Please know that we're doing our best to provide a better experience at the earliest convenience.

Your previous editor was working great, if you would just add an option to use it, we would be able to finally get back to good user experience. Why do you need to expose us to a broken user experience for an unpredictable amount of time if you have a good solution available?

For me at least, markdown-native typing was a feature not something to be fixed. A wysiwyg editor that recognises some markdown keypresses isn't really the same thing.

Is there another editor that makes you believe that it is possible to combine WYSIWYG editor and markdown one, while providing a good user experience? The only editors that come close are ones that treat markdown as primary - e.g. Obsidian. While there are many nice features in your tool, it seems like reinventing text editing is huge task and unlikely to provide a good experience for all on a medium term.

So while you keep trying, it would be good to have something which provides the only functionality that many of your users need - markdown editor.

I will also add that I am very disappointed by this change. As a frequent single backtick (`) user, the new process (a mouse movement to select the text, a mouse movement to open the ... sub menu, a click, a mouse moment to select the Code option, a click) compared to the old process (a single keypress) is a significant UX downgrade. Please readd the option to use markdown input directly.

Hi Peter,

Thanks for suggesting Obsidian. I will pass this feedback to the Product Team for further discussion.

I think even for new users, many will prefer the ease of use of just typing markdown as you go rather than a WYSIWYG editing experience.

I feel like there's a misunderstanding happening somewhere in the product team that markdown is bad and needs to be replaced for some reason, but it's actually an excellent editing experience because it's fast, everything is text so you can process it easily when using the API, and it's well-integrated and readable even outside the tool. It's also commonly used and compatible with content in many other places. It matches editing in successful products like GitHub and GitLab, and many other issue trackers and content management systems.

@vickyp Do you have any insight on this? Current editor is disrupting our work on a daily basis, why can you not just allow us to switch to the old one?

Hi Peter,

We are sorry to say that we will not revert back to support full Markdown. We can add more Markdown syntaxes to the new editor, but reverting back to full Markdown is not on our roadmap. Thank you for understanding.

Disappointing news, but thank you Vicky for keeping us up to date with your decisions - I do appreciate that.

Hi Peter,

I'm sorry to hear that the new editor still isn't meeting your expectations. Could you provide more details on what you mean by "behaving in unpredictable ways"? This information would help our team investigate and resolve the issue more effectively.

Regarding keeping this thread open, we would rather our users can create separate feedback for separate bugs, instead of putting everything in one long thread. It would also help us manage better.

Hope you understand.

The new editor is still really bad, it behaves in unpredictable ways, which is exactly what markdown editor addresses. Could we not keep this issue open to see if it gets continued community support?

Me and others have reported tens of issues, however with each new fix there are new things that are broken. We have other things to do than working as a QA on this perpetually broken editor.

Me and others have reported tens of issues, however with each new fix there are new things that are broken. We have other things to do than working as a QA on this perpetually broken editor.

Hi Peter,

We're sorry that you feel that way. Unfortunately, without a specific bug report, I am afraid that we cannot step in and help with the bug resolve. We'd like to debug and fix the issues that our users have. Please feel free to create another thread to let us know the bugs that you are facing. We're sorry for the inconvenience.

This task is about a specific request - having the ability to switch to a markdown editor, as it existed before.

Regarding this request, I am sorry to say that we cannot roll back to the Markdown editor as I mentioned earlier in this thread. As it is a final decision from our team, I am afraid that in the near future, there will not be any changes. I am sorry if this is not the outcome that you have hoped for.

Ok then, will continue looking out for alternatives to Quire which include a markdown editor.

This task is about a specific request - having the ability to switch to a markdown editor, as it existed before. The only reason for a long thread is that you do not acknowledge it as a legitimate need that your users have.