| ID
|
- Before
- |
- After
+ | Challenges
|
- Reason
+ | Explanation and Actions taken
|
- | 1
+ | 1
|
- Store and access membership or loyalty reward cards digitally, eliminating the reliance on physical cards.
+ | We had a huge commit issue on github due to a circleci.yaml file that existed in our repo when we did not even set it up.
|
- Remove the digital membership loyalty rewards card feature.
- |
- We decided to narrow our focus down to name cards, sticking by our vision ‘networking made easy’.
+ | Research on circleci, github commit & also seek advice from our advisor, Ruby. Manage to remove the circleci.yaml file and resolve the commit issue.
|
- | 2
- |
- Exchange and share personal name cards through NFC integration
+ | 2
|
- Add friends through QR Code Scanning, thereafter users can view all of the friends’ cards.
+ | OCR integration into our app. Using the camera in the phone requires appropriate permissions and life cycles to be set up.
|
- QR Code is a widely used technology that users are used to using. Additionally, we are also using the camera for other functions such as the OCR to convert physical name cards into digital name cards, which means users would be more familiar with the scanning action with the camera, allowing easier familiarization of the app.
+ | It was not easy to set up the OCR integration into our app. After setting up the appropriate permissions and life cycle for using the phone camera, we were able to recognise the text successfully with rather decent accuracy. However, to filter out the appropriate information that should be used to pre-fill the fields for our name card forms is a huge challenge to us as we were not familiar with AI/ML. Instead we decided to use a simple regex of finding matching patterns to filter out the appropriate information such as ‘+65’ for phone numbers, ‘@’ for email address and 6 digit numbers (postal code) for address. In the future, we are planning to use some Large language models to more accurately filter out the appropriate information to pre-fill the fields correctly and filter out unnecessary information.
|
- | 3
+ | 3
|
- No segregation of sub collections in firebase.
+ | App crashing bug. During the start of Milestone 3, there was a bug with the app where the app would crash everytime a new page is opened.
|
- create a sub collection named ‘friends’ to segregate all the friends’ data and friends name card
- |
- When updating the firebase for the different collections, only 1 collection needs to be updated instead of the entire database under a document.
+ | We explored around with the app to try to find out when the crash happened. Initially, we thought that the cause of the crash was from the inappropriate life cycle set up for using the phone camera in the OCR function. However, we found out that any other tabs also caused the crash of the app, which means that the crash was not due to the inappropriate life cycle. We then decided to trace back the commits to find out when the bug first appeared. This would help us find out which code is causing the crash of the app. We also researched the error message shown. Turns out that there was some dependency issue, and it was solved quickly after.
|
- | 4
- |
- Converting physical name cards into personal name cards only
+ | 4
|
- Converting physical name cards into both personal & friend’s cards.
+ | NFC integration into our app.
|
- Not everyone will have a ConnectCard account. For example, businesses such as Dental clinics and salons also carry their own name cards. Therefore, by including a friend’s card option for the conversion of the physical cards, users can now save these name cards easily.
+ | Currently, flutter only has packages that support NFC communication between a NFC Device and a NFC tag. For peer to peer communication via NFC, it is basically not possible. Also, after careful consideration, we felt that using QR code is instead a better alternative as compared to NFC as QR code is a widely used technology that almost everyone is familiar with. This allows new users to easily learn how to use the feature without much learning curve. In addition, we are already using the phone camera for the OCR feature, this provides an extra layer of familiarity for the users, allowing them to get familiar with using the app quickly.
|
- | 5
+ | 5
|
- Friends can be added immediately with no friend request function
+ | Bluetooth integration into our app.
|
- Friend request system is set up. Users will have to accept and
+ | Bluetooth integration was another alternative that we considered during our discussion to replace the NFC technology. However, after careful considerations, we felt that QR code technology is still the ideal alternative due to the same reasons stated in point 4.
|
- Friend request system allows user to have more privacy and control over who they want their name cards to be shared with.
+ |
+
+ | 6
+ |
+ Deployment of app in both Android and IOS.
+ |
+ Initially, our app is supposed to be deployed on both IOS and Android. However, due to many dependency, permissions conflicts as well as time constraints, we were only able to deploy the app on android devices. We decided to follow through the development in Android devices and only fix up the IOS deployment in the future when we have more time.
|
-
# Project Log
Link: [https://docs.google.com/spreadsheets/d/1aPRcCrV2DgaXbIsEnaVfjLGABb_CIqXqBk_hmSb5DgI/edit?usp=sharing](https://docs.google.com/spreadsheets/d/1aPRcCrV2DgaXbIsEnaVfjLGABb_CIqXqBk_hmSb5DgI/edit?usp=sharing)
diff --git a/readme_assets/poster.png b/readme_assets/poster.png
index 49045f6..a6c81dc 100644
Binary files a/readme_assets/poster.png and b/readme_assets/poster.png differ