Divide By Zero Postmortem

Quick development time
Literally I've spent five to ten times more time and effort writing this postmortem than writing the app itself. The app is two lines long. C# will not let you directly divide by zero so you have to make a variable, set it to zero, and divide by that. That was easily the most challenging aspect of this program.

No performance optimizations required
Game runs at 30 fps without any need for optimizations. This is because of low graphic overhead and the WP7 device's ability to quickly divide numbers and crash.

No scope creep
When I started working on the app, I wanted to make an app that divided by zero and crashed. While some other ideas were thrown around (divide by three, help you locate your car, include a 'Bee Attack' mini-game) I managed to brush these aside and stick with the initial vision.

Twitter
If I hadn't been pumping up this release and subsequent postmortem so much on Twitter, I could have finished in half the time and be making a meaningful game right now. That game would have been sweet.

Price
I priced the app at $49.99. In hindsight, this may have been too much. Sales of the app probably won't be very good.

Exception Handling
Had I implemented any type of exception handling, the app probably would not crash when it experiences the divide by zero runtime error. For future versions I may handle this more gracefully.

Art Assets
I thought I was done and ready to submit but then I discovered I needed to create various WP7 icons and a screen shot. This forced me to open Adobe Photoshop (thankfully already loaded and sitting idle on my Task Bar) and create four new images. Luckily I am very good at selecting File -> New. If I had this to do over again though, I would have just pressed Ctrl + N and saved myself a few mouse clicks.

Testing
We did not do any extensive testing on Divide By Zero. Hopefully it doesn't fail review!