library to our app. We followed the instruc*ons to integrate into the app. Tested it, checked the calls it made, were happy and released it, gradually, 1%..5%..20% then 100%. Graphs were green, no alerts going off, all was well…..
android.net.conn.CONNECTIVITY_CHANGE Caused the startup API’s to be called – repeatedly. One users app called the startup calls 2800 *mes in a single day Our monitoring copied desktop and we had no alerts on start up calls
and we see the crash reports but we cannot reproduce. We test on devices, not simulators We cover the different ios versions that we support We have old and new devices
VoiceOver func*onality in for you Bukons that have labels have the accessibility set for you Icons need to have accessibility labels added Automa*on frameworks reuse this to iden*fy elements
labels (in the correct language too) so we had this covered….. It read out “VIP FLOATING BAR” And users had to disable VoiceOver to select any of the op*ons.
copying of monitoring from desktop would be enough We assumed that we just needed device coverage like browser/os coverage. We put our hopes on automa*on to save the day We didn’t test in the same way as a user would use the app.
ask what is different about mobile that we might not have covered? • Put yourself in the same posi*on as the user • Reduce risk – small releases and staged rollouts • Monitor and Check Ra*ngs/Reviews