log 30: plan

organized 

In one of my first logs describing the work I have put in so far I mentioned how I took the long way for a lot of the features. Rewriting and loading code at every single point so that I could make sure each screen could work. I wrote about how taking a long way ensures that the features work at the expense of time. I also wrote about how I wasted my time because I didn’t understand Swift enough to directly write a structure or class which can be reused. Well… I have finally gotten to the point where I can load data in one place, and send it across different screens. I must say, I am glad that I took the long route to make sure everything works first. Transferring functions and variables to a central loading location was a piece of cake because I had everything written out already. Now, much of my data is being read from a screen that appears before the user is able to interact with the app. This deals with a lot of my loading issues where functions and data will only trigger when a certain screen is selected. Having all my data loaded beforehand makes transitions seamless without loading delay. The next thing I am going to be working on is making sure that my database for user information is structured more efficiently so that I can load bigger amounts of data without having to worry about timing functions. Aside from that, exercise video creation for my exercise database is going great! My goal is to film 30 videos per week. After two weeks, I’m at 90. I’m hitting upload limits on Youtube and Instagram. Feels great to be productive!