Because the emulator’s size wasn’t the same as the device last week when I exhibited the system on a real device, there were numerous UI deformities. I thus spend some time resolving this UI issue. <\/p>\n\n\n\n
After resolving the UI problem, I began testing the app with a real barcode and scan, where I discovered a number of issues. They were major issues that might cause the software to fail or have negative effects, but because they were display issues, we view them as minor issues.<\/p>\n\n\n\n
I also spent some time fixing various issues, such as the focus issues, but the hardest was figuring out how to set the interval following a go-back navigation so I could restart the timer that I had stopped when moving to the next screen.<\/p>\n\n\n\n
I came up with a plan to refresh the screens following go back navigation. The solution wasn’t very formal, but I was able to solve the issue by applying critical thinking. I did this by sending nonsense parameters to useDidMountEffect, which is similar to a use effect but doesn’t call on the initial render. I then used that hook that would be called once the parameters changed, and I placed the function that makes the request on it. Inside the function, I set the timer to true.<\/p>\n","protected":false},"excerpt":{"rendered":"
Because the emulator’s size wasn’t the same as the device last week when I exhibited the system on a real device, there were numerous UI deformities. I thus spend some time resolving this UI issue. After resolving the UI problem, I began testing the app with a real barcode and scan, where I discovered a … <\/p>\n