CST 489-499 - Module 14

 Week 14,

This week was fairly productive as well, but I feel like I can pick up speed, or at least spend more time than I have already. Last week my plan was to add non-users of our app to be included in a given board game match/event and to figure out a way to determine how a user would win (highest score, lowest score, custom placements). So far, I was able to implement those, that way for people who don't own an android phone, and now users don't have to type as much to determine who wins. Additionally, I added a dialog screen for users where were invited to an event to have the ability to accept or decline. Before, that was implemented, any user can just visit the event/match and change certain things about it. Now that is no longer the case.

Right now, if a game/match was deleted, there is no rollback on the user metrics which keeps track of the number of times they won/lost, win/loss streaks, etc. It would be unfortunate if a user accidentally lost their winning streak so if there is at least some mitigation to that scenario, that would help. So up next, I plan on working on that, as well as fixing any bugs we haven't covered already.

There wasn't much of a challenge this week from the usual suspects, however I did have some trouble with a page on the app that shows the quick match games where users don't have to start an event to play a game. In short, with firebase's database, we have to include some settings for a new index we would need to sort something from the database. In MySql, you would just simply make the query, but with Firebase, while you can use it, for multiple devices/people it wouldn't work, so you have to make an index for the query. An SQL "where" query. Other than that, I think things are going relatively ok, ignoring the time factor.

Comments

Popular posts from this blog

CST 489-499 - Module 9

CST 489-499 - Module 10

CST 489-499 - Module 13