Workflowy blog full#
Workflowy blog pro#

Workflowy blog full#

Jumping on the bandwagon while your inboxes are already full :P WorkFlowy on the other hand, is an almost a pixel-perfect beautifully designed functional and aesthetic tool. Then, WorkFlowy which already has achieved great WYSIWYG interface will go back steps to the more premiliminar, uncomfortable, and basic Markdown format? That makes absolutely no sense to me.ДЇor the ones who really like Markdown there is also Dynalist which is a WorkFlowy clone only that has a horrible design and a very ugly UI. Markdown is noisy, cluttered, and awful to read, and even worst, super cumbersome to edit when you try to change something you see in edit mode, then that item or letter or word will jump to another place when you want to to edit, is so frustrating and annoying!ДЄlso, consider that most Markdown editors like Obsidian are trying really hard to achieve WYSIWYG because their users continuously ask them to move from MD to a beautiful and functional modern editor to avoid dealing with the troubles of MD!. Please don't ever make WorkFlowy a Markdown editor! In list view these notes would always display rendered and expanded. When you click into the note it is in edit mode, and then when focus is removed it renders Markdown. Would you want a toolbar popping up every time you change text fields in WorkFlowy? I wouldn't.ДЄs Dmitry suggests above, I could see a new 'View' option for notes (like Boards) where the user could designate a note 'Markdown'. Slack's is pretty good, but it still requires an editing mode toolbar to make it work. There are hybrid implementations of WYSIWYG and Markdown, and they are getting better. Markdown is best suited for one big text area, imho. after all WorkFlowy bullets and notes are just a bunch of different text fields. Much of the 'flowy' comes from NOT jerking into and out of view/edit mode whenever you change focus. Markdown, by definition, is bi-modal with edit and view modes.

Workflowy blog pro#

IвЂ™m still a Pro user until the end of the year, so IвЂ™ll be watching it with interest.I've been fervently anti-Markdown (for WorkFlowy) since to implement it system wide would require fundamental changes to the way the WF works. Maybe the Workflowy team can improve on this front this blog post gives me hope. ThatвЂ™s such a comfort and a relief, coming from Workflowy. That hasnвЂ™t been true with Dynalist.Д«ut the biggest reasons I switched to Dynalist are that the developers are engaged with their users, they have a public roadmap of their development plans, and users have an active community where they can interact with the developers. When I used Workflowy, I found I was bringing my laptop home from work just so I wouldnвЂ™t have to deal with the Workflowy app. I havenвЂ™t had the same issues you have with the app.I really like the Dynalist app, and it was the big part of why I made the switch. However, that could be because IвЂ™m a new user whoвЂ™s still вЂњthinking in WorkflowyвЂќ as it were.

I also find IвЂ™m not really using DynalistвЂ™s extra features, which I was initially so excited about. There are a couple minor things that I really miss: the вЂњspring-loadedвЂќ menus on Workflowy bullets the new ability to drag bullets directly into other bullets. I really like it, but Workflowy has a simple elegance I miss. I recently switched to Dynalist as well, and like you IвЂ™m not sure if IвЂ™m going to stick around or not.