Fyp 2
Fyp 2
Fyp 2
Existing System: The existing system was previously paid, so the user had to pay to
use it. Perhaps in the future, it may become paid again.
Proposed System:
If the current system becomes paid, we can leverage HU's network infrastructure to
launch HUChatApp worldwide. By uploading it to HU servers, we can grant access to
teachers, students, and new users. This would enable our university to effortlessly
convey important news to individuals without requiring them to physically visit the
university.
The Chat App will be designed with a client-server architecture, where users interact
with the application through client interfaces, and a central server manages the
communication between clients. The server will be responsible for handling user
authentication, message routing, and overall system coordination.
Key Components:
Authentication: (Phone Auth Firebase)
Update Profile
Realtime Chat: (Text, Emoji, Image, Voice, Gif, Video)
Reply to any Chat (Text, Image, Voice, Gif, Video)
Video Call: (Agora SDK)
Delete Messages
Status & Expire status after 24 hours
Call History
Search
Cross-Platform Compatibility
Feasibility study:
Technical Feasibility:
Evaluate the hardware requirements for both the server and client devices.
Ensure the chosen hardware is scalable to accommodate potential increases
in user base.
Assess the compatibility of software components, including the operating
systems and development tools.
Verify the availability of third-party APIs or libraries for additional functionalities.
Economic Feasibility:
Break down the costs associated with development tools, server hosting, database
management, and potential third-party services.
Compare these costs to the budget allocated for the project
Decision:
_______________________________________________________________________________
______________
_______________________________________________________________________________
_____________.