ePub support, Palm support, and Sony support.

Once those are added, you really need to put in some kind of “central repository” which would allow publishers and authors to upload their books for sale under contract and subscribers of your service to retail those books. You will find a lot of smaller publishers don’t want to, or cannot be in retail business due to other business dealings. A repository supporting the above formats and allowing subscribers of your service to retail those books for a standard cut would be a major boost to your business.

In the eBook business, typically a 45% cut goes into the retail end and 55% returns to the publisher/author side. If you supported all of those formats and structured the business correctly, you would find some publishing houses would allow you to be exclusive source for some of their titles. This would boost your subscriber base.

Definitely a relevant comment.

Yes, we have been very careful targeting and limiting our data formats. One reason is that we know most publishers have only PDF or mostly PDF. I think the self-pub folks are a bit ahead of the game here, because they don’t have huge backlists or production pipelines to change.

We have also seen that devices are moving more and more to full web access, and PDF support is a big issue with people buying devices. It really came home one day when we discovered that we had iPhone support without building it.

We also have very high standards about content functionality. We did PDF with much of the power of the XML systems we used to build as consultants, and so we want to make sure that any efforts in other formats will enhance the system, and especially meet our hard requirement to keep it usable by non-coders.

So keep an eye on us, and remember that anyone can make a PDF, and we can deliver its content to any browser.