- Introduction
- Motivation
- Features
- Installation
- Usage
- Folder Structure
- API Documentation
- Backend Repository
- Contributing
- FAQs
- License
- Contact Us
- Additional Resources
Message_50 is a modern, secure, and fast messaging web application designed to provide seamless communication for users. It leverages cutting-edge technologies such as the Subtle Crypto API, WebSockets, and IndexedDB to ensure a highly secure and efficient messaging experience. This repository contains the frontend code for the application.
The motivation behind creating Message_50 stems from the need for a reliable, private, and user-friendly messaging platform. With increasing concerns about data privacy and security, Message_50 aims to provide:
- End-to-End Encryption: Ensuring that user data remains private and secure.
- Cross-Platform Accessibility: Allowing users to stay connected across devices.
- Real-Time Communication: Leveraging WebSockets for instant message delivery.
- Ease of Use: A clean, intuitive interface for users of all technical backgrounds.
Message_50 is built with the vision of fostering private and meaningful connections between friends, families, and colleagues.
- End-to-End Encryption: Messages are encrypted and can only be read by the sender and recipient.
- Cross-Platform Support: Access your chats on mobile, tablet, and desktop devices.
- Real-Time Messaging: Instant message delivery using WebSockets.
- Media Sharing: Share images, videos, and documents securely.
- User-Friendly Interface and Experience: A clean and intuitive design for effortless navigation.
To set up the frontend of Message_50 locally, follow these steps:
-
Clone the repository:
git clone https://github.com/davidtimi1/Message_50.git
-
Navigate to the project directory:
cd Message_50 -
Install dependencies:
npm install
-
Start the development server:
npm run dev
- Open your browser and navigate to
http://localhost:3000. - Set up the backend
- Sign up or log in to access the messaging features (optional guest mode).
- Explore functionalities such as sending messages and sharing media files.
Message_50/ # Root Directory
├── dist/ # build files
├── src/
│ ├── app/ # structured like Nextjs app router
│ │ ├── chats/
│ │ ├── contacts/
│ │ ├── media/
│ │ ├── settings/
│ │ └── feedback/
│ ├── auth/ # auth lib and resources
│ ├── landing/ # landing page resources
...
│ │ └── page.jsx
│ ├── lib/ # addn lib and modules
│ ├── users/
│ │ └── page.jsx # dynamic route for handling unauthed user view
│ ├── ui/ # global css files
│ ├── App.jsx
│ ├── index.jsx
│ └── service-worker.js
├── public/ #
│ ├── index.html
├── logo.png
├── logo.svg
├── user-icon.svg
├── mainfest.json
│ └── favicon.ico
├── prerendered-htmls/ # html snapshot of important routes (support SEO and prefetch)
│ └── ...
├── vite.config.mjs # bundling config
├── vercel.json
├── package.json
└── README.md # docs
The backend code for Message_50 is hosted in a separate repository MSG50-BE. It handles server-side operations, including user authentication, message storage, and real-time communication using WebSockets.
You can find the backend repository here: MSG50-BE GitHub Repository
- Ensure your code follows the project's coding standards.
- Write clear commit messages.
- Test your changes thoroughly before submitting a pull request.
- Provide detailed descriptions of your changes in the pull request.
Yes, we use end-to-end encryption (E2EE) to ensure your data remains private and secure.
Absolutely! Our platform is cross-platform and works seamlessly on all your devices.
Messages are delivered instantly using WebSockets and cutting-edge technology.
E2EE ensures that only you and the person you're communicating with can read the messages. No one else, not even the platform, can access your messages.
Yes, at happens if I lose my device? If you lose your device, your messages cannot be accessed without your private key. Always ensure you have a backup of your encryption keys.
T Read morehi
#roject is licensed under the MIT License. See the LICENSE file for details.
For any inquiries or feedback, please visit our Contact Us page or send us a message through the feedback form.
- Privacy Policy: Privacy Policy
- Terms of Use: Terms of Use
- Developer Portfolio: David Uwagbale's Portfolio
- GitHub Profile: [David Uwagbale's GituMailavidTmailto:devs.message50@gmail.com ev_did