Thanks Cyax, this is exactly correct.
Asking for code that has 0 bugs to be written is unrealistic, especially for a web app which can be used on an older browser and its impossible to account for all of them. As Cyax mentions even big companies with multi-million dollar budgets release software that has bugs in it all the time, this is something that should be expected in this field.
And cancelling an order for one bug, after first delivery, this is what really annoys me. And it wasn’t even a bug that made the app to be completely unusable, they say it was because of the frame drops. Well gee, a 3d app for the web that doesn’t have smooth frame rates didn’t pass their test, really ? By this measure you can run Google on an old laptop and say it’s lagging.
Besides, it’s something which I could have addressed because I am finding this out just now. I could have easily worked on improving frame rates if I was given the time or just knew that it was what needed to be done.
This order got cancelled only a few hours after my second delivery (with physics), I didn’t even get the time to figure out what was wrong. The customer opened a dispute by saying the work was buggy right after delivery. I denied his request saying that bugs can be fixed and I can’t just cancel like that and urged him to work together to improve his experience. After he provided a record of a bug and requested a revision I started working on figuring it out but after a few hours the order got cancelled. And that is that