ruland39 / unilink

A Proximity Based Social Media Android App

Ruland Muhammad Furqan

Computer Science with Artificial Intelligence at the University of Nottingham Malaysia

👋 Hi! I'm Ruland, most likely the only Ruland you will ever come across. I possess a multidisciplinary background, coupled with a deep passion for product design and crafting user-centric, intuitive designs. My technical proficiency in Software Engineering, Web and Mobile Development as well as AI stems from my studies as a computer science student. Embracing the philosophy of "Learning by Doing," I continually seek opportunities to learn and enhance my capabilities.

💡 I thrive on feedback and constructive discourse, as they fuel my pursuit of knowledge and skill advancement. My commitment revolves around the creation of engaging and innovative products that hold the potential to inspire hope and make a meaningful impact on people's lives. Through the medium of UI/UX design and product creation, I aspire to translate ideas into tangible solutions that enhance user experiences.

🤝 Looking forward to connecting and collaborating with like-minded professionals and being a part of the ever-evolving community.

👌 https://ruland.framer.website/

unilink's Issues

Refactor the code bro

There's alot of redundant code and some things that could better be implemented under the OOP design, but for now what we have is simply to create a functioning prototype

Loading screen/progress bar class

• Generally, we require a progress bar to show loading to the end user.
• A specific issue that comes up is after #623bbdf, when the HomescreenActivity class is being loaded after logging in, or just opening up the app, it takes a while to retrieve the user data from Firestore hence when the Homescreen loads, there's no user information stored; null

Fragment stacking in the Homescreen Activity

After committing #20, the Bluetooth Button discovering mode does not stay as the fragment changes, and I realised this is due to the other fragments being called using replace(), hence not having a proper backstack.

• Need to figure out the flow of stacking for the Homescreen fragments

Feature/ Navigation Drawer

Component/Bottom Navigation Bar does not appear properly on some devices

Bottom Navigation Bar does not show up or misaligned on some devices due to screen resolution

Feature Page should only happen during installation and not after logging out

Beacon transmission bytes excess

• In the Bluetooth Branch, running the current code returns the following java.lang.ArrayIndexOutOfBoundsException: end > bytes.length. This is due to the long exceeding the maximum bytes to be transmitted in the beacon.
• Fixable by using a string for the unique user id instead of Long and try to transmit that instead.

Feature/Bluetooth Low Energy Implementation

android BLE docs: https://developer.android.com/guide/topics/connectivity/bluetooth/ble-overview

Feature/Tutorial Page Full Functionality

The feature pages should only load the first time the app is opened.
The feature page should also have sliding animations, rather than the default going up top.

Create TextWatcher implementations

The TextWatcher()s made in commit #80892cd can be made cleaner by implementing each of those textwatcher in each of its own classes, and just implement them in each text view. This is because some textwatchers just watches on specific regex (like email or number) or even if it's just empty.
Example:

• A TextWatcher to for an IsEmpty() validation
• Pattern.EMAIL Regex validation
• etc

Put Connections/Friends in Home Screen