Story of two writing interfaces
I love the writing interface for write.as platform. No-nonsense. It does what it is supposed to do. Plus, all the other options, though available, get out of the way while I write. Grammarly works as expected. The posts are auto-saved in an intelligent way. At the same time, I can also build a list of drafts while working on them. The word count is visible, not the character count, as with Micro.blog that hosts my main website.
That last point tells you about the priority of these two #platforms that are very similar, yet different in many ways. Micro.blog compares itself to Twitter; hence considers itself closer to microblogging (well, it's in the name). So the writing interface looks similar to the one on Twitter. Or, for that matter, most social media platforms. A bare text box that accepts Markdown text.
Write.as, on the other hand, calls itself “a place for focused writing”. This shows with the editor. Every time I use it, I want to write long. I can't say the same for the text box that Micro.blog provides. It's suitable only for microblogging.
Sure. Given the platform's well-supported APIs, a list of clients already supports publishing to Micro.blog. So this is not an issue that many may face. However, most are only written for the Apple ecosystem, something I am not part of.
I love almost everything about Micro.blog. But I hate its writing interface and love the one provided by write.as. No surprise, then, that I am publishing most of my thoughts here.
This leaves me very confused. Which is my primary platform?
Have something you'd like to respond with? Send me a note via email, and let's start a conversation. You can also follow me via RSS.