One of the most fantastic things is the feedback you get from the BdJ netizens. Ordinarily, when a person with a particular problem appears at your site from Google, they are probably looking for an application to help them, with the deliberate emphasis on “an” – it doesn’t matter if it’s your application or someone elses, so if yours doesn’t fit the bill, they hit the back button and move on.

On BdJ, it’s subtly different – because it’s your application on offer, they are looking for your application to solve their problem, and they are not shy about letting you know if there’s an issue or something they don’t like. Listen to the feedback – it’s invaluable.

Bits du Jour is also a great way to stress test your operation, everything from your installation to your store front – if there’s a problem, there’s nothing like a massive increase in traffic to show it up. It’s worth emphasising that using BdJ is not about the money – it’s about getting a bit of money – but mainly it’s about getting a lot of traffic and customers compressed into a 24 hour period.

Some of my observations:

Installation

I use ClickOnce for all my deployment. I like it primarily because it means I can push out updates and have the clients update themselves with no action required on the part of the user. A few users experienced problems with the installation. After digging through some of the issues, I had one persons installation time out. I had one person whose installation was hanging and one who was inexplicably seeing a 404.

• The installation time out was caused by an ultra slow connection from someone in Tanzania. Whilst I have nothing against people in less well connected countries, my focus is inevitably going to be on countries like the UK, US, Canada, Australia etc. I make the tacit assumption that if you’re on my site you’re using broadband.
• The hanging installation was caused by a machine that refused to install the .Net framework. This persisted even when the framework was downloaded straight from Microsoft, so there’s not much I could do about that. I’m not about to start offering support for the .Net framework.
• Didn’t manage to get to the bottom of the 404, noone else was seeing it.

Runtime Errors

• One user was having a problem because the software couldn’t get write permission to a part of his user profile that he absolutely should have access to. The fact he couldn’t did make me wonder how any other software was working, but I sent him a registry patch to move Home Document Manager’s data folder which got him moving.
• Another user installed the app but it wouldn’t start. I’ve not figured this one out yet, but I suspect there will be a wider problem that I can do nothing about.

Activation

When customers make a purchase, they are emailed a serial number which they enter into the app – the app then calls my licensing server and they are sent a license file. This is one of the parts that I was very pleased with. There were no issues with the activation at all.

One person said they weren’t going to buy because I used online activation, but that’s one person in 14 months so I’m not too worried.

Summary

All in all, a very worthwhile experience and very positive feedback from the vast majority of customers. PDF Scan Pro comes on BdJ in around a week, it’s less mature than Home Document Manager, but seems to have had better traction, so we’ll see how that goes.

It’s been about 10 months since Home Document Manager made the transition from project to product. Looking back on those 10 months I can level a couple of criticisms at myself; the main one is that I haven’t iterated aggressively enough. The other is that I’ve ignored some customer feedback because it didn’t gel with my vision of where I wanted Home Document Manager to go.

Something happened in the last month that has injected a bit of pace into my development. I started considering a closely related, although entirely seperate product. Where HDM is a desktop document management tool, the new product was an advanced PDF Viewer/Editor/Annotator.

Part of the dance that micro ISV‘ers do when conceiving a new product is to evaluate competition, see what they do, see what they don’t do, see if they alleviate the particular pain that you’re trying address, and why, or why not. In short, we try to find our Unique Selling Proposition. I looked closely at a number of big names in the document imaging and PDF worlds, products like Acrobat Professional, Abbyy Finereader and the like. Not only did I find my USP within minutes, I’ve found a wealth of new user interface ideas and major bits of functionality that would slot right in to Home Document Manager.

I’m already a decent way through coding for the new product and have had so many a-ha moments for version 2 of HDM too.

Choosing WPF was a mistake. I love WPF. I work for Microsoft writing WPF. But for this particular project, it was the wrong call. The new project I’m writing uses Windows Forms. It’s been a while since I did WinForms, but my WPF experience is illuminating my UI architecting in new ways. I also really don’t miss the WPF cold start times. I’m certainly more productive using WPF, but let’s face it, in the B2C world, your customers really don’t care about that. Version 2 of HDM will use WinForms.

I haven’t paid enough attention to minimising the clicks my users have to go through in order to perform common tasks. This was immediately apparent when reviewing the competition for my new product, so version 2 of  HDM will have a much improved UI.

The deployment mechanism I use for HDM (ClickOnce) has its advantages. I can update end user installs easily, but serious B2B is a struggle because of the lack of Proxy support in ClickOnce. I also fell into the self signed ClickOnce bootstrapper trap, which effectively brought iterations of version 1 of HDM to a premature end. Bog standard installers from hereon-in.

One of the things I have to consider is whether or not to bring two such closely related products under the same umbrella on the same website. This has obvious advantages for marketing and SEO, they are both paperless/PDF/document related products.

A lot to mull over, but for me, speccing and developing a second complimentary/related product seems to be a good thing so far. I know the arguments about laser-like focus for micro ISVs, and I’m hoping that I’m not stumbling into a heffalump trap. But having two related products, particularly on the same website, should add credibility, and the 2 products can also have a beneficial effect on each other. Time will tell.

p.s. I’m writing this on Christmas day only because I’m standing in the kitchen with our latest edition (Eli Benjamin, 6 weeks old) strapped to my chest while I wait for the turkey to cook. Happy Christmas everyone.