Like I said before the new hiscore is going to be revolutionary and something not yet done.
I did say that it will have cool features and design, and just recently I watched this small documentary on design, these words came up so many times: “simplicity” and “functionality”. These word gave me a new horizon when coding the interface and realised, its not how cool the feature work, but it is how good it work.
When coding this morning, I kept making it simple at first and made it work “right”, the way it needs to work. The hiscore will be hopefully up in a few weeks. We will take aboard 2-3 BETA users. Side comment: no its not an ajax app that starts as beta and never gets out of beta. The beta testing will test for bugs, functionality, and understandibilty. If i get at least 1 PM asking on how to add, there are 2 reasons, the beta user is quite dumb or I made it too complex.
What i am looking in a beta tester?
#The ability to report back any errors even the small ones
#A guess of what might have caused the error
#Taking full advantage of the system
What am i doing atm?
Well i am mostly working on the DB structure and how it is going to interconnect with each other. I am also going back to that “1 class a day” move to keep the work doing. I will try to get fk4 and b3f to start working on utility classes and remote scripts.
The main worry atm, is can i keep the quality as high, and get it done in time?
