{"id":56,"date":"2020-11-13T11:35:13","date_gmt":"2020-11-13T16:35:13","guid":{"rendered":"http:\/\/blog.prestigecode.com\/?p=56"},"modified":"2020-11-13T11:35:13","modified_gmt":"2020-11-13T16:35:13","slug":"app-saving-detailed-tracking","status":"publish","type":"post","link":"https:\/\/blog.prestigecode.com\/index.php\/2020\/11\/13\/app-saving-detailed-tracking\/","title":{"rendered":"App Saving &#038; Detailed Tracking"},"content":{"rendered":"\n<p>I had plans after entirely switching over to Laravel for the backend framework for Antilobby. Laravel enables the more efficient execution of queries and authentication, so I can save processing power on my AWS instance and also develop more memory intense features with Antilobby.<\/p>\n\n\n\n<p>A few weeks after switching over, I made the decision to work more on the app. With the goal of having Antilobby collect more useful data for its users, I went ahead and began developing a way for the app to track application use by the minute. I have been able to add these features and am currently working on an effective database scheme to deploy these features with.<\/p>\n\n\n\n<h2 class=\"has-text-align-center\">Detailed Application Time<\/h2>\n\n\n\n<p>In an effort to provide more insight into daily usage, I made the application begin tracking how many seconds each minute that an application is being used for. I had plans to do this along with the tracking of time an application is open for, even if it&#8217;s not being touched but still consuming CPU time. This capability is also possible with the changes I&#8217;ve made and I am also developing a way to save this information so that I can use it to make the website experience better.<\/p>\n\n\n\n<h2 class=\"has-text-align-center\">Threads<\/h2>\n\n\n\n<p>I&#8217;ve also implemented the use of multithreading so that the UX can be improved. I&#8217;ve successfully implemented this logic into all of the saving methods and any method used in doing so. So things should be working a lot smoother now. \ud83d\ude0a<\/p>\n\n\n\n<p>With all these features, I&#8217;m looking at beginning to refactor a lot of the codebase that Antilobby is run on. I&#8217;ve done a bad job at maintaining this code, so it&#8217;s time to fix that.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I had plans after entirely switching over to Laravel for the backend framework for Antilobby. Laravel enables the more efficient execution of queries and authentication, so I can save processing power on my AWS instance and also develop more memory intense features with Antilobby. A few weeks after switching over, I made the decision to [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[17,24,25,18],"_links":{"self":[{"href":"https:\/\/blog.prestigecode.com\/index.php\/wp-json\/wp\/v2\/posts\/56"}],"collection":[{"href":"https:\/\/blog.prestigecode.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.prestigecode.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.prestigecode.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.prestigecode.com\/index.php\/wp-json\/wp\/v2\/comments?post=56"}],"version-history":[{"count":1,"href":"https:\/\/blog.prestigecode.com\/index.php\/wp-json\/wp\/v2\/posts\/56\/revisions"}],"predecessor-version":[{"id":57,"href":"https:\/\/blog.prestigecode.com\/index.php\/wp-json\/wp\/v2\/posts\/56\/revisions\/57"}],"wp:attachment":[{"href":"https:\/\/blog.prestigecode.com\/index.php\/wp-json\/wp\/v2\/media?parent=56"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.prestigecode.com\/index.php\/wp-json\/wp\/v2\/categories?post=56"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.prestigecode.com\/index.php\/wp-json\/wp\/v2\/tags?post=56"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}