This year I’ve been trying to reduce my use of social media, and of my phone. These two goals go hand-in-hand: if I don’t have social media apps on my phone I am less tempted to keep looking at it, checking for something new. It also means that when I get a notification on my phone, it is more likely to be a message (via SMS, or messaging apps) meant specifically for me, rather than some low-information notification to increase my “engagement” with a social media app. Together, this is a way for me to keep believing in the Internet, and ensuring that I’m using it, rather than the other way around.
Another aspect of reducing dependence on social media is investing more in my own, independent publishing platforms: this blog, and my website. For the time being at least, this blog runs on WordPress.com which has apps for all the common platforms.
Part of achieving the above is posting not just longer articles and links to this blog, but also pictures capturing memorable moments in my day-to-day life. This is something I’ve been using Instagram for, but since I took the Instagram app off my phone, I wanted to see if I could use the WordPress Android app to do the same.
The answer is: sort of. I initially posted yesterday’s Sunday Selection post without the image. I then wandered out to one of my favorite local cafes where I took the picture. But adding the picture to the post using the WordPress Android app turned out to be more troublesome than I was expecting.
First I added the picture to the post from my phone’s photo gallery, and updated it. Everything seemed to work, but when I checked the post, the image URL appeared broken. For some reason the app used a URL for local Android storage rather than the uploaded image URL. If I somehow interrupted the image upload or the post update, this wasn’t clear at all.
Second I tried to edit the post again to make sure the changes had saved properly. But when I exited the post editing screen without actually making any edits, the app designed to remove all paragraph breaks from the post. Luckily WordPress seems to keep a version history for posts, so I could go back to an older version.
Finally, I ended up deleting the image from the post, and then adding it from the WordPress media library (which had the proper uploaded version of the image) and re-publishing. This seemed to finally work.
So I managed to do what I wanted, but the fact that what should be a common use case was so buggy leaves a really bad impression. While I don’t want to go back to using other platforms for this, I’m now much less excited to use WordPress for this. For now, I’m willing to give WordPress the benefit of the doubt. Maybe this is a one-off use case, or these bugs will be fixed in future versions, but I certainly am disappointed.