My progress was a bit halted this week on our group project. I was trying to quickly add dark mode to the application ui and ended up spending way more time than I had originally planned on it. I wanted to have the dark mode persist even if the users closed the application. So, I downloaded the provider package from pub dart website which is supposed to help you use the same variable in multiple area of the application. Basically, in flutter, you can only move data down the tree/widget hierarchy and the provider package allows you to circumvent this more easily by passing the data up or down the widget tree. It seems like I was able to get the provider functionality itself to work but my button to switch dark mode on and off is Not working yet. Also downloaded the shared preferences package which allows data to persist to the disk asynchronously, it’s not guaranteed and shouldn’t be used for critical data. So, yeah. I went down the rabbit hole a little bit. The dark mode button is the moon/crescent shaped icon in the top right corner of the app. That said, I have been trying to get the authentication set up with aws(amazon web services) amplify but am having some issues with admin level access.
Since the dark mode is not requirement for the project, I am planning to focus on the user authentication/login set up which is a requirement. However, there needs to be some configuration setup work with aws tool. I keep getting errors trying to connect our flutter project to the amazon authentication tool(amplify). It appears that it is connected to amplify but only for one of us (the main account holder which is not me), am not 100% sure. I am still looking through the amplify documentation to see if there is a solution. Might end up having to get on a phone call with my team mates so we can figure out the issue more quickly.
Once I can get the authentication setup, then I would like to work on the other ui screens and have the routing complete, i.e., being able to navigate from the login screen to the other pages/screens of the craigslist mobile app and navigate backwards as well.
One other thing which is not a big deal but did stick out to. The collaboration over github is a bit rough haha. We need not to push code to github if the application is failing to build on our locals. It’s a bit challenging right now as we (maybe me mostly) are still spending most of our time reading documentation and getting the application setup but I think it will get easier once we are mostly focusing on the business logic. I have worked on github with developers at work but because we are making incremental and small updates to the code base that issues like merge conflicts and breaking builds do not happen too often. I suppose that might be different if you are working on a team that pushes a lot of code to production but that has yet to be my experience working for a large company.
