Making Old App Perform Better

Currently, I’ve finished my rework up to the point the app is ready to smoothly take some data.

Notes:

  1. Significant reduction of coding.
  2. Pre-networking data is beneficial.
  3. Need to improve skills with UI constraints
  4. More realistic plans for the project, new ideas.

Point #1 It's running on much less code.
The new code is much more efficient, legible, and disciplined. Ever since the first time I made this app, I have implemented new skills such as using a design pattern for organization.

Point #2 I pre-network the data, and overall it reduces the number of reads.
In the previous version of the app, networking occured in so many instances; swiping collections, entering and exiting pages, etc. In this version, I fetched the data during the launch screen. Here is a look at how smooth the collection View has become:

(Old version)

(New version, no more blank spaces)

Point #3: Setting constraints is… difficult.
I spent a lot of time struggling with constraints, which I’m inclined to study in the future.

Point #4: New plans:
I’ve recently been exposed to how difficult Bar/QR implementation would actually be, due to real-world issues.
While I believe the barcoding/QRcoding feature would have been a great solution for the workplace, there were things I couldn’t fix in real life. The culprit issue is the inconsistency of the barcodes provided by the manufacturer, which are often labeled incorrectly or have various codes for the same product. The labor of creating my own QR/barcodes, (which assumes I would have to print out and attach) is not a feasible solution. While it’s unfortunate, I might plan other new solutions in the future.

Written on November 2, 2020