Week 3 Progress Reports

Summary:

This week, we were still in the planning phase. However, this does not mean that we were unable to progress on our project overall. We were able to meet with a previous member of the tech team, who illuminated the logic behind their usage of development tools such as Flutter. As a team, we have come together to generate a list of tasks that we can keep track of throughout the rest of the quarter in order to stay on top of our work and reach our objective.

Update: 4/21/19

Throughout the weekend, we touched base via our group chat in order to work on our Gantt planning chart. We were each able to communicate that we added a few new tasks to the Gantt Google Document. After doing this, I feel as though we have a clearer vision of what we still need to do both as a team and individually.

Update: 4/19/19

Some of our team members were able to meet with a previous member of the tech team who was closely involved in the design and implementation of the app. We had various questions regarding the current server and storage usage since we were unsure if we wanted to continue using the previous team's development tools. After this interview, we feel comfortable being able to begin our programming on Tuesday.

Update: 4/17/19

I did some further research about the current app's development tools. We were in the process of determining the pros and cons of continuing with the same tools, such as Flutter. I did some research into Flutter and felt as though this is still a good framework for the app because it is easy to use since it requires JS, which everyone in the team earlier mentioned they are comfortable using

Update: 4/16/19

We met after class in order to further deliberate how we can get started on our project. Most of our conversation revolved around the logistical issue of gaining access to the Github repository as well as planning how we should continue innovating on the new project. An example of a specific questions we addressed was: How are we going to increase the speed of photo rendering? We looked into the previous team's code to see if this it is a result of the implementation of the storage or the quality of the storage requests themselves.