Debug firmware/software before release
There are far too many glitches in the stable updates released - a video on Twitter showed a user who randomly could not type a number 2 in his password and so he had to disconnect the power plug. The Internet meanwhile is also rife with users who cannot, for love nor money, name their portal during the setup process.
I realised eventually that I could use the back button a few screens (I went back to the connect to WiFi stage) and then progress through the stages again for the portal to be able to be named. This is hardly intuitive when Facebook Portal help (and customer services) recommend a factory reset at this stage, involving the home button which will not actually do anything in the setup dialogue.
Facebook should be thoroughly ironing out bugs before releasing firmware/software updates as this is not a great start to a conventional product relationship between buyer and Facebook "here's the product, now you have bought it, usability and functionality (based on the actual needs of users) is an afterthought".
-
Priyanka commented
Decodering software and firmware thoroughly is necessary before releasing it. To guarantee peak performance and dependability, mistakes, inconsistencies, and vulnerabilities must be found and fixed. Unit, integration, and regression testing as well as log and error report analysis are examples of debugging techniques. Thorough debugging improves user experience and product quality by lowering the possibility of post-release problems.