We have been fielding a lot of questions about CPO’s next version that is due out very soon. The work is still fast and furious here with a private beta release date of March 31 looming large. There are a few things that current CreativePro Office users should know as we finally enter the release phase of this long project.
We have decided to do a private beta release of CreativePro Office 2.0 on March 31 with a public release shortly thereafter.
This is an honest question and the answers are many. Mainly, the scope of work was much larger than anticipated. In retrospect, we may have tried to cram too many features into the initial 2.0 release. But, since version 1.0 has a pretty complete feature set, we knew we had to match and exceed that benchmark which I believe we have done.
Too many to list here but the ones we’re most excited about are:
Yes and no. CreativePro Office 2.0 will have a free option among several premium, paid options. We will release the official pricing structure very soon.
No. We are allowing a 6 month grace period after launch for existing users to migrate to a free or paid plan on version 2.0. If you decide that you do not wish to continue using CPO we will provide a data extract feature so that you can get your data out of the system and migrate it to another service.
No. Version 1.0 will not accept any new subscriptions after April 15. Existing users of version 1.0 will have 6 months from the public release date to migrate over to a CreativePro Office 2.0 subscription.
Yes, but it will be available after the public hosted release. The reason is that we have to do some tweaking to the self-hosted version to insure a smooth installation experience for the widest variety of users.
No, the price point of version 2.0 will be higher. We will release official prices within a week.
CPO has been developed to be as intuitive as possible to use. However, we realize that support in many forms is necessary for a satisfied user base. The forum and priority email (for subscribers) will be the primary means of helping our users find their way around CreativePro Office 2.0. Tutorials and help files will be built out as we see a need. For example, if we see that many users are having trouble with file uploads; we’ll create some help content around that specific issue. We are definitely going to create some comprehensive help content for the self-hosted, downloadable version though.
We have long fielded the request for different language versions of CPO. Our plans are to include over 10 translations in version 2.0. We already have the translations more or less sketched out but we will be working as much as we can with native speakers to fine tune the translations.
No but we have added over 45 currencies to version 2.0 and will add more at your request.
Our plan for CreativePro Office is to continue to integrate more and more features over time as this application becomes profitable. While we might not be able to give you a specific date for a specific feature roll out, be confident that we have many improvements in store for the future.
Thanks for reading. Please let us know if you have any other questions.
Discussion: 8 comments
Dave Bergschneider
Mar 25, 2010Will it be possible for the current CPO source code purchasers to get full premium access to the hosted version for a time being until the upgrade in May is made available?
Also, will the free updates or whatever be available for those whom have purchased CPO in the last 6-12 months be made available?
Good work guys!
Erjon Metohu
Apr 14, 2010When is the final launch date, because I know it's been getting pushed month after month?
Jason
Apr 15, 2010cristiane
Apr 19, 2010best,
cristiane
Andy Darnell
Apr 20, 2010Sarah
Apr 20, 2010Jason
Aug 20, 2010Heather Denton
Aug 21, 2010Thanks for the continued correspondence inquiring about the source code for 2.0. We understand that you are looking forward to getting that. I am sure that you understand that it's almost impossible for us to release source code for a product that is undergoing testing and receiving final touches. It would be a hassle for you as a user to have to continually patch the code to make it work as it is intended.
I appreciate the fact that you are hanging on, looking forward to this, and can assure you that the source code will be released, though not in keeping with the deadlines we originally anticipated. Your response to us has helped along the choice to avoid release dates in the future, since so many things can happen to change what we anticipate.
Hope you have had a chance to preview CPO 2.0 and like what you see.
Heather and Jeff