Installing PubCoder

I’m leaving for the USA in a while for a holiday, so been busy preparing for that.

Why this post about installing PubCoder?

In my last post, I determined the first of 10 heuristics/criteria for choosing a tool that helps you create and publish ebooks. When critiquing an ebook creation tool, I ask:

  1. Does the tool support effortless writing?

I can’t answer that question before installing PubCoder. Also, the installation process is a herald of the kind of interaction design decisions designers made about the rest of the application. So if I struggle to set it up, I’ll likely struggle to get into it.

I’ll be using PubCoder as a tool to create fixed-layout interactive ebooks that can be published on a variety of platforms. I suggest checking out Non-Fiction Fixed Layout eBooks from my mentors, eBook Architects to get a sense of how complicated it can be to make these kinds of books. Which is why ebook designers ask a hefty fee for making them.


Installing PubCoder: A “meh” experience

Here are the screenshots and my thoughts about installing PubCoder as comments. My verdict so far is that PubCoder’s installation process is needlessly complicated, requires an internet connection, and leaves the user without much guidance at first startup.

However! I did play with PubCoder after installing it, and am finding a lot of promising interaction design decisions which, I think, will prove it to be a powerful tool for creating fixed-layout or interactive ebooks. But that’s for another post.


1. Requiring access through your computer’s safety net, the firewall, makes installation difficult, but isn’t the developer’s fault. Most users should be familiar with this dialog, and know what to do. 


2. First annoyance, a random crash. Errors are hard to explain to users, and the reassurance that “you will be able to send a crash report” is fine, but still doesn’t help the user feel in control. Why not add an option to send a crash report within that error message?


3. Requiring users to sign in online all the time is an understandable security precaution, but it’s also an added step. The more steps it takes to install software, the less likely users will be to complete installation (totally anecdotal, not a rule that I know of). 


4. Do you really need all this information? If company isn’t required, why have that field there at all?


5. A decent captcha. 


6. The verification email was pretty easy. Yet another step, though. 


7. Alright, one month to go! 


8. Confirmation that you may have to be online at all times. 


9. All done! Time to look at example ebook projects.