0 Members and 1 Guest are viewing this topic.
How professional can one make a calculator game? Discuss.
6: Having the program run out of the box. It's far too common for me to try to run a program, only to find out that the author was using data not contained in the program. All data necessary to run the program should be included in the download.
10: Have something to distinguish your program and make it unique. Don't write a quadratic solver unless it's freakin' 3D.
Here are a few additional tips I can share based on my own calculator and professional experience:Build smart software. Smart software make extensive (but never read) documentation useless. Smart software make the user feel he has been using it forever even the first time. Smart software subtly suggests. Dumb software impose constraints.A screen that adapt what it shows based on previous use is smart. A preference setup that reset to the startup values after a crash is dumb (I'm sure you know one).make sure of the quality of what you build. Test often and extensively. Track the features of the game, identify reproducable test steps, learn when to re-run them for regression testing. Look for automated testing and build custom tools to make it possible, the time invested will quickly be profitable to the quality of your work. Version control may also be of great help to track changes and understand regressions.streamline your release process. This is a prerequisite to frequent releases (and thus users feedback). A release cycle includes building, testing, packaging and uploading. Simple custom scripts will often be enough, but you may also have a look to well-known tools that make the job easier such as Make, SCons, Rake or Gradle. If you can't automate the process, try at least to reduce it to a simple and systematic manual procedure.promote you work. An excellent game will become excellent only when people know it and believe it. Share early screenshots and demos, build roadmaps, announce important releases where users will ear them. Know what makes your work unique and tell the world.And always let the users drive you. Track feature requests and discuss them extensively. Make bug fix your priority: make it clear what information you need for the diagnostic, and take the time to reproduce them on your side (users aren't stupid, they are just not developers). Never let workarounds become the way to go.