edgeprod

Sorry about the re-paste from the other thread, but here's some thoughts on it:

I wasn't involved in the company when plans for that were announced. That was to be developed by the former coder.

When I bought the company, I spoke with Chio about what would be more beneficial to users -- developing a stand alone package that could post out to a variety of platforms (and, at the same time, removing the restrictions and allowing an "unlimited domain license" with it), or producing an update to the WordPress version of Autoblogger.

I think that it's a fairly unanimous opinion that the stand alone versions served the interests of our user base, and makes the most sense to concentrate development on now.

We maintain a user base of thousands of licensed domains for the WordPress version, but many HAVE moved to the stand alone.

We'll have to evaluate how many people still use the older version versus the newer in order to determine the feasibility of continuing development.

Chio and I are both of the opinion that there are things we'd certainly LIKE to add to the WordPress version, so it really comes down to A) how big is the user base still, and B) what's the commerical viability? Since we do not currently have the WordPress version for SALE, what economic factors drive a full-blown update for it, what specific features would we add, etc?

More likely, the major releases from Relink Software (at least in the NEAR future) will be the continued updates to the Autoblogger Pro Stand Alone platform, the Adult Empire Builder product (which performed well in beta, and would need to be stripped down completely, then rebuild to be viable in a retail enviroment), the Forum Autoposter (which works very well, but also needs to be rebuild and reskinned for retail), a CMS system (which is working on one of my sites), and a suite of ASP-based services for blog owners.

In the middle of all of that, if we DO determine there is viability/need for the update to the WP version of Autoblogger, we'll probably make some structural changes to it so that it can live a quiet life of semi-retirement.

I'd say the mix of support tickets for the "old" Autoblogger are about 1 out of every 30 or so versus tickets for the new Autoblogger. If you mix in the tickets for Bliggo and some of our other products, you're probably talking more like 1 in 150 or so. This says to me that most people are using it, are reasonably happy with what it does and where it is in its development cycle.

Remember, too, that we're at version 2.6 of the old version, which introduced a lot of new features, fixed a number of annoying bugs, and increased functionality across the board. We made quite a few updates during the life cycle already.

I'm talking out loud here, this isn't by any means the "official" statement on it, but I hope it answers some questions and provides some insight into where my head is at on our product lines.