Zuri ChatApp Desktop Application

Zuri ChatApp is a Slack Clone Desktop App project created in Flutter. This project is developed by the desktop team under TEAM SOCRATES

Description

• Zuri ChatApp supports Desktop and Mobile. This project is aimed at developing a chat App solely for the Zuri program that is fast and helps to dissemonate infomation easily among it users.

Features

• Splash
• Login
• SigUp
• Onboarding
• Home
• DM
• Thread
• Channel
• Profile
• Admin
• Insights
• Routing
• Theme
• Database
• Provider (State Management)
• Validation
• Code Generation
• User Notifications
• Dark Theme Support (new)

Technologies Used

Folder Structure

Demo-Preview

Table of Contents

1. Zuri ChatApp Desktop Application
2. Demo-Preview
3. Table of Content
4. Installation
5. Usage
6. Development
7. Contributing
8. License
9. Conclusion

1. Zuri ChatApp Desktop Application
2. Demo-Preview
3. Table of contents
4. Installation
5. Usage
6. Development
7. Contributing
8. License
9. Conclusion

Installation

Usage

This space shows useful examples of how our project can be used. Additional screenshots, code examples and demos will be added to this space.

Development

Contributing

Contributions are what make the open source community such an amazing place to be learn and create. Any contributions you make are greatly appreciated.

1. Fork the Project
2. Clone your forked repository
   • Fork from dev branch
   • Clone the forked repository
3. Set your origin and upstream repository
   • Set your forked repo as your origin
   • Set zc_desktop_flutter as upstream repo
   • Check if origin and upstream are added
4. Create your Feature Branch (git checkout -b feature/zc_desktop_flutter)
   • Work on your section under the feature you are implementing
5. Add files (git add .)
6. Commit your Changes (git commit -m 'Add some zc_desktop_flutter')
7. Pull from dev branch to stay up to date for local merge (git upstream dev)
8. Push to the Branch(dev branch) (git push origin feature/zc_desktop_flutter)
9. Open a Pull Request When making a PR, your PR is expected to have the following comments" - What is the task/issue completed? - What does the PR actually does? - How can the PR be manually tested? - Screenshots(of your implementation - A mobile screen or an APi payload).

Contributors

This project would not have come alive if not for the great deal of contributors gave their valuable input in code implementation and discussions. Names will be posted on completion

License

Conclusion