First of all, I would like to say hi to everyone!
This is a step in the right direction for Infopop but I would like to list a few suggestions:
1. Coding:
The most critical shortcoming of UBB.classic is the code base. It is messy, cluttered and unorganized and although Charles did an excellent job refactoring and enhancing it, it still suffers from it's original code base.
I believe that the development team should spend a good time designing the software because the more you design now, the less you have to code later. Maybe something like MVC design pattern should help. There is no need to rush.
Also, some competitors fell into the trap of using OO syntax with function-oriented approach. So be aware
BTW, are you guys considering using PHP5 features?
2. Features:
Despite the fact that UBB.classic is outperformed in terms of features and performance by many competitors, it has features that non of them has: professional-looking interface, balanced feature set and an easy to use Admin CP. I believe that the new product should concentrate on having a good balance between features and usability.
3. Price:
As Gladius said, the price should be reconsidered as most competitors are cheaper than the current price points of UBB products.
