Shortly after WisCon, I decided that I wanted to be able to work with my Dreamwidth journal on my iPhone. An iOS app seemed like a natural thing that should exist in the world and, conveniently, I know how to make one.
Sadly, I was quickly impeded by the state of the existing API. The API was designed in another age: back before Rest/JSON, and at a time when people expected “LJ/DW clients” to be desktop apps that’d download all your entries for off-line reading. There are some glaring omissions from the API (and it’s certainly… old-timey).
But, hey, it’s open source, no? I mean, I suppose I could send them a pull request. True, I don’t really know Perl and find that LAMP development is about five times harder than it should be. But, hey, minor stuff.
Over the summer, I started talking to some of the folks at Dreamwidth about this, and that started me into conversations about a new Rest/JSON API and whatnot. But progress on that front has been slow. Which I get. They have their own priorities, and some weirdo from the Internet is pestering them with, “hey, if you added an X I could make you a Y.” I just think it’s a Y that’s interesting.
A few days ago, I was hit with another urge to work on the Dreamwidth iOS app, and I built out a quick app that implements some of the basic functions. I can login, see my recent entries, view some basic profile information, and post a simple entry. That’s not nothing.
But I’m still stuck with those API limitations that seem to prevent me from really making this thing useful. Le sigh.
Mirrored from Under the Beret.
This entry was originally posted at Dreamwidth, where the colours are brighter, the conversation wittier, and people will mail you a free puppy when they like what you've written.