Meeting 3 for 451 (18.10.2022)
📅 Date: 18.10.2022
📍 Location: CMPE BM5 Classroom
🕐 Duration: 15.10 - 17.00
📝 Note Taker: Bahrican Yeşil
👥 Attendees:
- Bahrican Yeşil
- Egemen Atik
- Onur Kömürcü
- Ezgi Aysel Batı
- Ecenur Sezer
- Batuhan Çelik
- Koray Tekin
- Hasan Can Erol
- Enes Sürmeli
- Altay Acar
- Gökay Yıldız
- Determining the app name
- Determining the app color scheme
- Deployment in all personal computers
- Base internal setup in the mobile/back/front teams
- Feature determination for this week
- Determining the required endpoints, their request and response bodies. (authentication flow)
- Annotation data model - Research
- Determining the logo
- We discussed what should be the name of our app. To solve this discussion faster and in a way that all team members contribute, we opened an excel sheet. All team members wrote their name suggestions anonymously. Then, we created a Google form and get the votes of all team members. According to the voting results, the most selected name is "Learnify". So we determined the name of the app as "Learnify".
- We also had a discussion on the color scheme of the app. To resolve this discussion too in a faster and more democratic way we used "colorhunt.co" website (with the suggestion of Altay). There are some previously prepared color schemes by considering the harmony of the primary and accent colors. Among these ones, each team member chose and suggested his/her favorite and shared it on our discord channel. Then, we again created a Google Form with all these favorited options and voted them among the team. As a result of the voting, we chose the following color scheme as the color scheme of our app. The color scheme of the app
- We also decided to determine our app logo since, with the determination of the app name and color scheme, we are able to decide on the logo. To determine the logo, we again got help from the web and ai-based solutions. We tried several websites and finally, we chose our favorite logos by inspiring them (having an idea about how it can be). Our logo with our app name will be as below (Altay will draw this again).
- We discussed the base setup and decided that each sub-team should get ready for the base setup of its own technology. Any further discussions and problems will be handled in the sub-team meetings.
- Each member should use the dockerized app by accessing the deployed back-front and the app APK mobile team will provide before our presentation. All team members should be sure that s/he can run the app with the deployed back connection (not local).
- Since after this week, we have so less time for the presentation, we determined the features we will implement this week. We had several discussions on this topic not only within the team but also with TA. In the end, we decided to finish the following features:
- Signup
- Login
- Verify email
- Forgot password
- Resend email verification code And we will also have a static (not functional but designed to give an insight about how the screen will be) home screen which welcomes the user after the authentication process.
- We discussed Suzan hoca's mention of annotation research in the lecture. We understand that the topic of the next week will be annotations. We have already done the research and created a wiki page regarding the annotations. So, for this week, we will re-read our research and get a better understanding of annotations by also getting the help of additional resources.
- We don't have to draw wireframes/designs of the screens. We can just basically implement them on the code side.
- We also had to determine the request and response bodies of the endpoints we determined in this meeting. The reason for this requirement is the fact that all sub-teams (back, front, mobile) should create compatible models, and should expect, send and return something that is expected by all team members. This topic took most of the time in our meeting and we had several discussions, we did a good brainstorming. In the end, we decided on the following data schemes for the request and response bodies of the endpoints mentioned above:
Request -->
- Username
- Password
Response -->
- Error/Success message
Request -->
- Password
Response -->
- Error/Success message
- Access token
- User
Request -->
- Verification Code
Response -->
- Error/Success message
- Access token
- User
Request -->
Response -->
- Error/Success message
- Deletion of lang code from user class.
- What we will be dealing with this week: BACK: Develop endpoint + test + documentation FRONT: Develop page design + network connection + test MOBILE: Develop page design + network connection + test
- Project plan will be updated, the home page will have a higher priority
| # | Details | Assignee(s) | Due | Issue |
|---|---|---|---|---|
| 1 | Update the project plan to give priority to the home screen | Batuhan Çelik | 22.10.2022@ [23:59] | Link will be given |
| 2 | Design the determined logo, create and share the output files with the team | Altay Acar | 22.10.2022@ [23:59] | #353 |
| 3 | Run the dockerized back and front apps on your local | All Team Members | 24.10.2022@ [23:59] | Link will be given |
| 4 | Set the base project and setup for Flutter | Mobile Team | 22.10.2022@ [23:59] | Link will be given |
| 5 | Set the base project and setup for React | Front Team | 22.10.2022@ [23:59] | Link will be given |
| 6 | Set the base project and setup for Node.js | Back Team | 22.10.2022@ [23:59] | Link will be given |
| 7 | Re-read annotation notes, do detailed research | All Team Members | 24.10.2022@ [23:59] | Link will be given |
| 8 | Signup endpoint implementation | Batuhan Çelik | 24.10.2022@ [23:59] | Link will be given |
| 9 | Signup endpoint test & documentation | Batuhan Çelik | 24.10.2022@ [23:59] | Link will be given |
| 10 | Login endpoint implementation | Hasan Can Erol | 24.10.2022@ [23:59] | Link will be given |
| 11 | Login endpoint test & documentation | Hasan Can Erol | 24.10.2022@ [23:59] | Link will be given |
| 12 | Verify email endpoint implementation | Ecenur Sezer | 24.10.2022@ [23:59] | Link will be given |
| 13 | Verify email endpoint test & documentation | Ecenur Sezer | 24.10.2022@ [23:59] | Link will be given |
| 14 | Send verification code endpoint implementation | Batuhan Çelik | 24.10.2022@ [23:59] | Link will be given |
| 15 | Send verification code endpoint test & documentation | Batuhan Çelik | 25.10.2022@ [23:59] | Link will be given |
| 16 | Mobile - Signup screen design and functionality (without back connection) | Bahrican Yeşil | 24.10.2022@ [23:59] | #358 |
| 17 | Mobile Signup screen tests | Bahrican Yeşil | 25.10.2022@ [23:59] | #359 |
| 18 | Mobile - Login screen design and functionality (without back connection) | Onur Kömürcü | 24.10.2022@ [23:59] | Link will be given |
| 19 | Mobile Login screen tests | Onur Kömürcü | 25.10.2022@ [23:59] | Link will be given |
| 20 | Mobile - Forgot Password screen design and functionality (without back connection) | Ezgi Aysel Batı | 24.10.2022@ [23:59] | Link will be given |
| 21 | Mobile Forgot Password screen tests | Ezgi Aysel Batı | 25.10.2022@ [23:59] | Link will be given |
| 22 | Mobile - Verify Email screen design and functionality (without back connection) | Egemen Atik | 24.10.2022@ [23:59] | Link will be given |
| 23 | Mobile Verify Email screen tests | Egemen Atik | 25.10.2022@ [23:59] | Link will be given |
| 24 | Web - Signup screen design and functionality (without back connection) | Altay Acar | 24.10.2022@ [23:59] | Link will be given |
| 25 | Web Signup screen tests | Altay Acar | 25.10.2022@ [23:59] | Link will be given |
| 26 | Web - Login screen design and functionality (without back connection) | Koray Tekin | 24.10.2022@ [23:59] | Link will be given |
| 27 | Web Login screen tests | Koray Tekin | 25.10.2022@ [23:59] | Link will be given |
| 28 | Web - Forgot Password screen design and functionality (without back connection) | Gökay Yıldız | 24.10.2022@ [23:59] | Link will be given |
| 29 | Web Forgot Password screen tests | Gökay Yıldız | 25.10.2022@ [23:59] | Link will be given |
| 30 | Web - Verify Email screen design and functionality (without back connection) | Enes Sürmeli | 24.10.2022@ [23:59] | #385 |
| 31 | Web Verify Email screen tests | Enes Sürmeli | 25.10.2022@ [23:59] | Link will be given |
| 32 | Implement the navigation manager | Bahrican Yeşil | 22.10.2022@ [23:59] | #356 |
| 33 | Implement the language and theme provider and multi-theme support base setup | Bahrican Yeşil | 22.10.2022@ [23:59] | #357 |
| 34 | Implement the main function, base mvvm setup, helper extensions and the first app widget | Bahrican Yeşil | 22.10.2022@ [23:59] | #350 |
| 35 | Document the meeting notes - Week 3 | Bahrican Yeşil | 20.10.2022@ [23:59] | #348 |
The mobile team has organized a separate meeting on 17.10.2022 and dicussed the development process of mobile side, took some decisions. You can read the meeting notes of this mobile team meeting here.