Blog Post #3
How is the journey so far?
I am really enjoying my project thus far! Our team is creating a cross-platform mobile app that creates a fitness plan consisting of workouts based on your fitness level and fitness goals. We’re using React Native Javascript for the frontend, Firebase for the backend, Expo for the build, and GitHub Actions for continuous integration and deployment. It’s been a while since my web dev class and I wasn’t familiar with any of the tech or mobile development beforehand so there was a steep learning curve at the start. I’m a visual learner so I purchased a Udemy course that taught and demonstrated React Native and it has helped me learn quickly. I’ve also enjoyed working with my teammates!
What communication tools is your team using, and how well is this going?
We use a Discord server and it’s been great! One of my teammates is on the East Coast while the rest of us are in PST. Despite this time difference, we’re able to use Discord to communicate asynchronously and thoroughly. We have different channels for different topics; this keeps our discussions multi-threaded and in parallel. A sampling of some of our channels:
- general
- contact-info
- team-standards
- project-plan
- project-archive
- meetings
- standup
- account-info
- resoures
- all-things-firebase
- all-things-github
- exercise-library-stuff
- approvals (anything that requires approving such as PRs goes here)
- progress-reports
How often does your team commit their code? Is code integrating easily?
We use GitHub: https://github.com/osu-cs467-myFitnessTrainer/myFitnessTrainer
Our team commits code around five or so times per week. The code is integrating easily! We implemented GitHub Actions that will do the following upon pull requests and pushes to main:
- Install package.json dependencies
- Run the Javascript eslint linter
- Run tests
We’ve also implement main branch rules such as requiring at least one reviewer and obsoleting stale requests upon changes in a PR. By doing all this set up, we can continuously integrate changes knowing that our new code will not break existing functionality. This automates the verification for us.
Leave a Reply