Testing, testing, 1-2-3. Posting this from Ulysses 18.5 into my WordPress.com [atomic site] blog.
Yes, it works!
In yesterday’s post, I declared my love for the Ulysses app. I really have been testing several writing and word processing apps for a few years now and this is The One for me.
Since the beginning, I liked Ulysses so much that I didn’t even try to see if I could torrent it. I bought a license up front for each device they offered the software on. Then, when they switched to a subscription-based license model–a cavalier move for a small software company at the time–I stayed on as a user. Even though the app didn’t do everything I wish it could for my writing, I wanted to support the team to see where they would take their work.
It’s just important for me, personally, to keep all of my writing in the same sandbox. The process of switching back and forth between this editor and that application, or copying text from one place to another, or trying to figure out which file of everything was the right one, or the nagging fear of losing the work (it’s 2019!) or accidentally publishing it…
…the administrative tasks around writing were making it easy for me to let my writers’ block win. Ulysses has since been with me for: academic writing, editing articles, work posts, an early start on my memoirs, and (yay!) blogging.
But I still had to do all my work on my laptop or paper.
Then about a month ago, Ulysses sent out a newsletter titled, “Hacks for Mobile Writing.” Since introducing support for iOS 13’s text editing gestures, it’s been easier to get my thoughts out on my phone.
While these gestures are Apple’s features, Ulysses’ design doesn’t get in the way. Meaning, you can actually use them, and build muscle memory across your tools and apps so you can use them even better. It’s not a parity experience, but this is a great example of how sometimes that’s not the best. The outcome I want is to write; not to feel like I’m on my laptop [so that I can write], or to feel like I’m on Platform [so that I can write].
There’s an analogy here somewhere about modeling this type of interplay between software application and OS and the web. If one day everything is in the browser (an OS for the web, if you will), how might we support users instead of each one of us re-building the wheel just because we can? Should we even? And if so, should it be up to a company, or a neutral-ish party, like the web standards crew? Does an early version exist somewhere already (that isn’t a walled garden)?