├── .gitignore ├── .github └── PULL_REQUEST_TEMPLATE.md ├── submissions ├── quick-vocab.md ├── MyBlog.md ├── astroappwritestarter.md ├── weebhook.md ├── HealthPlus.md ├── Carbon_footprints.md ├── CodeSnippetVault.md ├── gitknit.md ├── SnapQuest.md ├── Vissipass.md ├── pipelineui.md ├── sahil_todo.md ├── TimeCapsule.md ├── adventure-log.md ├── spotfit-gym-manager.md ├── Acadai.md ├── search_ideas_submission.md ├── krishi_mitra.md ├── devx.md ├── anon-messenger.md ├── BugBank.md ├── launchbase.md ├── QuickShare.md ├── ScholarLift.md ├── means-HF.md ├── entrepreneurs-hub-web-app.md ├── FeedbackSO.md ├── TicTacToe-Shift.md ├── careplus.md ├── renest-01.md ├── cpp-sdk-appwrite.md ├── devpath.md ├── kitchen_pal.md ├── Auth_with_Appwrite.md ├── unique-username-function.md ├── SnapStudio.md ├── scrummie-poker.md ├── Ahaar.md ├── Suraksha.md ├── MedConnect.md ├── eventManagement.md ├── decide-yesno-app.md ├── invicollab.md ├── React-Appwrite-RealTime-Chat.md ├── event_planner.md ├── PlantHead.md ├── algomorph.md ├── Jatin_Blog.md ├── MoodJournal.md ├── wp-appwrite-login.md ├── moodsync.md ├── FashionSathi.md ├── SoundStake.md ├── brieffly.md ├── app-comment.md ├── aChief.md ├── Browser-Power-Tools.md ├── heart-bridge.md ├── Patronus_Appwrite_hack_submission.md ├── EduMeet_Web.md ├── Orbit.md ├── sketchy-board.md ├── joblier.md ├── attendify.md ├── rroist.md ├── Trackpot.md ├── NyxAPI.md ├── wisdoma.md └── Askinator.md ├── TEMPLATE_SUBMISSION.md ├── LICENSE ├── spellsentry.md ├── RULES.md ├── CODE_OF_CONDUCT.md └── README.md /.gitignore: -------------------------------------------------------------------------------- 1 | TEMPLATE_SUBMISSION.md 2 | -------------------------------------------------------------------------------- /.github/PULL_REQUEST_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: 2 | 3 | ## Name of Team Lead 4 | _Enter your full name_ 5 | 6 | 11 | 12 | ## GitHub handles of Team Members 13 | _Enter the GitHub handles of all your team members (including yourself) as separate bullet points_ 14 | 15 | 24 | 25 | ### Are all of your team members registered on our [Hackathon Signup page](https://apwr.dev/htf24-hackathon)? 26 | _This is a mandatory step for all participants to be considered eligible for judging_ 27 | 28 | - [ ] Yes 29 | - [ ] No 30 | 31 | --- 32 | 33 | ## Rules and Code of Conduct 34 | By submitting this PR, you agree to follow our Rules and Code of Conduct. 35 | 36 | - [x] Yes 37 | 38 | --- 39 | 40 | ## Anything Else? 41 | _Any other feedback, queries or information you would like to share with us?_ -------------------------------------------------------------------------------- /submissions/quick-vocab.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: QUICK-VOCAB 2 | 3 | ## GitHub handles of Team Members 4 | @Opedepodepes-Olugbemi 5 | 6 | ## Project Title 7 | quick-vocab 8 | 9 | ![image](https://github.com/user-attachments/assets/c36a15bb-6b3a-43fb-a671-c4762db93e98) 10 | 11 | 12 | ## Project Description 13 | A vocabulary building application designed to help users learn new words in a language and their meanings. 14 | 15 | ## Inspiration behind the Project 16 | Learninng new language is hard, having an helper to teach you makes it easier 17 | 18 | ## Tech Stack 19 | The stack i used is: 20 | React (frontend), 21 | Typescript (backend), 22 | Shadcn(ui library), 23 | Gemini 1.5 pro(ai model) 24 | appwrite(database and auth) 25 | 26 | ## Project Repo 27 | https://github.com/Opedepodepes-Olugbemi/quick-vocab 28 | 29 | ## Demo Video/Photos 30 | ![image](https://github.com/user-attachments/assets/0d16d07b-6349-4a60-9ab7-41d54a33756e) 31 | -------------------------------------------------------------------------------- /submissions/MyBlog.md: -------------------------------------------------------------------------------- 1 | # MyBlog - A Blogging web App 2 | 3 | * https://github.com/anant223 4 | 5 | ## My Blog 6 | * Developed a feature-rich blogging platform with secure user authentication and role-based 7 | permissions, incorporating a rich text editor (TinyMCE) for content creation. 8 | * This blogging platform uses Appwrite for secure user authentication, blog data storage, and role-based permissions. Appwrite’s Authentication manages secure login, while its Database stores and retrieves user-generated content. 9 | 10 | ## Inspiration behind the Project 11 | 12 | * I was joining Appwrite hackathon, but without friends to form a team or any clear project ideas, I decided to seek inspiration online. As I explored various articles on Medium, I had a lightbulb moment: why not create something medium type of blog system 13 | 14 | ## Tech Stack 15 | React, Tailwind CSS, Appwrite, and ReduxToolkit 16 | 17 | * https://github.com/anant223/MyBlog 18 | 19 | 20 | 21 | 22 | 23 | https://github.com/user-attachments/assets/eff9f401-92a8-4864-84fb-0afc8d55aed7 24 | 25 | -------------------------------------------------------------------------------- /submissions/astroappwritestarter.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Astro Appwrite Starter 2 | 3 | ## GitHub handles of Team Members 4 | petipois 5 | 6 | ## Project Title 7 | _What is the name of your project?_ 8 | 9 | Astro Appwrite Starter 10 | 11 | ## Project Description 12 | _What have you built during the hackathon?_ 13 | 14 | Starter repo with Notes Application 15 | 16 | ## Inspiration behind the Project 17 | _What is the story behind this project? Why did you choose to work on this specific idea?_ 18 | 19 | I wanted to create something that could be used as a quick starting point for adding backend to an Astro site 20 | 21 | ## Tech Stack 22 | _How have you built this project? Mention the technologies/methods/platforms you used to build your project_ 23 | 24 | Astro JS 25 | Tailwind CSS 26 | Appwrite 27 | 28 | ## Project Repo 29 | _Share a public repo link of your project_ 30 | 31 | https://github.com/petipois/astro-appwrite-starter 32 | 33 | ## Demo Video/Photos 34 | _Share a 2-3 minute demo video of your project_ 35 | 36 | https://youtu.be/Hb2UtCvs3i8 -------------------------------------------------------------------------------- /submissions/weebhook.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Weebhook 2 | 3 | ## GitHub handles of Team Members 4 | - @dishwasher-detergent 5 | 6 | ## Project Title 7 | Weebhook 8 | 9 | ## Project Description 10 | During this hackathon, I developed a project that captures and inspects webhook requests, providing a streamlined way to analyze payload data. 11 | 12 | ## Inspiration behind the Project 13 | The motivation for building this project stems from the widespread use of webhooks by services like Discord, Stripe, and Appwrite to transmit data. Often, their documentation is limited or unclear, making it challenging to interpret payloads accurately. This tool addresses that gap by allowing users to inspect actual webhook payloads directly, simplifying the process of understanding and integrating these services. 14 | 15 | ## Tech Stack 16 | In this project, I utilized, NextJS, Tailwind, and Appwrite. 17 | 18 | ## Project Repo 19 | https://github.com/dishwasher-detergent/weebhook 20 | 21 | ## Demo Video/Photos 22 | Deployed Project: https://weebhook.com 23 | Demo Video: https://youtu.be/PYfxTKgcs2I -------------------------------------------------------------------------------- /TEMPLATE_SUBMISSION.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: 2 | 3 | ## GitHub handles of Team Members 4 | _Enter the GitHub handles of all your team members (including yourself) as separate bullet points_ 5 | 6 | 13 | 14 | ## Project Title 15 | _What is the name of your project?_ 16 | 17 | 20 | 21 | ## Project Description 22 | _What have you built during the hackathon?_ 23 | 24 | 27 | 28 | ## Inspiration behind the Project 29 | _What is the story behind this project? Why did you choose to work on this specific idea?_ 30 | 31 | 34 | 35 | ## Tech Stack 36 | _How have you built this project? Mention the technologies/methods/platforms you used to build your project_ 37 | 38 | 41 | 42 | ## Project Repo 43 | _Share a public repo link of your project_ 44 | 45 | 48 | 49 | ## Demo Video/Photos 50 | _Share a 2-3 minute demo video of your project_ 51 | 52 | 55 | -------------------------------------------------------------------------------- /submissions/HealthPlus.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: HealthPlus - A doctor's appointment management system 2 | ## GitHub handles of Team Members 3 | - [@AdityaSrivastava](https://github.com/AdityaSrivastava185) 4 | 5 | ## Project Title 6 | HealthPlus 7 | 8 | ## Project Description 9 | HealthPlus is a healthcare management system project which is designed for the clinic doctors and individuals to schedule and manage their appointments. 10 | 11 | ## Inspiration behind the Project 12 | It is designed because there are lot of softwares and tools for the big hospitals to manage their appointments but not for small local clinics and doctors . So here comes `HealthPlus` which is designed for small and local clinics where the doctors can view , schedule and cancel the appointments of the patients and on each update on their appointments , the patient will be notified on the messages which makes the entire appointment process easy to use and with simple and minimal design of the web app , It's easy to navigate and use the project. 13 | 14 | ## Tech Stack 15 | - Nextjs 14 (frontend) 16 | - Shadcn UI 17 | - Appwrite (Auth , Database , Storage , Message using Twilio) 18 | - Aceternity UI 19 | - Tailwind CSS 20 | - Vercel 21 | 22 | ## Project Repo 23 | - [Github Repository](https://github.com/AdityaSrivastava185/nextjs-healthcare-management-system-appwrite) 24 | 25 | ## Demo Video/Photos 26 | - [Deployed Project](https://healthplusv1.vercel.app/) 27 | -------------------------------------------------------------------------------- /submissions/Carbon_footprints.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: CARBON FOOTPRINT TRACKER 2 | 3 | ## GitHub handles of Team Members 4 | 5 | -@Aaditdot-1234 6 | -@Madmax2810 7 | -@Gunjanpatilexe 8 | 9 | ## Project Title 10 | 11 | CARBON FOOTPRINT TRACKER 12 | 13 | ## Project Description 14 | 15 | 16 | 17 | ## Inspiration behind the Project 18 | 19 | 20 | 21 | ## Tech Stack 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | ## Project Repo 31 | 32 | https://github.com/Aaditdot-1234/Carbon_Footprints 33 | 34 | 35 | ## Demo Video/Photos 36 | 37 | https://youtu.be/o-eVICtZnjY 38 | 39 | -------------------------------------------------------------------------------- /submissions/CodeSnippetVault.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: CodeSnippet Vault 2 | 3 | ## GitHub handles of Team Member (1) 4 | @Aishwary2004Gupta 5 | 6 | ## Project Title 7 | **CodeSnippet Vault** 8 | 9 | ## Project Description 10 | **CodeSnippet Vault** is a platform that allows users to securely store, manage, and share code snippets. Users can authenticate via GitHub, add code snippets with language tags, vote on snippets, and perform basic code quality checks on stored snippets. 11 | 12 | ## Inspiration behind the Project 13 | This project was inspired by the need for developers to have a centralized place to store reusable code snippets. Additionally, having a quality analysis feature and voting mechanism makes it a powerful community-driven repository. 14 | 15 | ## Tech Stack 16 | 17 | ### Frontend: 18 | 19 | - Next.js with TypeScript for the core application framework 20 | - Tailwind CSS for styling 21 | - shadcn/ui for UI components 22 | - Radix UI icons for consistent iconography 23 | 24 | ### Backend & Infrastructure: 25 | 26 | ### Appwrite for: 27 | 28 | - Authentication (OAuth with GitHub) 29 | - Database management 30 | - Serverless functions 31 | - Real-time updates 32 | 33 | ## Project Repo 34 | [CodeSnippet Vault Repository](https://github.com/Aishwary2004Gupta/Code-snippet-vault) 35 | 36 | ## Demo Video/Photos 37 | 38 | 39 | 40 | https://github.com/user-attachments/assets/b5f97ce2-a0ee-4ec1-9ad7-0c537da1f417 41 | 42 | 43 | 44 | 45 | -------------------------------------------------------------------------------- /submissions/gitknit.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: GitKnit 2 | 3 | ## GitHub handles of Team Members 4 | - [@TejasBhovad](https://github.com/tejasBhovad) 5 | 6 | 7 | ## Project Title 8 | GitKnit 9 | 10 | ## Project Description 11 | What have you built during the hackathon? 12 | 13 | I have created a discord bot and a supporting website that allows developer tool discords to link their repositories to a particular discord forum channels and push threads from that channel to our supporting website 14 | 15 | ## Inspiration behind the Project 16 | Finding answers to obscure questions is hard particularly when the developer tooling is new, Often solutions to these problems are foudn in their discord, these qna's aren't indexable on the web, I wanted to create a site where all these obscure questiosn are indexed on the web and are accessible. 17 | 18 | 19 | ## Tech Stack 20 | - *Frontend*: NextJS, ShadCN UI, TailwindCSS 21 | - *Backend*: Appwrite, tanstack/react-query 22 | - *Appwrite*: Database, Auth 23 | 24 | ## Project Repo 25 | - [Site Repo](https://github.com/TejasBhovad/gitknit) 26 | - [Discord Bot Repo](https://github.com/TejasBhovad/gitknit-bot) 27 | - [Live URL](https://gitknit.vercel.app/) 28 | - [Discord Bot Invite](https://discord.com/oauth2/authorize?client_id=1292501643224678492) 29 | 30 | ## Demo Video/Photos 31 | Share a 2-3 minute demo video of your project 32 | [YT](https://www.youtube.com/watch?v=qA807-M52gs) 33 | 36 | -------------------------------------------------------------------------------- /submissions/SnapQuest.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: SnapQuest 2 | 3 | ## GitHub handles of Team Members 4 | - @HumanBot000 5 | 6 | ## Project Title 7 | SnapQuest 8 | 9 | ## Project Description 10 | SnapQuest is an app where users can compete against other users to see who manages to finish a given challenge first and take an image or video of it. 11 | The challenges have various difficulties and can range from "picking a selfie with your favorite book" to "balance a water bottle" or "find animal-shaped balloons", SnapQuest combines traditional Social Media aspects with fast and fun challenges. 12 | ## Inspiration behind the Project 13 | I often have the problem when meeting with friends, that after some hours we get bored and don't know what to do. 14 | With the appwrite hackathon coming up, I looked for solutions on how I could use my programming skills to create a fun activity for friends. 15 | An unexpected bonus of the app is how it encourages users to rediscover their own hometowns. By hunting for specific spots or completing challenges in places they might usually overlook, people can explore familiar surroundings in a totally new way. 16 | 17 | ## Tech Stack 18 | The app was mainly built using dart/flutter to ensure cross-platform compatibility. 19 | I also used Appwrite User Auth, File Storage and Databases 20 | 21 | ## Project Repo 22 | https://github.com/HumanBot000/SnapQuest-src 23 | 24 | ## Demo Video/Photos 25 | https://drive.google.com/file/d/1BtgDN9Z27dDbsrjLBEuyOJbkJ04TjLLZ/view?usp=sharing 26 | -------------------------------------------------------------------------------- /submissions/Vissipass.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: VissiPass 2 | 3 | ## GitHub handles of Team Members 4 | - @khushalsarode 5 | - @vishakhasarode 6 | - 7 | ## Project Title 8 | VissiPass: An web app for Creating Dynamic Visitor Pass! 9 | 10 | ## Project Description 11 | VissiPass is a streamlined digital pass generation system designed to manage and organize visitor requests efficiently for organizations. Built with React.js on the frontend and Appwrite on the backend, VissiPass provides a secure, user-friendly solution for visitor management that modernizes and enhances the traditional approach to tracking and verifying visitor information. 12 | 13 | ## Inspiration behind the Project 14 | The idea behind VissiPass is to create a more organized and secure environment for managing visitors. Many organizations face ongoing challenges with visitor tracking and security, especially with manual processes that can be unreliable. VissiPass addresses these issues by offering a fully digital solution that simplifies the visitor management process, making it both efficient and secure. 15 | 16 | 17 | ## Tech Stack 18 | - **Frontend:** React.js 19 | - **Backend:** Appwrite 20 | - **Appwrite Services Used:** Storage, Auth, Messenger, Database 21 | - **Authentication:** Appwrite Autonomous Auth, OAuth2 (Google, GitHub) 22 | 23 | ## Project Repo 24 | [GitHub Repository for VissiPass](https://github.com/Khushalsarode/appwrite-hackathon/) 25 | 26 | ## Demo Video/Photos 27 | [Demo Video on YouTube](https://youtu.be/Qmpllvp_ccc) 28 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | BSD 3-Clause License 2 | 3 | Copyright (c) 2024, Appwrite 4 | 5 | Redistribution and use in source and binary forms, with or without 6 | modification, are permitted provided that the following conditions are met: 7 | 8 | 1. Redistributions of source code must retain the above copyright notice, this 9 | list of conditions and the following disclaimer. 10 | 11 | 2. Redistributions in binary form must reproduce the above copyright notice, 12 | this list of conditions and the following disclaimer in the documentation 13 | and/or other materials provided with the distribution. 14 | 15 | 3. Neither the name of the copyright holder nor the names of its 16 | contributors may be used to endorse or promote products derived from 17 | this software without specific prior written permission. 18 | 19 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" 20 | AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 21 | IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 22 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE 23 | FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 24 | DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 25 | SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 26 | CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, 27 | OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE 28 | OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 29 | -------------------------------------------------------------------------------- /submissions/pipelineui.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: PipelineUI 2 | 3 | ## GitHub handles of Team Members 4 | - @riccardoperra 5 | 6 | ## Project Title 7 | PipelineUI 8 | 9 | ## Project Description 10 | Pipeline UI is a visual editor for creating and managing GitHub Actions workflows. 11 | Built with SolidStart and Appwrite, this tool simplifies the process of defining GitHub pipelines 12 | by allowing users to visually editing and update workflows. 13 | It automatically generates and updates the YAML configuration files, ensuring a seamless integration with 14 | GitHub thanks to their language server integration. 15 | 16 | ## Inspiration behind the Project 17 | We are using IntelliJ Idea at work, and one day in September my colleague and I were struggling a lot 18 | to create a workflow file for GitLab since that editor doesn't have any type of autocompletion. So why not create a builder from scratch only for that which allows you to create entire workflow files? 🤣 19 | 20 | ## Tech Stack 21 | This project has been built with SolidJS and SolidStart with enabled SSR, Vanilla Extract for styling and many other dependencies that 22 | has been linked in the [Project README](https://github.com/riccardoperra/pipelineui/tree/appwrite?tab=readme-ov-file#-technical-info) 23 | 24 | ## Project Repo 25 | 26 | https://github.com/riccardoperra/pipelineui/tree/appwrite 27 | 28 | Note: my submission is on appwrite branch 29 | 30 | ## Demo Video/Photos 31 | 32 | https://pipelineui-appwrite-env.up.railway.app/ 33 | 34 | https://github.com/user-attachments/assets/6399c1ba-c61c-49f3-a3f3-dca21778ef72 35 | -------------------------------------------------------------------------------- /submissions/sahil_todo.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: 2 | 3 | 4 | ## GitHub handles of Team Members 5 | sahilrawat001 6 | 15 | 16 | ## Project Title 17 | To-do list backend 18 | 23 | 24 | ## Project Description 25 | _What have you built during the hackathon?_ 26 | 27 | 32 | 33 | ## Inspiration behind the Project 34 | I've made simple todo list with user authentication 35 | 40 | 41 | ## Tech Stack 42 | Node.js 43 | express 44 | 49 | 50 | ### Usage of Appwrite 51 | DATABASES- I've used the database of appwrite to save data 52 | AUTH- I've used auth of appwrite for user signup login with the sessions of appwrite_ 53 | 68 | 69 | ## Project Repo 70 | [_Share a public repo link of your project_](https://github.com/sahilrawat001/app-write) 71 | 72 | 77 | 78 | ## Demo Video/Photos/Link 79 | _Share a 2-3 minute demo video or photos or a deployed link of your project_ 80 | 81 | 86 | 87 | ## Anything Else You Want To Share With Us? 88 | 89 | -------------------------------------------------------------------------------- /submissions/TimeCapsule.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Time Capsule 2 | 3 | ## GitHub handles of Team Members 4 | 5 | - @Motlakz 6 | 7 | ## Project Title 8 | 9 | Time Capsule - Memory Fort 10 | 11 | ## Project Description 12 | 13 | The project I created is **Memory Fort**, a digital time capsule platform that allows users to create, manage, and share memories that can be revealed at specific times in the future. Users can create both private and public time capsules, schedule reveal dates, and attach various types of media to their capsules. The platform features flexible views for browsing memories, advanced filtering options, and a user-friendly dashboard for managing capsules. 14 | 15 | ## Inspiration behind the Project 16 | 17 | The reason I chose this idea/project was to provide a unique way for individuals to preserve and share their memories. In a world where digital content is often fleeting, I wanted to create a platform that allows users to curate their experiences and share them with others at meaningful moments in the future. 18 | 19 | ## Tech Stack 20 | 21 | The technologies I used to build this project include: 22 | 23 | - Next.js 14+ (App Router) 24 | - TypeScript 25 | - Tailwind CSS 26 | - Shadcn/UI Components 27 | - Framer Motion 28 | - Appwrite Backend and Database 29 | - React Hook Form 30 | - Zod Validation 31 | 32 | ## Project Repo 33 | 34 | Share a public repo link of your project: 35 | [Time Capsule GitHub Repository](https://github.com/Motlakz/time-capsule) 36 | 37 | ## Demo Video/Photos 38 | 39 | Share a 2-3 minute demo video of your project: 40 | [Memory Fort Demo Video](https://youtu.be/W-bjdtY_HiI?si=ivySJxRig9hVNUC9) 41 | -------------------------------------------------------------------------------- /submissions/adventure-log.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: 2 | 3 | ## GitHub handles of Team Members 4 | 5 | - @ffex 6 | 7 | ## Project Title 8 | Adventure Log 9 | 10 | 11 | ## Project Description 12 | Do you ever play tabletop RPGs? Do you ever want to keep track of your adventures? Do you want to share your adventures with your friends? 13 | 14 | The project I created is all of this and more. It's a web app that allows you to create a "Adventure Log" for your tabletop RPG group starting with a simple audio recording. 15 | 16 | The app will transcribe the audio and allow you to review the transcription and then transform that into a journal style document write from the hand of your character. 17 | 18 | 19 | ## Inspiration behind the Project 20 | 21 | Recently I've start a campaign of D&D with some friends and my character is a mage with the intrest of writing a journal about their adventures. 22 | 23 | I've always thought it would be cool to have a digital version of this so I can share it with my friends and keep track of our adventures. 24 | 25 | So I took the Appwrite challenge to build this app and see if I can make it a reality. 26 | 27 | ## Tech Stack 28 | 29 | - Backend: 30 | - Appwrite Authentication 31 | - Appwrite Database 32 | - Appwrite Storage 33 | - Appwrite Functions 34 | - Python 35 | 36 | - Frontend: 37 | - Angular 38 | - PrimeNG 39 | 40 | - AI services: 41 | - AssemblyAI (Transcribe) 42 | - OpenAI GPT (Generate Journal) 43 | 44 | ## Project Repo 45 | 46 | https://github.com/ffex/adventure-log-journal 47 | 48 | ## Demo Video/Photos 49 | 50 | https://youtu.be/VjspxUhuasE -------------------------------------------------------------------------------- /submissions/spotfit-gym-manager.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: 2 | 3 | ## GitHub handles of Team Members 4 | 5 | - https://github.com/itcodehery 6 | - https://github.com/Achuabhal 7 | 8 | ## Project Title 9 | 10 | _SpotFit Gym Manager_ 11 | 12 | 15 | 16 | ## Project Description 17 | 18 | _What have you built during the hackathon?_ 19 | 20 | We have built a comprehensive gym management application called SpotFit Gym Manager. This application allows users to book slots in their gym, get AI assistance on any gym-related help, and book trainers for specified training sessions. 21 | 22 | ## Inspiration behind the Project 23 | 24 | _What is the story behind this project? Why did you choose to work on this specific idea?_ 25 | 26 | The inspiration behind this project was to streamline the gym management process and enhance the user experience. We noticed that many gym-goers face difficulties in booking slots and finding the right trainers. Our goal was to create a solution that addresses these issues efficiently. 27 | 28 | ## Tech Stack 29 | 30 | _How have you built this project? Mention the technologies/methods/platforms you used to build your project_ 31 | 32 | The project is built using React.JS for the frontend and Appwrite for backend services. We also integrated AI functionalities from Google's Gemini API to provide users with assistance on gym-related queries. 33 | 34 | ## Project Repo 35 | 36 | _Share a public repo link of your project_ 37 | 38 | https://github.com/itcodehery/appwrite-project 39 | 40 | ## Demo Video/Photos 41 | 42 | _Share a 2-3 minute demo video of your project_ 43 | 44 | https://youtu.be/bqTosM89Q0s 45 | -------------------------------------------------------------------------------- /spellsentry.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: SpellSentry 2 | 3 | ## GitHub handles of Team Members 4 | _Enter the GitHub handles of all your team members (including yourself) as separate bullet points_ 5 | 6 | - @madhav-relish 7 | - @sajdakabir 8 | 9 | 10 | ## Project Title 11 | _What is the name of your project?_ 12 | 13 | SpellSentry 14 | 15 | 16 | ## Project Description 17 | _What have you built during the hackathon?_ 18 | 19 | 20 | This project helps to identify the spelling/grammatical mistakes in a website. 21 | The user can enter the url of their webiste and with the help of AI they can get the 22 | tone of their content, fix spelling mistakes and grammer mistakes as well. 23 | 24 | 25 | ## Inspiration behind the Project 26 | _What is the story behind this project? Why did you choose to work on this specific idea?_ 27 | 28 | 29 | - I wanted to build something which is a real world problem and english is not a native language for a lot 30 | of people so they can struggle with bad SEO and website performance because of english mistakes. 31 | 32 | - We plan to add more language support in the future 33 | 34 | 35 | ## Tech Stack 36 | _How have you built this project? Mention the technologies/methods/platforms you used to build your project_ 37 | 38 | 39 | The technologies I used... 40 | - Next.js 41 | - Typescript 42 | - Node js 43 | - Express 44 | - Shadcn UI 45 | - Next Auth 46 | - Google AI 47 | 48 | 49 | 50 | ## Project Repo 51 | _Share a public repo link of your project_ 52 | 53 | 54 | https://github.com/madhav-relish/SpellSentry 55 | 56 | 57 | ## Demo Video/Photos 58 | _Share a 2-3 minute demo video of your project_ 59 | 60 | 63 | -------------------------------------------------------------------------------- /submissions/Acadai.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Acad.ai 2 | 3 | ## GitHub handles of Team Members 4 | _Enter the GitHub handles of all your team members (including yourself) as separate bullet points_ 5 | 6 | @jaibhedia 7 | 8 | ## Project Title 9 | _What is the name of your project?_ 10 | 11 | Acad.ai 12 | 13 | ## Project Description 14 | _What have you built during the hackathon?_ 15 | 16 | Acad.ai offers a dynamic, AI-driven learning platform that simplifies course creation and enhances engagement through interactive, personalized learning experiences. It provides intuitive, self-paced education for users of all backgrounds, removing barriers to accessible and efficient learning. 17 | 18 | 19 | ## Inspiration behind the Project 20 | _What is the story behind this project? Why did you choose to work on this specific idea?_ 21 | 22 | The reason I chose this idea/project was that it allows users to create comprehensive courses on any topic without extensive research. It organizes content into digestible chapters with interactive quizzes that enhance engagement and reinforce understanding. With real-time progress tracking and seamless password-less authentication, Acad provides a personalized and user-friendly platform. 23 | 24 | ## Tech Stack 25 | _How have you built this project? Mention the technologies/methods/platforms you used to build your project_ 26 | 27 | The technologies I used are 1) React.js 2) Node.js 3) Express.js 4) OpenAI API 5) Appwrite Cloud 28 | 29 | ## Project Repo 30 | _Share a public repo link of your project_ 31 | 32 | https://github.com/jaibhedia/Acadai-Appwrite 33 | 34 | ## Demo Video/Photos 35 | _Share a 2-3 minute demo video of your project_ 36 | 37 | https://drive.google.com/file/d/1C-0k80zwAvWzO6rptCMdNSH68km4Qeri/view?usp=sharing 38 | -------------------------------------------------------------------------------- /submissions/search_ideas_submission.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Search Data 2 | 3 | ## GitHub handles of Team Members 4 | _Enter the GitHub handles of all your team members (including yourself) as separate bullet points_ 5 | [@leonyangela](https://github.com/leonyangela) 6 | 7 | ## Project Title 8 | _What is the name of your project?_ 9 | [Search Ideas](https://github.com/leonyangela/appwrite-hf2024-search-ideas.git) 10 | 11 | ## Project Description 12 | _What have you built during the hackathon?_ 13 | The project I created is user must login and register inorder to add another ideas, they can search the ideas list based on name 14 | 15 | 16 | ## Inspiration behind the Project 17 | _What is the story behind this project? Why did you choose to work on this specific idea?_ 18 | The reason I chose this idea was because I'd like to gather list of ideas and user be able to search the idea from the list if the list is too long 19 | 20 | ## Tech Stack 21 | _How have you built this project? Mention the technologies/methods/platforms you used to build your project._ 22 | The technologies I used is React, and Appwrite as Auth & database, I also use React Provider for state management. 23 | 24 | ### Usage of Appwrite 25 | _Highlight any Appwrite products used within the project._ 26 | 27 | - Appwrite Databases 28 | 29 | I used Appwrite Databases to store the ideas data 30 | 31 | - Appwrite Auth 32 | 33 | I used Appwrite Auth to store any registration user 34 | 35 | ## Project Repo 36 | _Share a public repo link of your project_ 37 | https://github.com/leonyangela/appwrite-hf2024-search-ideas.git 38 | 39 | ## Demo Video/Photos/Link 40 | _Share a 2-3 minute demo video or photos or a deployed link of your project_ 41 | ![image](https://github.com/user-attachments/assets/17e5091e-0536-4f20-8e02-ad7a0c80d3c3) 42 | 43 | ## Anything Else You Want To Share With Us? 44 | 45 | -------------------------------------------------------------------------------- /submissions/krishi_mitra.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Krishi Mitra 2 | 3 | ## GitHub handles of Team Members 4 | - [@DChitale](https://github.com/DChitale/) 5 | 6 | 7 | ## Project Title 8 | Krishi Mitra 9 | 10 | ## Project Description 11 | Krishi Mitra is a web platform designed to help farmers easily find relevant government schemes based on their input, such as income, crop type, and other factors. This tool aims to simplify access to available benefits, subsidies, and programs, empowering farmers with the resources they need to grow and thrive. 12 | 13 | ## Inspiration behind the Project 14 | The inspiration behind Krishi Mitra came from the challenges faced by farmers in accessing government schemes due to lack of awareness or complex processes. We chose this idea to bridge the gap between farmers and the benefits provided by the government, ensuring they can take advantage of opportunities that would otherwise be overlooked. 15 | 16 | ## Tech Stack 17 | - Next.js for the frontend 18 | - Appwrite for authentication and backend services 19 | - Appwrite for managing databases and backend storage 20 | - Vercel for deployment 21 | ### Usage of Appwrite 22 | - **Appwrite Databases**: Used for storing farmer inputs and matching them to relevant schemes. 23 | - **Appwrite Storage**: Used to securely store and retrieve important data. 24 | - **Appwrite Filters**: Used to filter the schemes based on the Input. 25 | 26 | ## Project Repo 27 | [GitHub Repo Link](https://github.com/DChitale/krishi-mitra) 28 | 29 | ## Demo Video/Photos/Link 30 | [Deployed Project Link](https://krishi-mitra-web.vercel.app/) 31 | 32 | 33 | ## Anything Else You Want To Share With Us? 34 | This project is a step towards making technology accessible to rural areas and simplifying farmers' lives by providing them with vital information in a user-friendly way. 35 | -------------------------------------------------------------------------------- /submissions/devx.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: DevX 2 | 3 | ## GitHub handles of Team Members 4 | - @ankit-0369 5 | 6 | 7 | ## Project Title 8 | DevX - platform for devlopers 9 | 10 | 13 | 14 | ## Project Description 15 | DevX is a blogging application, where a user can register/login using email and password, or login through magic link and read blogs written by other devs. User can write a blog and can publish. A user can read blog of others and can CREATE, READ, DELETE, UPDATE his own written blogs. This project uses Appwrite as backend and database services for handling authentication, asset storage etc. This project has developed under the appwrite hackathon by @ankit-0369 with future plans of integrating real time user connection, implementation of community management routes in the application. 16 | 17 | 20 | 21 | ## Inspiration behind the Project 22 | DevX is a platform for developers. I inspired from other blogging platforms and thought of developing a platform where devs can share their knowledge and can engage in a community of same minds and can learn and teach others also. 23 | 24 | 25 | ## Tech Stack 26 | - **React.js** for the frontend, providing a fast and seamless user experience. 27 | - **Tailwind CSS** for a responsive design. 28 | - **Appwrite** as the backend for user authentication, database management, and secure data storage. 29 | - **Redux Toolkit** for better state management of the application and control over the themes. 30 | 31 | 32 | ## Project Repo 33 | https://github.com/ankit-0369/devx 34 | 35 | 38 | 39 | ## Demo Video/Photos 40 | [Demo video](https://drive.google.com/file/d/1Ps_NLCQfZF0vCht5yJAKN1M_wiq78o-t/view?usp=sharing) 41 | 42 | 45 | -------------------------------------------------------------------------------- /submissions/anon-messenger.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Anonynous Messenger 2 | 3 | ## GitHub handles of Team Members 4 | - [@SahilKumarIN](https://github.com/SahilKumarIN) 5 | 6 | ## Project Title 7 | Anonymous Messenger 8 | 9 | ## Project Description 10 | Anon-Messenger – a safe space for anonymous communication. Whether you want to create a private room for open discussions, share a secure link for feedback, or communicate without revealing your identity, Anon-Messenger makes it easy and secure. Users can sign up, create rooms, and share the link with anyone. The person with the link can post messages without fear of tracking or identification. 11 | 12 | ## Inspiration behind the Project 13 | The inspiration behind **Anonymous Messenger** was the need for a simple yet powerful tool to help users anonymously message their feelings/confess their feelings. This project inspires from ngl which is an anonymous messagenger platform to send their confession. 14 | 15 | ## Tech Stack 16 | - **React**: For building the frontend. 17 | - **TailwindCSS**: To style the user interface. 18 | - **Appwrite**: As a backend service for secure data management, including databases and authentication. 19 | 20 | ### Usage of Appwrite 21 | - **Appwrite Databases**: I used Appwrite Databases to store event details such as roomDetails, roomDescription, date, time, and users. 22 | - **Appwrite Authentication**: Appwrite Authentication was implemented to ensure the create, update, or delete rooms messages. 23 | 24 | ## Project Repo 25 | [Anon messenger GitHub Repo](https://github.com/SahilKumarIN/anon-messenger) 26 | 27 | ## Demo Video/Photos/Link 28 | Check out the project here: 29 | 30 | 31 | https://anon-msngr.netlify.app/ 32 | 33 | 34 | 35 | 36 | ## Anything Else You Want To Share With Us? 37 | This project is scalable and we have in mind to work on it in future with a good team and make it a scalabe and valuable application. 38 | -------------------------------------------------------------------------------- /submissions/BugBank.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: BugBank 2 | 3 | ## GitHub handles of Team Members 4 | - [@SiddharthSahani](https://github.com/SiddharthSahani) 5 | - [@NishumbhShah](https://github.com/nisooom) 6 | - [@TejasBhovad](https://github.com/TejasBhovad) 7 | - [@HamzaMurghay](https://github.com/HamzaMurghay) 8 | 9 | ## Project Title 10 | BugBank 11 | 12 | ## Project Description 13 | We made a project called BugBank, designed to simplify bug management for developers. With AI-generated summaries that offer quick insights, you can stay on top of critical issues effortlessly. Collaborate seamlessly with your team, track progress in real time, and enhance your workflow—all in one intuitive platform. 14 | 15 | ## Inspiration behind the Project 16 | The reason we chose this project is to address the common challenges developers face in bug management. We recognized that traditional methods often lead to confusion and inefficiency, hindering productivity. By integrating AI and user-friendly features, we aimed to create a solution that streamlines the bug management but also enhances collaborations. 17 | 18 | ## Tech Stack 19 | We used 20 | - **Frontend**: NextJs (meta-framework for React), ShadCN (headless ui), TailwindCSS (good dx for styling) 21 | - **Backend**: Appwrite, FastAPI (api routes for ollama) 22 | - **Appwrite**: Database, Auth 23 | 24 | ## Project Repo 25 | - [Public Repo](https://github.com/erga-labs/bug-bank) 26 | - [Deployed Repo](https://github.com/nisooom/bug-bank) 27 | - [npm package](https://github.com/TejasBhovad/bugbank-package) 28 | 29 | ## Demo Video/Photos 30 | - [Site Link](https://bugbank.vercel.app) 31 | - [Demo Video (Outdated)](https://www.youtube.com/watch?v=f_mSsfRukG0) 32 | 33 | ### Images 34 | ![Demo Image - 1](https://raw.githubusercontent.com/erga-labs/bug-bank/refs/heads/main/github/bb_3.jpeg) 35 | ![Demo Image - 2](https://raw.githubusercontent.com/erga-labs/bug-bank/refs/heads/main/github/bb_2.jpeg) 36 | -------------------------------------------------------------------------------- /submissions/launchbase.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Launch Base 2 | 3 | ## GitHub handles of Team Members 4 | _Enter the GitHub handles of all your team members (including yourself) as separate bullet points_ 5 | 6 | - @aditya000099 7 | 8 | 9 | ## Project Title 10 | _What is the name of your project?_ 11 | 12 | Launch Base 13 | 14 | 15 | ## Project Description 16 | _What have you built during the hackathon?_ 17 | 18 | Launch Base is a ready-to-use starter template that helps you kickstart your SaaS app quickly. It’s built with Appwrite as the backend to handle all core operations like authentication, database, and storage, so you can focus on building features without worrying about the setup. Perfect for getting your SaaS idea off the ground fast! 19 | 20 | ## Inspiration behind the Project 21 | _What is the story behind this project? Why did you choose to work on this specific idea?_ 22 | 23 | Launch Base came from seeing developers spend too much time on repetitive setup tasks like authentication, databases, and storage instead of focusing on their core ideas. I built it to provide a solid, ready-to-use foundation with Appwrite, allowing developers to skip the basics and start building faster. The goal is simple: help others launch their SaaS projects quickly and efficiently. 24 | 25 | ## Tech Stack 26 | _How have you built this project? Mention the technologies/methods/platforms you used to build your project_ 27 | 28 | NextJS 29 | Appwrite 30 | Stripe, Mailgun, PayPal 31 | Tailwind 32 | 33 | ## Appwrite Usage 34 | 35 | Used appwrite cloud to create a fully functional saas - used Auth, Databases 36 | Will keep adding more features to it! 37 | 38 | ## Project Repo 39 | _Share a public repo link of your project_ 40 | 41 | https://github.com/aditya000099/launchbase 42 | 43 | ## Demo Video/Photos 44 | _Share a 2-3 minute demo video of your project_ 45 | 46 | https://youtu.be/A1UsaEWjIqA 47 | 48 | https://i.imgur.com/ZFa9ok2.png 49 | -------------------------------------------------------------------------------- /submissions/QuickShare.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: QuickShare 2 | 3 | ## GitHub handles of Team Members 4 | - [@mayank0274](https://github.com/mayank0274) 5 | 6 | ## Project Title 7 | 8 | QuickShare 9 | 10 | ## Project Description 11 | 12 | QuickShare is file sharing web application , with QuickShare you can share files via uploading and converting them into links that remains valid for 24 hrs . In addition to this we can password protect download i.e we can set a pin and user will be required to enter pin in order to download that file. 13 | 14 | ## Inspiration behind the Project 15 | As a student, I am always looking for ways to improve my productivity and collaboration. I often find myself needing to share files with classmates, and other students. However, traditional file sharing methods can be cumbersome and time-consuming. 16 | With QuickShare we can share files quickly as there is no need of repetitive signup/login on different platforms , take care of your privacy as you can password protect download and expirable links.I believe that QuickShare will be a valuable tool for students and professionals alike. It will help them to share files quickly and easily. 17 | 18 | ## Tech Stack 19 | 20 | - Next.js 15 for frontend and creating api's 21 | - Chakra UI for styling 22 | 23 | ### Uses of appwrite 24 | 25 | - **Database** :- For storing file entry records and passowrds(in hash format) 26 | - **Storage** :- for storing files 27 | - **Functions** :- I used two clean up functions which runs everyday at 12:00 am 28 | - **Databse cleanup** => Delete entries from databse which are 24 hrs old 29 | - **Storage cleanup** => Delete files from storage bucket which are 24 hrs old 30 | 31 | ## Project Repo 32 | 33 | Github repo : [QuickShare](https://github.com/mayank0274/quick-share) 34 | 35 | ## Demo Video/Photos 36 | 37 | - Live preview :- https://quick-share-yjx1.vercel.app/ 38 | 39 | 40 | https://github.com/user-attachments/assets/0199879e-b712-46f3-aa46-98e4aaf45bf1 41 | 42 | -------------------------------------------------------------------------------- /submissions/ScholarLift.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: ScholarLift 2 | 3 | ## GitHub handles of Team Members 4 | 5 | 6 | @asmb123 7 | 8 | @prathmesh703 9 | 10 | @Lokeshranjan8 11 | 12 | @chiragmalik2612 13 | 14 | ## Project Title 15 | 16 | 17 | ScholarLift 18 | 19 | ## Project Description 20 | 21 | 22 | Scholarlift is an educational crowdfunding platform that connects students in need of financial support with generous donors. 23 | 24 | ## Inspiration behind the Project 25 | 26 | Scholarlift was inspired by the belief that education should be accessible to all, regardless of financial barriers. Many talented individuals struggle to fund their studies, prompting us to create a platform connecting them with supportive donors. Our goal is to empower students to achieve their academic dreams and foster a community that believes in the transformative power of education. 27 | 28 | 29 | 30 | 31 | 32 | ## Tech Stack 33 | 34 | 35 | ScholarLift was made in NextJs 14 using appwrite cloud at its backend. 36 | * Used Typescript and Tailwind for developer experience 37 | * Used Appwrite's: 38 | - Auth for authentication 39 | - Database for storing the user's crowdfunding details 40 | - Storage for storing any images 41 | 42 | ## Project Repo 43 | 44 | 45 | https://github.com/asmb123/hacktober_project24 46 | 47 | ## Demo Video/Photos 48 | 49 | https://drive.google.com/file/d/1kVIuYlekGfLGUSfpfwn9ruiNyi8EZ7RN/view?usp=sharing 50 | 51 | -------------------------------------------------------------------------------- /submissions/means-HF.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Means-HF 2 | 3 | 4 | ## GitHub handles of Team Members 5 | 6 | - @gitadityakumar 7 | ## Project Title 8 | 9 | Means-HF 10 | 11 | ## Project Description 12 | Means-hf is a powerful learning tool that helps users improve their English vocabulary while watching YouTube videos. Built for the Appwrite Hackathon, this project combines a browser extension with a web application to create an seamless learning experience. 13 | 14 | 15 | ## Inspiration behind the Project 16 | One day, I was watching a YouTube video and struggled to understand a few words; naturally, I don’t know every word in English. Around that time, I was also learning web development, which inspired me to create a platform that could track my YouTube history (with my consent) and allow me to extract and understand words and meanings from videos. I also thought this could work as a note-taking app, using YouTube content as a source. Once I started building it, I carefully chose my tech stack and made slow progress until I learned about this hackathon. That gave me the motivation to speed up the project, so I focused on the essential feature of extracting words and meanings. 17 | 18 | ## Tech Stack 19 | Here is tech used in project 20 | - **Frontend**: Built with Next.js. 21 | - **Authentication**: Appwrite's Auth for secure user authentication. 22 | - **Browser Extension**: Built with plasmo framework and it tracks video history on YouTube and sends selected videos to the primary backend. 23 | - **Backend Server**: 24 | - Api server(BE1) 25 | it uses bull mq for queue 26 | - Worker 27 | it picks up task from queue 28 | 29 | 30 | ### Usage of Appwrite 31 | - Appwrite Auth 32 | 33 | I used Appwrite Auth to secure my next app 34 | it is also used in backend server and worker 35 | 36 | ## Project Repo 37 | 38 | https://github.com/gitadityakumar/Means-hf24-codebase 39 | 40 | ## Demo Video/Photos/Link 41 | 42 | Here is Youtube video link 43 | 44 | https://www.youtube.com/watch?v=e8tw_CJply4 45 | 46 | 47 | 48 | 49 | -------------------------------------------------------------------------------- /submissions/entrepreneurs-hub-web-app.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Entrepreneurs' Hub 2 | 3 | ## GitHub handles of Team Members 4 | @eliezerjoel 5 | 6 | ## Project Title 7 | Entrepreneurs' Hub 8 | 9 | 10 | ## Inspiration behind the Project 11 | I am currently studying a course called basic entrepreneurship, where students are required to form teams of five people and come up with a unique creative venture which solves a preoblem in the community. Our lecturer for this course has always struggled with trying to remember ventures that have been done before by prior students, in order to show off their problem solving skills and also motivate our creativity. Some times she can't really remember how a particular venture was made, or who made it. She believes that all knowledge should be shared, because it could be beneficial when others go with it back home or to their different communities. In this month of celebrating open source, i also believe that knowlede should be open sourced, so that people all over the world can access it and make any modifications to use it to improve their communities. That is why I cmae up up with this unique venture, that is a web application, so that the knowledge can be transfered from place to place, and across all generations. 12 | 13 | ## Project Description 14 | Entrepreneurs' Hub is a platform for students to upload their business ventures, images, share their knowledge, how they came up with those ventures, View other people's ventures and react on them 15 | 16 | ## Tech Stack 17 | I used 18 | Next JS to develop the frontend as well as backend 19 | Tailwind css for styling 20 | Appwrite Auth to sign up and login users 21 | Appwrite database to store and retrieve ventures and organisations data 22 | Appwrite Storage to save media files like ventures images and write-up documents 23 | 24 | ## Project Repo 25 | https://github.com/eliezerjoel/entrepreneurhub 26 | 27 | ## Hosted project 28 | https://enthub-seven.vercel.app/ 29 | 30 | ## Demo Video/Photos 31 | https://drive.google.com/drive/folders/1SuPP2403_DQDJgSlSY2Yc6sWR4HNPL06?usp=drive_link 32 | -------------------------------------------------------------------------------- /submissions/FeedbackSO.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: FeedbackSO 2 | 3 | ## Project Title 4 | FeedbackSO 5 | 6 | ## Project Description 7 | FeedbackSO is a single feedback management platform for managing feedbacks. We can easily create pages and share it other people to get 8 | their feedbacks. We can also import posts as feedbacks from social media and can share and import the results in our app 9 | or we can share them directly. 10 | We can also integrate them to other systems like wix, html pages, wordpress, next app, react app, svelte app, etc with our widget system. 11 | Customisable widgets plus endpoints for total customisation 12 | 13 | ## Inspiration behind the Project 14 | I created one SaaS pickpalette and tried to build a robust feedback system. And again while building another app, I again rebuild that. And 15 | mostly it is a tedious and mudane work and it takes time. So why not building a single platform for managing them only time and just integrate 16 | it with other projects. 17 | 18 | ## Tech Stack 19 | Next js , appwrite, trigger dot dev and vercel. 20 | I used next js as my Backend for frontend and also the api layer. 21 | Use of appwrite - 22 | 1. Database and remote configs. 23 | 2. Event driven queues. With appwrite I just have to connect events to the db and on data change and just have to trigger the actions. 24 | Mainly for scraping. 25 | 3. For primary authentication. 26 | 4. Building the SSO wrapper for widgets along with the next js api routes and appwrite oauth 27 | 5. Functions for actions 28 | 29 | I used trigger dot dev for twitter scraping using browsers which is not supported in appwrite functions 30 | 31 | I used react js and next js api routes for building the widget system. 32 | ## Project Repo 33 | Live app -> https://feedback-io-beta.vercel.app/ 34 | Repos 35 | Main app -> https://github.com/ArnabChatterjee20k/FeedbackIO 36 | Widgets -> https://github.com/ArnabChatterjee20k/feedbackio-widget 37 | Widget example -> https://github.com/ArnabChatterjee20k/feedback-io-examples 38 | 39 | ## Demo Video/Photos 40 | https://youtu.be/wlEWSAAuB70 41 | -------------------------------------------------------------------------------- /submissions/TicTacToe-Shift.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: TicTacToe-Shift 2 | 3 | ## GitHub handles of Team Members 4 | _Enter the GitHub handles of all your team members (including yourself) as separate bullet points_ 5 | 6 | 7 | - @Sou6161 8 | 9 | 10 | ## Project Title 11 | _What is the name of your project?_ 12 | 13 | 14 | TicTacToe-Shift 15 | 16 | ## Project Description 17 | _What have you built during the hackathon?_ 18 | 19 | 20 | The project I created is about tic Tac Toe Shift classic game which combines strategy and skill, challenging you to think ahead and outmaneuver , So unlock your cognitive potential of your mind and engage your mind with addictive gameplay and master the shift and claim your victory today!" 21 | 22 | 23 | ## Inspiration behind the Project 24 | _What is the story behind this project? Why did you choose to work on this specific idea?_ 25 | 26 | 27 | The reason I chose this project was to learn new things in web development especially as something unique or something with a little bit of twist which engages the player , thats why i created this game classic , regular game with a twist so that it can be played by anyone also its engages the user or player in 1v1 to win the game because there can only be "one winner😎" 28 | 29 | 30 | ## Tech Stack 31 | _How have you built this project? Mention the technologies/methods/platforms you used to build your project_ 32 | 33 | 34 | The technologies I used to make this game is -- > React(with bundler vite) , Tailwind css , Lenis(For smooth scrolling) , Socket.io(Web Sockets) , node.js 35 | 36 | 37 | 38 | ### Usage of Appwrite 39 | 40 | - Appwrite Authentication 41 | 42 | i used appwrite authentication so that player can create their account and participate in discussion and players can chat about the game 43 | 44 | 45 | 46 | ## Project Repo 47 | _Share a public repo link of your project_ 48 | 49 | https://github.com/Sou6161/shift-tic-tac-toe 50 | 51 | 52 | ## Demo Video/Photos 53 | _Share a 2-3 minute demo video of your project_ 54 | 55 | 56 | https://youtu.be/vRRZq1_g0Ic?si=Af69MCbV57vh8yd2 57 | 58 | 59 | ## Project Live Link(Deployable) 60 | 61 | 62 | https://shift-tic-tac-toe.vercel.app/ 63 | -------------------------------------------------------------------------------- /submissions/careplus.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: CarePlus - Healthcare Management System 2 | 3 | ## GitHub handles of Team Members 4 | [@abhi9ab](https://github.com/abhi9ab) 5 | 6 | ## Project Title 7 | CarePlus: Healthcare Management System 8 | 9 | ## Project Description 10 | A healthcare patient management application that allows patients to easily register, book, and manage their appointments with doctors, featuring administrative tools for scheduling, confirming, and canceling appointments, along with SMS notifications, all built using Next.js and Appwrite. 11 | 12 | ## Inspiration behind the Project 13 | The goal was to create an application that simplifies the process of registering patients, booking, and managing appointments with doctors. The focus is on ease of use, responsiveness, and incorporating features like SMS notifications for appointment confirmations and secure file storage using Appwrite 14 | 15 | ## Tech Stack 16 | Next.js 17 | Appwrite 18 | Typescript 19 | TailwindCSS 20 | ShadCN 21 | Twilio 22 | 23 | ## Usage of Appwrite 24 | Appwrite Authentication: Manages user sign-ups, logins, and session maintenance. 25 | Appwrite Databases: Stores patient and appointment data. 26 | Appwrite Storage: Securely stores profile pictures and healthcare-related documents, ensuring privacy and easy retrieval. 27 | 28 | ## Project Repo 29 | [GitHub Repository](https://github.com/abhi9ab/Healthcare-Platform) 30 | 31 | ## Demo Video/Photos 32 | ![careplus 1](https://github.com/user-attachments/assets/8dd592be-17ab-4fe6-bb20-31d523efecc3) 33 | ![careplus 2](https://github.com/user-attachments/assets/9fbd1b7b-70f0-484c-950c-8cb38ce37dad) 34 | ![careplus 3](https://github.com/user-attachments/assets/1ded860e-0be2-49e4-8142-db86a86622ab) 35 | ![careplus 4](https://github.com/user-attachments/assets/c238783c-0c21-4952-b5df-e7653a48bfc8) 36 | 37 | 38 | ## Anything Else You Want to Share With Us? 39 | Patients can easily register, book, and manage their appointments with doctors, while administrators have tools to schedule, confirm, and cancel appointments. The platform also includes SMS notifications for appointment confirmations and leverages secure file storage using Appwrite, ensuring a responsive and efficient user experience across all devices. 40 | -------------------------------------------------------------------------------- /submissions/renest-01.md: -------------------------------------------------------------------------------- 1 | 2 | # **Re-nest (To Donate Reusable Items)** 3 | 4 | ### **GitHub Handles of Team Members:** 5 | - `harshbisht27` 6 | 7 | ### **Project Title:** 8 | - **Re-nest** 9 | 10 | ### **Project Description:** 11 | - Re-nest provides a convenient way for individuals to donate reusable items like clothes, toys, and furniture directly from their doorstep. Partnering with trusted NGOs, it ensures donations reach those in need, encouraging environmental sustainability and social responsibility. Users can schedule a pickup or drop off items, with donors receiving rewards through brand partnerships. 12 | 13 | ### **Features:** 14 | - **Easy Donation Scheduling:** Book a doorstep pickup for donations. 15 | - **NGO Partnerships:** Ensures items are delivered to those who need them most. 16 | - **Rewards for Donors:** Receive gifts or vouchers from brand partners. 17 | - **Sustainability:** Supports a circular economy by reusing and redistributing items. 18 | - **Corporate Collaborations:** Engages companies in CSR and employee engagement programs. 19 | 20 | ### **Inspiration Behind the Project:** 21 | - Inspired by noticing how many reusable products often go to waste in daily life. Seeing items that could be useful to others discarded, I created Re-nest to help ensure these products find a second life. 22 | 23 | ### **Tech Stack:** 24 | - **Python:** Handles backend services, requests, and logic. 25 | - **React:** Used for building an interactive user interface. 26 | - **Mongoose:** Manages MongoDB for storing donation records and user data. 27 | - **Express:** Builds APIs and handles requests. 28 | - **Node.js:** Server-side JavaScript execution. 29 | 30 | ### **Usage of Appwrite:** 31 | - **Appwrite Contact:** Manages data for individuals who wish to reach out. 32 | 33 | ### **Project Repository:** 34 | - [GitHub Repository](https://github.com/harshbisht27/renest-01) 35 | 36 | ### **Demo Video/Photos/Link:** 37 | - [Re-nest App Demo](https://harshbisht27-renest-appwrite.netlify.app/) 38 | 39 | ### **Additional Information:** 40 | - This open-source project aims to enhance donation systems with modern authentication and secure data handling. It’s flexible, adheres to coding standards, and is open to contributions and customization. 41 | -------------------------------------------------------------------------------- /submissions/cpp-sdk-appwrite.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Appwrite SDK Support For C++ 2 | 3 | ## GitHub handles of Team Members 4 | 5 | - [@pooranjoyb](https://github.com/pooranjoyb) 6 | - [@sristy17](https://github.com/sristy17) 7 | 8 | ## Project Title 9 | ### Appwrite SDK for C++ 10 | 11 | ## Project Description 12 | Appwrite C++ SDK is the SDK designed to integrate Appwrite’s powerful backend capabilities into C++ applications. Built from scratch, this SDK allows C++ developers to leverage Appwrite’s comprehensive suite of tools, including database management, file storage, and real-time data processing, without the need for workarounds or external dependencies. 13 | 14 | ## Inspiration behind the Project 15 | Our main aim was to enable C++ developers to easily access Appwrite’s powerful backend services, which were previously unavailable in C++. While Appwrite provides SDKs for popular languages like Node.js, Python, Dart, etc, C++ support was missing. Offering C++ support expands Appwrite's reach, encouraging adoption across more development communities and enabling new possibilities in cross-platform and native C++ applications. 16 | 17 | ## Tech Stack 18 | - C++ Programming Language 19 | - Appwrite REST APIs 20 | - Postman for API-Testing 21 | 22 | ## Usage of Appwrite 23 | - **Appwrite Authenticaton** - Communication with Appwrite Authentication Services (Creating Account & Sessions) 24 | - **Databases** - Integrated REST APIs to create update & delete databases, collections, attributes, documents & indexes. 25 | - **Bucket** - Also integrated the same for creating Bucket and listing files, etc 26 | - **Health** - REST APIs Health Status of Appwrite Account. 27 | 28 | ## Project Repo 29 | 30 | [https://github.com/pooranjoyb/cpp-sdk-appwrite](https://github.com/pooranjoyb/cpp-sdk-appwrite) 31 | 32 | ## Demo Video/Photos 33 | [https://www.youtube.com/watch?v=L1D-Ibe7XeU](https://www.youtube.com/watch?v=L1D-Ibe7XeU) 34 | 35 | ## Anything Else You Want To Share With Us? 36 | This C++ SDK for Appwrite is still in its early prototype stage, and we are incredibly excited to keep building and expanding its features. We're actively working to bring full Appwrite support to C++, from advanced database handling to enhanced authentication and storage functionalities. 37 | -------------------------------------------------------------------------------- /submissions/devpath.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: DevPath 2 | 3 | ## GitHub handles of Team Members 4 | _Enter the GitHub handles of all your team members (including yourself) as separate bullet points_ 5 | 6 | - @dipanshurdev 7 | - @Jaydeeprawat17 8 | 9 | 10 | ## Project Title 11 | _What is the name of your project?_ 12 | 13 | DevPath 14 | 15 | ## Project Description 16 | _What have you built during the hackathon?_ 17 | 18 | 19 | Devpath is a beginner-friendly platform built with Next.js and Appwrite to guide new developers in tech. Inspired by roadmap.sh, Devpath offers clear, structured roadmaps for roles like Fullstack and Frontend Developer. Each roadmap outlines essential skills and technologies, paired with free resources—articles, tutorials, and courses—handpicked to simplify learning. With Devpath, newcomers can follow a streamlined, step-by-step path to build confidence and succeed in their tech careers. 20 | 21 | ## Inspiration behind the Project 22 | _What is the story behind this project? Why did you choose to work on this specific idea?_ 23 | 24 | The inspiration behind Devpath came from the need for a clear, accessible guide for beginners in tech. With so many learning resources available, it’s easy for newcomers to feel overwhelmed or unsure where to start. Platforms like roadmap.sh inspired us to create Devpath as a structured solution that not only outlines specific learning paths for roles like Fullstack or Frontend Developer but also pairs each step with quality, free resources. Our goal is to help aspiring developers confidently build foundational skills without the usual confusion, making tech careers more accessible to everyone. 25 | 26 | 27 | ## Tech Stack 28 | _How have you built this project? Mention the technologies/methods/platforms you used to build your project_ 29 | 30 | NextJS 31 | Appwrite 32 | Reactflow 33 | Tailwind 34 | 35 | ## Appwrite Usage 36 | 37 | I used Appwrite Cloud to build the database for roadmaps and will add authentication and other feature in future." 38 | 39 | ## Project Repo 40 | _Share a public repo link of your project_ 41 | 42 | https://github.com/dipanshurdev/devpath 43 | 44 | ## Demo Video/Photos 45 | _Share a 2-3 minute demo video of your project_ 46 | 47 | [Deployed site](https://devpath.netlify.app/) -------------------------------------------------------------------------------- /submissions/kitchen_pal.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: KitchenPal 2 | 3 | 4 | ## GitHub handles of Team Members 5 | - @highflyer910 6 | - @maxdevjs 7 | 8 | 9 | ## Project Title 10 | KitchenPal 11 | 12 | ## Project Description 13 | KitchenPal is a recipe management app that helps users save, organize, and generate recipes based on their dietary preferences. It integrates Appwrite for authentication and database management, along with the Gemini Generate API for AI-generated recipes. Additionally, the app supports multiple themes, enabling users to personalize their interface. 14 | 15 | ## Inspiration behind the Project 16 | KitchenPal came from the simple, everyday challenge of figuring out what to cook, especially when trying to stick to dietary preferences or use up ingredients you already have. We wanted to build something that takes the stress out of meal planning by letting you save favorite recipes and easily generate new ones based on what’s in your pantry. It’s a way to make cooking more fun, organized, and personalized, so people can enjoy healthier meals without the hassle. 17 | 18 | ## Tech Stack 19 | The technologies I used: 20 | - **Next.js** for the frontend, providing a fast and seamless user experience. 21 | - **Material UI** for a smooth, responsive, and visually appealing interface. 22 | - **Appwrite** as the backend for user authentication, database management, and secure data storage. 23 | - **Google’s Gemini Generate API** for personalized AI-generated recipes. 24 | - **React Context API** to manage theme switching between different color schemes. 25 | - **ESLint** to ensure clean and maintainable code. 26 | 27 | 28 | ### Usage of Appwrite 29 | - **Appwrite Authentication**: Used for managing user sign-ups, logins, and secure access to personal data. 30 | - **Appwrite Database**: Stored user-generated content such as recipes and dietary preferences. 31 | 32 | ## Project Repo 33 | https://github.com/highflyer910/kitchenpal 34 | 35 | ## Demo Video/Photos/Link 36 | https://kitchenpal.vercel.app/ 37 | 38 | ## Anything Else You Want To Share With Us? 39 | I’m grateful for the opportunity to participate in this hackathon alongside my friend. Working on this project allowed us to explore Appwrite for the first time and deepen our understanding of its capabilities. We look forward to your feedback! 40 | 41 | -------------------------------------------------------------------------------- /RULES.md: -------------------------------------------------------------------------------- 1 | # Hackathon Rules 2 | 3 | - All team members must register on the [Hackathon Sign Up page](https://apwr.dev/htf24-hackathon). 4 | 5 | - Hackers must form a team of 1 - 4 members. Solo hackers are allowed, however, building a team is encouraged. 6 | 7 | - The hackathon will start at `Oct 1st, 12 AM PT` and end at `Oct 31st, 11:59 PM PT`, you work on your hack during the allotted time only. Older projects will not be allowed. We will require you to build your project during the hackathon month only. 8 | 9 | - Your submission(s) must feature the usage of at least one Appwrite product (i.e., Auth, Databases, Storage, Functions, Realtime, and/or Messaging). Using more than one Appwrite product is encouraged. 10 | 11 | - You are encouraged to submit your project on [Built With Appwrite](https://builtwith.appwrite.io) after the hackathon. 12 | 13 | - It is mandatory to use Appwrite Cloud during this hackathon. You can [avail free Cloud credits](https://apwr.dev/hacktoberfest) for your team to use during the hackathon. 14 | 15 | - Projects will be judged based on the following criteria: 16 | 1. **Product Thinking** 17 | - Usefulness of the project in a real-world scenario. 18 | - Completeness of the features implemented. 19 | 2. **UI/UX** 20 | - The overall look, layout, color usage, and positioning in the application. 21 | 3. **Code** 22 | - `(clean code, proper naming conventions, use of linter);` 23 | - Use of best practices. 24 | 4. **Usage of Appwrite** 25 | - Is Appwrite central to the functioning of your project? 26 | - How many and how well the different Appwrite services have been leveraged 27 | 28 | - Hackers are allowed to work on multiple teams and submit multiple projects. 29 | 30 | - Only one member from each team will submit the project. They must add the GitHub usernames of all other team members in the submission. 31 | 32 | - There are no specified themes. Hackers are free to build on whatever idea they like. 33 | 34 | - The code for your project must be open-source. You must add the codebase of your project to a repo on your account, make the repo public, and share the link in your submission. 35 | 36 | - The intellectual property of your code belongs only to your team. 37 | 38 | - By participating in the hackathon, you agree to the [Code of Conduct](CODE_OF_CONDUCT.md). 39 | -------------------------------------------------------------------------------- /submissions/Auth_with_Appwrite.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Secure Authentication with Appwrite 2 | 3 | ## GitHub Handle 4 | - @rajchaudhary99 5 | 6 | ## Project Title 7 | Secure Authentication with Appwrite in React 8 | 9 | ## Project Description 10 | This project implements a secure and efficient authentication system in a React application using Appwrite’s backend-as-a-service (BaaS) platform. Built with developers in mind, this project demonstrates how to integrate Appwrite for user authentication, registration, and secure session management in a React environment. 11 | 12 | ## Inspiration Behind the Project 13 | As applications increasingly require robust and secure authentication systems, Appwrite offers a simple yet powerful solution for handling user authentication and session management. This project showcases how to leverage Appwrite’s features to quickly set up a secure authentication system, reducing the complexity of implementing such features from scratch. 14 | 15 | ## Key Features 16 | - **User Registration**: Allows users to sign up with an email and password through Appwrite’s API. 17 | - **User Login**: Enables secure login with persistent sessions, leveraging Appwrite’s session management. 18 | - **Password Reset**: Integrated password reset functionality for enhanced user convenience. 19 | - **Session Management**: Manages user sessions with Appwrite’s session API, ensuring secure access to protected routes. 20 | - **Error Handling and Validation**: Displays helpful messages to users for seamless interaction, with client-side validation and error handling. 21 | 22 | ## Tech Stack 23 | - **Frontend**: React.js, CSS for styling 24 | - **Backend**: Appwrite (BaaS for authentication) 25 | - **API**: Appwrite API for authentication and session management 26 | 27 | ## Features Implemented 28 | - **Registration & Login System**: Users can register, log in, and securely manage sessions using Appwrite. 29 | - **Secure Routing**: Protects routes based on authentication state, ensuring only logged-in users can access specific parts of the application. 30 | - **Persistent Sessions**: Keeps users logged in using Appwrite’s session management. 31 | - **User-Friendly Error Handling**: Provides real-time feedback on login, registration, and other actions. 32 | 33 | ## Project Repo 34 | [Auth using Appwrite GitHub Repository](https://github.com/rajchaudhary99/Auth-using-Appwrite) 35 | -------------------------------------------------------------------------------- /submissions/unique-username-function.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Unique Username Function 2 | 3 | 4 | ## GitHub handles of Team Members 5 | - @soranoo 6 | 7 | ## Project Title 8 | Appwrite-Unique-Username-Function 9 | 10 | ## Project Description 11 | A "Changeable Unique Username" is a common feature in many applications. 📝 12 | 13 | How to make it? Just check the username availability in the database when the username input field is changed, right? 14 | 15 | But, what if there are multiple users checking the same username at the same time? 🤔 All of them will get the same result, which is the username is available. This is because the username is not yet consumed by any user. Then, when they submit the form, the same username is likely to be used by multiple users. 🚨 16 | 17 | 🔑 The key point is, how to make sure the username is unique and able to deal with concurrent checking. 18 | 19 | This function allows you to check if a username is available or not with real-time checking compatibility instead of checking the availability of the username when the user submits the form. 20 | 21 | ## Inspiration behind the Project 22 | I had a REALLY hard time username checking in a project I worked on. It took me a lot of time to figure out how to make it work properly. I thought it would be great to have a function that can be used in any project to check the username availability with concurrent checking compatibility. 🚀 23 | 24 | ## Tech Stack 25 | Nothing but Appwrite and Typescript! 🚀 26 | 27 | ### Usage of Appwrite 28 | - Appwrite Functions 29 | 1. To check the username availability. 30 | 2. To remove related username reservations when the user submits the username to take. 31 | - Appwrite Databases 32 | 1. To store the username reservations. 33 | 34 | 49 | 50 | ## Project Repo 51 | [Appwrite-Unique-Username-Function](https://github.com/soranoo/appwrite-unique-username-function) 52 | 53 | ## Demo Video/Photos/Link 54 | Lets test with different browsers simultaneously. 55 | 56 | [Demo](https://appwrite-unique-username-function.vercel.app/) 57 | 58 | ## Anything Else You Want To Share With Us? 59 | 60 | ### How It Work 61 | ![img](https://github.com/soranoo/appwrite-unique-username-function/blob/main/docs/workflow.svg) -------------------------------------------------------------------------------- /submissions/SnapStudio.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: 2 | 3 | ## GitHub handles of Team Members 4 | _Enter the GitHub handles of all your team members (including yourself) as separate bullet points_ 5 | 6 | - @rajeev033 7 | - @eik-1 8 | 9 | 10 | ## Project Title 11 | 12 | **SnapStudio** 13 | 14 | ## Project Description 15 | 16 | SnapStudio makes it easy for anyone to create custom images of themselves without needing a new photoshoot every time. Just upload a few of your own photos, and SnapStudio’s AI generates new images with different styles, settings, and backgrounds—whether you need a fresh social media profile picture, an updated professional look, or something unique for your personal brand. With SnapStudio, you’re in control of your own photo library, with creative options at your fingertips. 17 | 18 | ## Inspiration behind the Project 19 | _What is the story behind this project? Why did you choose to work on this specific idea?_ 20 | 21 | We were inspired by the work of twitter user and indie hacker @levelsio and his tool photoai, which makes custom photos accessible and fun to create. Seeing how powerful this concept was, we aimed to build a tool that makes it just as easy to create high-quality, creative images but with a focus on user-friendliness and flexibility. SnapStudio empowers anyone to express themselves in new ways. 22 | 23 | ## Tech Stack 24 | 25 | 26 | The technologies we used... 27 | 28 | - **Frontend**: Built with React and styled using Tailwind CSS. 29 | - **Backend Server**: Developed using Node.js and Express, the backend handles requests, manages data processing, and communicates with the AI model for image generation. 30 | -**Appwrite**: We use Appwrite for backend services including user authentication, Database and Storage buckets. 31 | - **Machine Learning**: SnapStudio leverages the **Black Forest lab's latest FLUX 1.1** model for its powerful image generation capabilities, enabling realistic and diverse photo outputs based on user input. 32 | - **Cloud Services**: We chose **Azure** for VM deployment to host and scale our application. 33 | 34 | ## Project Repo 35 | 36 | https://github.com/rajeev033/SnapStudio 37 | 38 | ## Demo Video/Photos 39 | 40 | https://www.loom.com/share/68ad0d1ab8444095a217ee875dc77073?sid=b7fd1602-ad18-42b1-946b-36f4178c7b41 41 | 42 | ## Deployment Link 43 | 44 | You can try this app here- 45 | http://20.244.44.25 46 | -------------------------------------------------------------------------------- /submissions/scrummie-poker.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Scrummie-Poker 2 | 3 | ## GitHub handles of Team Members 4 | 5 | - @pikami 6 | 7 | ## Project Title 8 | 9 | Scrummie-Poker 10 | 11 | ## Project Description 12 | 13 | Scrummie-Poker is a collaborative estimation tool for agile teams, designed to make story point estimation easy and accessible. 14 | 15 | Users can create estimation sessions, invite teammates to join, and collaboratively estimate tickets. Tickets can either be created within the app or imported, and the team can vote on estimates in real time. It’s a modern take on the classic scrum poker approach. 16 | 17 | ## Inspiration behind the Project 18 | 19 | Many existing scrum poker apps are paid, and I wanted to create a free alternative that my team—and others—could use. I was also eager to explore Appwrite and thought this project would be an ideal way to leverage its realtime capabilities while solving a practical problem. 20 | 21 | ## Tech Stack 22 | 23 | The frontend is built with React using Vite, and the following libraries: 24 | 25 | - **yup**: For form validation 26 | - **ckeditor5**: To provide a rich text editor for tickets 27 | - **papaparse**: For parsing CSV files during ticket import 28 | - **showdown**: To convert markdown from imported CSVs into HTML 29 | - **tailwindcss**: For styling the UI 30 | - **tanstack forms**: For form state management 31 | - **tanstack router**: To manage application routes 32 | 33 | The backend is powered by Appwrite 34 | 35 | ### Usage of Appwrite 36 | 37 | - **Auth**: Facilitates user signups and guest accounts management 38 | - **Databases**: Stores all estimation session and ticket-related data 39 | - **Realtime API**: Provides real-time updates during estimation sessions, ensuring smooth interaction during voting and ticket updates 40 | - **Functions**: Manages session invitations and dynamically updates usernames in session data, ensuring user lists are always current 41 | 42 | ## Project Repo 43 | 44 | https://github.com/pikami/scrummie-poker 45 | 46 | ## Demo Video/Photos/Link 47 | 48 | A video demo can be viewed here: 49 | https://youtu.be/jpSDdylpwmk 50 | 51 | The application can also be reached using this link: https://poker.y3.lt 52 | 53 | ## Anything Else You Want To Share With Us? 54 | 55 | Working with Appwrite was an exciting experience, especially since it was my first time using a backend-as-a-service platform. It provided me with all the tools I needed to make Scrummie-Poker come to life, and I thoroughly enjoyed the process. 56 | -------------------------------------------------------------------------------- /submissions/Ahaar.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Ahaar 2 | 3 | ## GitHub Handle of Team Member 4 | 5 | - [@isatyamks](https://github.com/isatyamks) 6 | 7 | 8 | ## Project Title 9 | 10 | **Ahaar** 11 | 12 | ## Project Description 13 | 14 | **Ahaar** is an intelligent food analyzer and nutritional guide designed to help people make healthier food choices in real time. Utilizing advanced AI models, Ahaar recognizes various food items through a camera and provides detailed insights on their nutritional content, health benefits, and potential risks. If a detected food item is deemed unhealthy, Ahaar suggests healthier alternatives, guiding users toward smarter, balanced choices. With its user-friendly interface and focus on daily nutrition tracking, Ahaar empowers users to better understand and improve their dietary habits, promoting a healthier lifestyle. 15 | 16 | ## Inspiration Behind the Project 17 | 18 | The inspiration for Ahaar comes from the urgent need to address the growing issue of diet-related health concerns, particularly in India. Millions face health problems like obesity, diabetes, and heart disease due to poor dietary choices, yet there’s limited technology available to support informed food decisions. Our goal was to create a solution that provides real-time nutritional guidance, enabling users to understand the impact of their food and make healthier lifestyle choices. Ahaar bridges this gap by offering accessible nutritional information that can improve users' long-term health and well-being. 19 | 20 | ## Tech Stack 21 | 22 | - **OpenCV** (`cv2`): For image processing and food recognition. 23 | - **NumPy**: For numerical operations and data handling. 24 | - **Pandas**: For data manipulation and management. 25 | - **Seaborn** and **Matplotlib** (`plt`): For data visualization and performance analysis. 26 | - **TensorFlow**: For building and training AI models. 27 | - **Keras** (`tensorflow.keras`): High-level API for building and training deep learning models. 28 | - **Pillow (PIL)**: For handling image files and formats. 29 | - **Scikit-Image** (`skimage`): For image reading and processing. 30 | - **Flask**: Web framework to handle the backend, API requests, and routing. 31 | - **Flask-Session**: For session management in Flask. 32 | - **Appwrite**: For authentication and user management. 33 | - **Google Generative AI**: For generative AI features. 34 | 35 | ## Project Repo 36 | 37 | [https://github.com/isatyamks/Ahaar](https://github.com/isatyamks/Ahaar) 38 | 39 | ## Demo Video/Photos 40 | 41 | [Watch the Demo Video](https://youtu.be/ye6rU7BnZT4) 42 | -------------------------------------------------------------------------------- /submissions/Suraksha.md: -------------------------------------------------------------------------------- 1 | # Suraksha 2 | 3 | Suraksha is a comprehensive personal safety app, empowering users with quick-access tools to stay safe in various situations. Its user-friendly design and powerful features ensure that user safety is the top priority. 4 | 5 | ## Inspiration Behind Suraksha 6 | 7 | In a world where safety is paramount, having quick and reliable access to emergency tools is crucial. Suraksha was developed to provide peace of mind, allowing users to feel more secure knowing they have a safety app designed to respond effectively in emergencies. 8 | 9 | ## Key Features 10 | 11 | - **Emergency Contacts**: Easily set up trusted contacts for quick communication during emergencies. 12 | - **SOS Shake-to-Alert**: Activate the SOS feature by shaking your phone, instantly notifying your emergency contacts with your location. 13 | - **Fake Siren**: Deter potential threats by triggering a loud, startling siren. 14 | - **Emergency Helplines**: Access essential emergency numbers, such as helplines for police, ambulance, fire brigade, and more. 15 | - **Continuous Safety Mode**: Background monitoring to detect unusual activity and automatically alert contacts in suspicious situations. 16 | 17 | ## Tech Stack 18 | 19 | - **Languages**: Java, Kotlin 20 | - **Local Database**: Room Database, SQL 21 | - **Backend**: Appwrite (for authentication and secure data storage) 22 | 23 | ## Technologies in Detail 24 | 25 | - **Kotlin**: Robust and reliable, Kotlin powers the app's core functionality, ensuring smooth performance across Android devices. 26 | - **Room Database**: Provides local data storage for emergency contacts, enabling reliable offline access. 27 | - **SQL**: Manages data efficiently, ensuring accurate information handling. 28 | - **Appwrite**: Secures user data and manages authentication for a seamless, secure experience. 29 | 30 | ## Real-Life Impact 31 | 32 | Suraksha has received positive feedback for enhancing users' sense of security. Real-life testimonials highlight the app's effectiveness in emergency situations, reinforcing its role as a trusted companion for personal safety. 33 | 34 | ## GitHub Handles of Team Members 35 | 36 | - **Ritvija Pachori** @ritvijapachori - Android Developer 37 | - **Ayush Deshmukh** @Deshmukh-Ayush - Web & App Developer 38 | - **Pragya Hurmade** @Pragyaa3 - Web Developer 39 | - **Satyam Sharma** @satyamsharma17 - Android Developer 40 | 41 | ## Repository 42 | 43 | Access the repository here: [Suraksha on GitHub](https://github.com/ritvijapachori/Suraksha) 44 | 45 | ## Project Link 46 | 47 | Download the project from here: https://drive.google.com/file/d/1hlZ3haAn4kvYgZ9TAgm1lvDkKxAwO6EF/view?usp=sharing 48 | -------------------------------------------------------------------------------- /submissions/MedConnect.md: -------------------------------------------------------------------------------- 1 | **Hackathon Submission: MedConnect - Blockchain-Powered Healthcare Accessibility** 2 | 3 | **GitHub handles of Team Members** 4 | @Amarnath-Rao 5 | 6 | --- 7 | 8 | ### Project Title 9 | **MedConnect - Blockchain-Powered Healthcare Accessibility** 10 | 11 | ### Project Description 12 | MedConnect is a blockchain-driven platform designed to make quality healthcare accessible, especially to underprivileged communities. It combines the power of Web3 for secure crowdfunding, Appwrite for backend services, and AI for diagnostic assistance. MedConnect allows users to access a secure crowdfunding platform for verified medical needs, file healthcare grievances, and explore virtual hospital tours through immersive AR/VR. The platform also integrates AI-powered health risk analysis, making it a comprehensive solution for healthcare accessibility. 13 | 14 | ### Inspiration behind the Project 15 | Millions of people lack access to essential healthcare services due to high costs and insufficient resources. MedConnect was created to bridge this gap, leveraging blockchain for secure financial support, Appwrite for a smooth user experience, and AI to assist in health diagnostics. The goal is to create an intuitive, user-friendly platform for those in need of affordable healthcare options. 16 | 17 | --- 18 | 19 | ### Tech Stack 20 | - **Frontend**: Next.js 21 | - **Interactive Components**: Appwrite for seamless user interaction and security 22 | - **Blockchain**: Solidity, Web3 for crowdfunding 23 | - **Database**: Appwrite Databases for efficient and secure data handling 24 | - **AI**: Gemini AI for health risk assessment 25 | - **AR/VR**: Immersive technologies for virtual hospital tours 26 | 27 | --- 28 | 29 | ### Usage of Appwrite 30 | - **Appwrite Authentication**: Manages user sign-ups, logins, and session maintenance. 31 | - **Appwrite Databases**: Stores user profiles, healthcare grievances, and project data for secure and organized access. 32 | - **Appwrite Storage**: Securely stores profile pictures and healthcare-related documents, ensuring privacy and easy retrieval. 33 | 34 | --- 35 | 36 | ### Project Repo 37 | GitHub Repository: [MedConnect](https://github.com/Amarnath-Rao/MedConnect) 38 | 39 | ### Demo Video Link 40 | [Watch the Demo Video](https://youtu.be/XjWS-9WEWfM) 41 | 42 | --- 43 | 44 | ### Anything Else You Want to Share With Us? 45 | MedConnect is designed to serve as both an individual resource and a collaborative platform for healthcare access and support. The integration of a discussion feature enables users to connect, share advice, and support each other in navigating healthcare challenges. The project aims to be a valuable resource for communities in need, providing both financial and informational support. 46 | -------------------------------------------------------------------------------- /submissions/eventManagement.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: **Event Management** 2 | 3 | ## GitHub handles of Team Members 4 | - [@asmitRai](https://github.com/asmit27rai) 5 | 6 | ## Project Title 7 | **Event Management** 8 | 9 | ## Project Description 10 | The Event Management App is a robust platform built to streamline the process of managing events. It allows admins to add, update, and delete events, review and manage user requests for event participation, and respond to user inquiries. For users, the app offers a seamless experience to explore upcoming events, request to join them, and contact the admin for further details. This app is designed with both usability and scalability in mind, leveraging Appwrite for backend services and React for an interactive user interface. 11 | 12 | ## Inspiration behind the Project 13 | The inspiration for this project came from the need to simplify event management for both organizers and participants. Whether for school events, community gatherings, or company activities, a centralized system for event management allows admins to handle all aspects in one place. By integrating communication and request handling features, the app not only simplifies organization but also fosters a community-oriented space where users can connect with event organizers directly. 14 | 15 | ## Tech Stack 16 | The project is built using: 17 | 18 | - **React** for frontend development and creating dynamic UI components 19 | - **Tailwind CSS** for styling the application and ensuring a modern, responsive design 20 | - **Appwrite** for backend services like authentication, file storage, database and messaging function. 21 | 22 | ### Usage of Appwrite 23 | - **Appwrite Authentication**: I used Appwrite Auth to manage user authentication, including sign-ups, log-ins and maintaining user sessions. 24 | - **Appwrite Databases**: I used Appwrite databases to store user accounts, manage event and manage requests. 25 | - **Appwrite Storage**: Appwrite storage is used for securely storing event image. 26 | 27 | ## Project Repo 28 | GitHub Repository: Event Management 29 | [Explorer](https://github.com/asmit27rai/event-management) 30 | 31 | ## Demo Video/Photos/Link 32 | - Demo Video: [Link to Video](https://drive.google.com/file/d/1agR2T0oOTFoZVObL_xp6unfzRmZotYat/view?usp=drive_link) 33 | 34 | ## Anything Else You Want To Share With Us? 35 | The Event Management App is designed not only as a tool for event organization but also as a community platform. By including features for user communication and request management, it simplifies event participation and encourages interaction between admins and users. The use of Appwrite services makes it a secure and scalable application that can adapt to a variety of event types and user needs. -------------------------------------------------------------------------------- /submissions/decide-yesno-app.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: DecideYesNoApp - Log your decisions 2 | 3 | ## GitHub handles of Team Members 4 | - [@viennarzc](http://github.com/viennarzc) 5 | 6 | ## Project Title 7 | DecideYesNo App 8 | 9 | ## Project Description 10 | an iOS application that helps users make and track binary (yes/no) decisions. The app provides a simple interface for recording decisions while maintaining a comprehensive history of each choice made. Key features include: 11 | 12 | - Simple Yes/No decision interface 13 | - Detailed decision logging with timestamps 14 | - Historical tracking of changed decisions 15 | - User authentication 16 | - Cloud sync using AppWrite backend 17 | - Cross-platform capability (initially for iOS, with planned web and Android) 18 | 19 | The app helps users maintain accountability and track patterns in their decision-making process over time, while keeping the interface clean and focused on the core yes/no choice mechanism. 20 | 21 | ## Inspiration behind the Project 22 | _What is the story behind this project? Why did you choose to work on this specific idea?_ 23 | 24 | ## Tech Stack 25 | The project is built using a modern, scalable architecture: 26 | 27 | **Client Side:** 28 | 29 | - Swift UI for iOS native app development 30 | 31 | **Backend (AppWrite):** 32 | 33 | - **Authentication**: Sign-ups, Logins, Sessions. 34 | - **Database**: Storing Decisions, and DecisionHistory 35 | 36 | ## Project Repo 37 | 38 | 39 | - https://github.com/viennarzc/DecideYesNoApp 40 | 41 | 42 | ## Demo Video/Photos 43 | ### Video 44 | - [Youtube - App Demo](https://youtu.be/Yz_aoC_mx10) 45 | 46 | ### Photos 47 | 48 | ![RocketSim_Screenshot_iPhone_15_Pro_Max_6 7_2024-10-31_10 36 04 Medium](https://github.com/user-attachments/assets/05b19c60-4516-4ee7-9e42-96112afd0d41) 49 | ![RocketSim_Screenshot_iPhone_15_Pro_Max_6 7_2024-10-31_10 36 45 Medium](https://github.com/user-attachments/assets/e35a2d40-0c53-4f01-9e55-5a1d6efc5544) 50 | ![RocketSim_Screenshot_iPhone_15_Pro_Max_6 7_2024-10-31_10 36 36 Medium](https://github.com/user-attachments/assets/24f4d836-6b8a-439f-aea8-733f6741c894) 51 | ![RocketSim_Screenshot_iPhone_15_Pro_Max_6 7_2024-10-31_10 36 29 Medium](https://github.com/user-attachments/assets/5ed38644-70f3-4b7a-9382-63d215477711) 52 | ![RocketSim_Screenshot_iPhone_15_Pro_Max_6 7_2024-10-31_10 36 24 Medium](https://github.com/user-attachments/assets/efc61777-4eac-4a7d-9127-266d9f2d6869) 53 | ![RocketSim_Screenshot_iPhone_15_Pro_Max_6 7_2024-10-31_10 36 16 Medium](https://github.com/user-attachments/assets/47db2699-f13d-49b2-883c-a007696b1ff2) 54 | ![RocketSim_Screenshot_iPhone_15_Pro_Max_6 7_2024-10-31_10 36 09 Medium](https://github.com/user-attachments/assets/02d6a538-82fc-4034-a895-8c7a6522a943) 55 | -------------------------------------------------------------------------------- /submissions/invicollab.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Invicollab 2 | 3 | ## GitHub handles of Team Members 4 | _Enter the GitHub handles of all your team members (including yourself) as separate bullet points_ 5 | 6 | @Droovian 7 | @Introvert2000 8 | @gadekar123 9 | 10 | ## Project Title 11 | _What is the name of your project?_ 12 | 13 | Invicollab 14 | 15 | ## Project Description 16 | _What have you built during the hackathon?_ 17 | 18 | Our platform transforms the traditional invitation & wishes experience by enabling users to create interactive, 19 | personalized video-based wishes as well as animated invitations. You can form groups and create a custom video for a friend on their birthday. 20 | Apart from this you can create & share invites to your friends/family for any occasion you are looking to celebrate just by selecting 21 | what you'd like and copying the link to the experience we provide for you. 22 | 23 | ## Inspiration behind the Project 24 | _What is the story behind this project? Why did you choose to work on this specific idea?_ 25 | 26 | The heart of InviCollab is about making it easy to gather loved ones for life’s meaningful moments. 27 | The platform itself can feel like a “virtual gathering space” where users come together, creating the warmth of shared memories, 28 | especially with the collaborative video feature. Invitations as well are often boring & don't provide any real experience, we wanted to change that. 29 | 30 | ## Tech Stack 31 | _How have you built this project? Mention the technologies/methods/platforms you used to build your project_ 32 | 33 | NextJS, Framer Motion, Clerk, Appwrite, ShadCN, AcertinityUI 34 | 35 | ## Usage of Appwrite 36 | 37 | Appwrite Databases: Store user, video, space, invitation data 38 | Appwrite Storage Buckets: Store user uploaded videos 39 | 40 | ## Project Repo 41 | _Share a public repo link of your project_ 42 | 43 | https://github.com/Droovian/wishly-digitalwishes 44 | 45 | ## Demo Video/Photos 46 | _Share a 2-3 minute demo video of your project_ 47 | ![hom![create-invitation](https://github.com/user-attachments/assets/e525c2be-ebfa-466e-a518-985bc9ea2625) 48 | e-screen](https://github.com/user-attachments/assets/8bd4dff0-0d56-44c8-a667-84b0f21e2323) 49 | ![videowish](https://github.com/user-attachments/assets/ec4d2616-739d-4d89-8685-541192013624) 50 | 51 | https://youtu.be/LrUdSqslSuk 52 | 53 | ## Anything else you want to share with us 54 | We look to get this to multiple users in the near future. Expand with multiple templates wherein people can also share their own creations. 55 | Monetize the platform as well (ideally for the videos feature). Lastly for the Invitations we are going to let people customize it more to 56 | their preference & be a part of how the end result will look like. 57 | -------------------------------------------------------------------------------- /submissions/React-Appwrite-RealTime-Chat.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Real-Time Chat App 2 | 3 | ## GitHub handles of Team Members 4 | - @akshayram1 5 | 6 | ## Project Title 7 | **Real-Time Chat App** 8 | 9 | ## Project Description 10 | During the hackathon, we built a **Real-Time Chat Application** using **React JS** and **Appwrite**. The app allows users to register, log in, and chat in real-time. It features an intuitive interface for easy communication, with messages updating instantly across all active users. The backend infrastructure is powered by **Appwrite**, handling authentication, database management, and real-time functionality. 11 | 12 | ## Inspiration behind the Project 13 | The motivation behind this project was to create a fast and reliable communication platform. Real-time communication has become essential in today’s digital world, and we wanted to explore the power of Appwrite to build an efficient chat app. This project was driven by the desire to simplify real-time messaging, making it more accessible and scalable. 14 | 15 | ## Tech Stack 16 | - **React JS**: Used for building the frontend UI. 17 | - **Appwrite**: A complete backend platform that managed user authentication, real-time messaging, and database operations. 18 | - **Appwrite Real-Time API**: Implemented for real-time message synchronization. 19 | - **Appwrite Databases**: For storing user details and chat messages. 20 | - **Appwrite Authentication**: To manage user sessions, registration, and login functionality. 21 | 22 | ### Usage of Appwrite 23 | - **Appwrite Authentication**: 24 | Implemented for handling user sign-ups, logins, and session management securely. 25 | 26 | - **Appwrite Databases**: 27 | Used to create and store chat messages in the `messages` collection, including attributes such as `user_id`, `username`, and `message body`. 28 | 29 | - **Appwrite Real-Time API**: 30 | Utilized to ensure that messages are updated in real time across all connected users as soon as a new message is added to the database. 31 | 32 | ## Project Repo 33 | https://github.com/akshayram1/React-Appwrite-RealTime-Chat 34 | ## Demo Video/Photos/Link 35 | Demo Video: [https://youtu.be/17s7UFNR7QM] 36 | 37 | Screenshots: 38 | 1. ![https://drive.google.com/file/d/1-q2NL74dPhkYsZxhx3NuMI5awqKkM2-3/view?usp=sharing] 39 | 2. ![https://drive.google.com/file/d/1rMEyvuO0snTp-NnYB77JidC2AxR8XgP6/view?usp=sharing] 40 | 3. ![https://drive.google.com/file/d/166Yv-ke9StA6QAdwNs3aXGZ-6nHlSQ21/view?usp=sharing] 41 | 42 | 43 | This project was an exciting and enriching experience! Using Appwrite to handle real-time features and authentication made the development process much smoother, and we were able to focus more on creating a seamless user experience. We're proud of what we built and eager to see how it can evolve. 44 | -------------------------------------------------------------------------------- /submissions/event_planner.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Event Planner 2 | 3 | ## GitHub handles of Team Members 4 | - [@Avradeep](https://github.com/Zedoman) 5 | 6 | ## Project Title 7 | Event Planner 8 | 9 | ## Project Description 10 | Event Planner is a web application that allows users to create, manage, and delete events efficiently. It features a user-friendly interface where users can input event details such as the title, description, date, time, location, category, and priority. Events are displayed in a card-based format for easy interaction and management. The project integrates CopilotKit for enhanced productivity through AI-powered suggestions and automation. For secure data handling, it uses Appwrite's backend services. More importantly here users can shere the event details on any social media. 11 | 12 | ## Inspiration behind the Project 13 | The inspiration behind **Event Planner** was the need for a simple yet powerful tool to help users organize events efficiently. Many event management tools are either too complex or lack essential features. This project aims to provide an intuitive experience for both tech-savvy and casual users while leveraging modern AI tools to make the experience more interactive. 14 | 15 | ## Tech Stack 16 | - **React**: For building the frontend. 17 | - **Next.js**: For server-side rendering and handling APIs. 18 | - **TailwindCSS**: To style the user interface. 19 | - **Shadcn-UI**: To ensure consistency in UI components. 20 | - **CopilotKit**: To enable AI-powered suggestions and automation for tasks like event creation. 21 | - **TypeScript**: For type safety and better developer experience. 22 | - **Appwrite**: As a backend service for secure data management, including databases and authentication. 23 | 24 | ### Usage of Appwrite 25 | - **Appwrite Databases**: I used Appwrite Databases to store event details such as title, description, date, time, location, category, and priority. 26 | - **Appwrite Authentication**: Appwrite Authentication was implemented to ensure the create, update, or delete events. 27 | - **Appwrite Storage**: Event images or related media could be stored using Appwrite Storage for future feature expansions. 28 | 29 | ## Project Repo 30 | [Event Planner GitHub Repo](https://github.com/Zedoman/AppWrite_Event_Planner) 31 | 32 | ## Demo Video/Photos/Link 33 | Check out a demo of the project here: 34 | 35 | 36 | https://github.com/user-attachments/assets/5e872039-63c0-49b0-9d1c-1d83c9a80b93 37 | 38 | 39 | 40 | 41 | ## Anything Else You Want To Share With Us? 42 | This project is built with scalability in mind, offering a clean interface with the potential to integrate more advanced features like calendar synchronization and notifications. We plan to continue iterating on this project by adding more event management tools and expanding the use of AI to make it even smarter. 43 | -------------------------------------------------------------------------------- /submissions/PlantHead.md: -------------------------------------------------------------------------------- 1 | 2 | # Hackathon Submission: **PlantHead - Your Social Plant Paradise** 3 | 4 | ## GitHub handles of Team Members 5 | - [@patel-aum](https://github.com/patel-aum) 6 | 7 | ## Project Title 8 | **PlantHead - Your Social Plant Paradise** 9 | 10 | ## Project Description 11 | PlantHead is a vibrant community platform where plant enthusiasts can share their green journeys and inspire others. Similar to Snapchat's streak feature, users can maintain their "plant streaks" by regularly sharing updates about their botanical companions. The app sends smart notifications for watering schedules based on each plant's specific needs. With location-based posts, users can discover what's growing in their neighborhood and connect with local plant parents. Whether you're a seasoned gardener or just starting your plant journey to plant mom, PlantHead helps you nurture your green family while being part of a thriving community. 12 | 13 | ## Inspiration behind the Project 14 | I was inspired by my mom who once spotted a plant and told me about its medicinal properties for treating bruises. I realized I don't really know much about the plants growing in my neighborhood! Also, since I have different plants in my garden and balcony, I often forget whether I've watered them or not. These simple problems got me thinking - why not create something that could help solve these everyday plant parent struggles? 15 | 16 | ## Tech Stack 17 | The project is built using: 18 | - Vite React for crafting smooth, responsive user interfaces 19 | - Tailwind CSS for elegant, modern styling 20 | - Appwrite as a Backend-as-a-Service (BaaS) powering authentication, database management, and notification systems 21 | 22 | ### Usage of Appwrite 23 | - Appwrite Authentication: Implements secure user authentication, handling sign-ups, log-ins, and session management using JWT 24 | - Appwrite Databases: Manages structured storage for post information and user plant data 25 | - Appwrite Storage: Handles secure storage and retrieval of plant images and user-generated content 26 | - Appwrtite Functions: Manages an trefleAPI and gives to the app respecting CORS policy 27 | 28 | ## Project Repo 29 | [GitHub Repository: Plant-head](https://github.com/patel-aum/planthead) 30 | 31 | ## Demo Video/Photos/Link 32 | - Live Demo: [Vercel Deployment](https://plant-head.vercel.app/) 33 | - Demo Video: [Video URL](https://drive.google.com/file/d/1jrTd-_9qqoUX2ELj_LHl4RXPMXEIsMB5/view?usp=sharing) 34 | 35 | 36 | https://github.com/user-attachments/assets/6ccfbc5b-7120-499a-993d-fad69698fa5a 37 | 38 | 39 | ## Anything Else You Want To Share With Us? 40 | Working with Appwrite was mostly great - loved the quick setup and real-time database features! Though there were some learning curves with queries, overall it proved to be the perfect choice for PlantHead. Looking forward to building more features with it! 41 | -------------------------------------------------------------------------------- /submissions/algomorph.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: **Algomorph - DSA Algorithm Explorer** 2 | 3 | ## GitHub handles of Team Members 4 | - [@shashankaz](https://github.com/shashankaz) 5 | 6 | ## Project Title 7 | **Algomorph - DSA Algorithm Explorer** 8 | 9 | ## Project Description 10 | The project I built during the hackathon is **Algomorph**, a comprehensive platform that allows users to explore, learn, and implement popular Data Structures and Algorithms (DSA) in multiple programming languages, including Python, Java, C++, and JavaScript. The platform provides an interactive playground for running algorithms, dynamic visualizations to make learning easier, and a discussions tab where users can collaborate, upvote, downvote, and comment on algorithmic problems and ideas. 11 | 12 | ## Inspiration behind the Project 13 | The reason I chose this project was to create a one-stop solution for anyone looking to understand algorithms better, whether they're students preparing for coding interviews or professionals brushing up their DSA knowledge. I wanted to include multiple languages, interactive code editing, and visual learning elements to make the learning process more engaging and intuitive. The discussion feature encourages collaboration, allowing users to discuss ideas and improve together. 14 | 15 | ## Tech Stack 16 | The project is built using: 17 | 18 | - **Next.js** for the frontend and backend 19 | - **Monaco Editor** for the interactive code playground 20 | - **Tailwind CSS** for styling the application 21 | - **Appwrite** for backend services like authentication and file storage 22 | - **Prisma** and **PostgreSQL (NeonDB)** for managing and storing data related to the discussions tab, including comments, upvotes, and downvotes 23 | - **React** for building dynamic user interfaces 24 | 25 | ### Usage of Appwrite 26 | - **Appwrite Authentication**: I used Appwrite Auth to manage user authentication, including sign-ups, log-ins, google signin and maintaining user sessions. 27 | - **Appwrite Databases**: I used Appwrite databases to store user accounts, manage code descriptions, and save the algorithms written in multiple languages. 28 | - **Appwrite Storage**: Appwrite storage is used for securely storing user profile pictures. 29 | 30 | ## Project Repo 31 | GitHub Repository: Algomorph - DSA Algorithm Explorer](https://github.com/shashankaz/algomorph) 32 | 33 | ## Demo Video/Photos/Link 34 | - Deployed Url: [Link to Website](https://algomorph.vercel.app/) 35 | 36 | ## Anything Else You Want To Share With Us? 37 | Algomorph is designed not only for individual learners but also as a collaborative platform, making it a unique place for people to discuss, vote on, and improve their algorithmic understanding. The discussion feature allows users to exchange ideas, making this project more community-focused and a helpful resource for coding interview preparation and beyond. 38 | -------------------------------------------------------------------------------- /submissions/Jatin_Blog.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Jatin_Blog : A Creative Site to read and write blogs 2 | 3 | 4 | ## GitHub handles of Team Members 5 | 6 | - @coddingjatin 7 | 8 | ## Project Title 9 | Jatin_Blog : Creative Blogs 10 | 11 | ## Project Description 12 | -Jatin_blog is a responsive blogging platform where users can create, manage, and comment on posts. Built using React for the frontend, Node.js with MongoDB for the backend, and Appwrite for backend services, it features JWT-based authentication, post categorization, and a search function for easy navigation. 13 | 14 | ## Inspiration behind the Project 15 | 16 | -The inspiration behind Jatin_blog came from the need for a streamlined, user-friendly platform where people can express their thoughts without the clutter of many modern blogging sites. I wanted to build something that focused on simplicity, functionality, and secure interaction—allowing users to easily write and categorize posts while also engaging with others through comments. 17 | 18 | -The use of Appwrite and technologies like React, Node.js, and MongoDB stemmed from my desire to explore modern web development tools that can create scalable, full-stack applications. This project served as a way to challenge myself, expand my development skills, and deliver a practical solution for online content creation and management. 19 | 20 | ## 🛠️ Tech Stack 21 | Frontend: React 22 | Backend: Node.js, Express 23 | Database: MongoDB 24 | Authentication: JWT 25 | Appwrite: Used for managing user authentication, database interactions, and other backend services 26 | 27 | ### Usage of Appwrite 28 | -Appwrite: Central to the project, Appwrite handles secure user authentication, allowing for seamless user login and registration. It also manages databases and server-side interactions like file storage, while providing easy integration with the existing Node.js backend. 29 | 30 | ## Project Repo 31 | -https://github.com/coddingjatin/Blog_Web 32 | 33 | ## Demo Video/Photos/Link 34 | -Demo Video Link : (https://drive.google.com/file/d/1h6cgh__6Vjg9bBp9vJRW3-nIQ3Gasoue/view?usp=sharing) 35 | 36 | ## Photos : 37 | https://drive.google.com/file/d/1Zjf5XMmQrRiDYzbFjfYH5PIzl3flEHM0/view?usp=sharing 38 | https://drive.google.com/file/d/1d1TT0h0Wf2D9eokNS3AGnA0g5l6yna19/view?usp=sharing 39 | https://drive.google.com/file/d/16pKqYion-bdTOFCgbHMP9YMGS_ODem4v/view?usp=sharing 40 | 41 | ## Anything Else You Want To Share With Us? 42 | -One key highlight of Jatin_blog is the integration of Appwrite for backend services. It significantly enhances the user experience by providing robust user authentication and database management, simplifying complex tasks like user registration, login, and secure session handling. 43 | 44 | -Additionally, the project serves as a practical learning ground, allowing me to experiment with a modern tech stack, including React, Node.js, MongoDB, and Appwrite. The goal is to create a seamless, user-friendly platform for blog creation and interaction while exploring advanced web development concepts. 45 | -------------------------------------------------------------------------------- /submissions/MoodJournal.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: MoodJournal 2 | 3 | ## GitHub handles of Team Members 4 | _Enter the GitHub handles of all your team members (including yourself) as separate bullet points_ 5 | 6 | - @shloksri 7 | 8 | ## Project Title 9 | _What is the name of your project?_ 10 | 11 | MoodJournal 12 | 13 | ## Project Description 14 | _What have you built during the hackathon?_ 15 | 16 | 17 | The project I created is a Mood Journal app which has 2 basic functionalities - Adding daily moods of the user, & adding journals created by the user. 18 | 19 | The user can log in using their Google account and write down however they are feeling on that day. The app records the date and time of their entries and the user has access to their previous records. 20 | 21 | 22 | ## Inspiration behind the Project 23 | _What is the story behind this project? Why did you choose to work on this specific idea?_ 24 | 25 | The inspiration comes from a personal journey towards understanding mental health. In our fast-paced world, many struggle to articulate their feelings. I wanted to create a simple tool for self-reflection that allows users to log daily moods and write journals about their experiences. This practice fosters awareness and helps identify emotional patterns. Participating in the Appwrite hackathon was a great opportunity to utilize their services, ensuring the app is functional and secure while supporting personal growth and well-being. 26 | 27 | ## Tech Stack 28 | _How have you built this project? Mention the technologies/methods/platforms you used to build your project_ 29 | 30 | This is a Full stack web application. Here is the link - https://health-app-appwrite.vercel.app/ 31 | 32 | - React for designing the frontend 33 | - Pink Design by Appwrite for styling 34 | - Google for OAuth provider 35 | - Mailgun - configured custom domain mg.shloksri.com to send emails to any user 36 | - Amazon Route53 for configuring the DNS records 37 | - Vercel for deployment to Production 38 | 39 | All Appwrite services used : 40 | - __Pink Design by Appwrite__ - The website is designed using the pink-design by appwrite. Most of the css classes used are the default ones present in the design. All components 41 | - __Auth__ - For allowing users to automatically sign-up/log-in using their Google account. Currently, my project supports only Google as the OAuth2 Provider 42 | - __Databases__ - To store the moods/journals entered by the user. When the user logs in, they will be able to see their previous entered journals and view their details. 43 | - __Functions__ for updating databases and trigger emails on the event of new user registration, thus utilising __Messaging__ feature as well. 44 | - __Messaging__ - To send emails to the user when they register for the first time. 45 | 46 | 47 | ## Project Repo 48 | _Share a public repo link of your project_ 49 | 50 | https://github.com/shloksri/health-app-appwrite 51 | 52 | ## Demo Video/Photos 53 | _Share a 2-3 minute demo video of your project_ 54 | 55 | https://youtu.be/lys5smBx78s 56 | -------------------------------------------------------------------------------- /submissions/wp-appwrite-login.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: wp-appwrite-login 2 | 3 | ## GitHub handles of Team Members 4 | - kartikmehta8 5 | 6 | ## Project Title 7 | wp-appwrite-login 8 | 9 | ## Project Description 10 | The Appwrite Login Plugin is a WordPress plugin that integrates Appwrite authentication with the WordPress login form. It allows users to log in using their Appwrite credentials and manage login settings through the WordPress admin interface. 11 | 12 | ### Features 13 | 14 | - Adds a **"Use Appwrite Credentials"** button to the WordPress login form. 15 | - Integrates with Appwrite user authentication, allowing users to log in via Appwrite. 16 | - Automatically creates WordPress accounts for Appwrite users if they don't already exist. 17 | - Disables the WordPress **"Send password reset"** link for Appwrite users, as password management is handled via Appwrite. 18 | - Admin settings page for configuring Appwrite credentials (API Key, Project ID, and Endpoint). 19 | - Option to enable or disable the **"Use Appwrite Credentials"** button based on settings. 20 | 21 | ## Inspiration behind the Project 22 | The idea behind this project came from the need to integrate modern authentication systems like Appwrite with WordPress. By providing a seamless login experience, this plugin allows developers and site owners to leverage Appwrite's secure authentication while maintaining WordPress's flexibility, enhancing user management and security capabilities. (Appwrite SSO POC) 23 | 24 | ## Tech Stack 25 | - **WordPress** – The core platform for plugin development. 26 | - **PHP** – The primary programming language for WordPress plugin development. 27 | - **Appwrite Auth** – A secure authentication platform integrated with WordPress login. 28 | - **Appwrite** PHP SDK – Used to communicate with the Appwrite API. 29 | - **Composer** – Dependency manager for PHP, used to install the Appwrite SDK. 30 | - **HTML** – For creating the login form and admin settings page structure. 31 | - **CSS** – For styling the login button and admin interface. 32 | - **JavaScript** – Used to toggle between Appwrite and WordPress login modes. 33 | - **MySQL** – The database behind WordPress, used to store user data and settings. 34 | - **GitHub** – Version control for project collaboration. 35 | 36 | ### Usage of Appwrite 37 | - **Appwrite Authentication:** Used to authenticate users via Appwrite credentials and manage login sessions securely. 38 | - **Appwrite PHP SDK:** Facilitates communication with the Appwrite API, enabling secure and efficient user authentication and session management. 39 | 40 | ## Project Repo 41 | https://github.com/kartikmehta8/wp-appwrite-login 42 | 43 | ## Demo Video/Photos/Link 44 | https://youtu.be/YrQfdEbknW8 45 | 46 | ## Anything Else You Want To Share With Us? 47 | This project is an open-source initiative aimed at enhancing WordPress's authentication by integrating modern systems like Appwrite. It’s built with flexibility in mind, adhering to all WordPress coding standards, allowing developers to easily configure Appwrite alongside WordPress’s native login system. 48 | -------------------------------------------------------------------------------- /submissions/moodsync.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: MoodSync - AI-Curated Music Recommendation App 2 | 3 | ## GitHub Handles of Team Members 4 | - **@adityaoberai**: Focused on frontend development and user interface design. 5 | - **@tessamero**: Responsible for backend integration and API setup. 6 | 7 | ## Project Title 8 | **MoodSync - AI-Powered Music Recommendation App** 9 | 10 | ## Project Description 11 | MoodSync is an innovative music recommendation application that curates playlists based on the user’s mood. Using machine learning algorithms, MoodSync analyzes user mood inputs to deliver personalized music recommendations tailored for various emotional states. Whether the goal is to enhance productivity, relax, or energize, MoodSync offers a unique, mood-specific listening experience. Built with Flutter, the app is fully compatible across Android and iOS platforms, ensuring accessibility and a consistent user experience. 12 | 13 | ## Inspiration Behind the Project 14 | The idea behind MoodSync was inspired by the impact music has on emotional well-being. In various situations, music serves as an effective means to manage or enhance one’s mood. MoodSync leverages this connection, providing users with music tailored to their emotional state, with the aim of improving their mental wellness and mood alignment through personalized music recommendations. 15 | 16 | ## Tech Stack 17 | - **Flutter**: Framework for building the app’s responsive, cross-platform user interface. 18 | - **Dart**: Primary programming language used for the application. 19 | - **Appwrite**: Provides backend functionalities for data storage, user authentication, and API management. 20 | - **Google Generative AI**: Powers the recommendation engine for mood-based music selection. 21 | - **Flutter Packages**: Key packages include `appwrite` for backend connectivity, `flutter_svg` for vector graphics, and `google_generative_ai` for mood-based recommendations. 22 | 23 | ## Project Repo 24 | The codebase for MoodSync can be found on GitHub: [MoodSync Repository](https://github.com/kathikcr/MoodSync.git) 25 | 26 | ## Demo Video/Photos 27 | A visual demonstration of MoodSync’s features and functionalities can be accessed via the GitHub repository: [MoodSync GitHub](https://github.com/kathikcr/MoodSync.git) 28 | 29 | --- 30 | 31 | # Installation Guide 32 | 33 | ## Prerequisites 34 | To set up MoodSync locally, ensure the following prerequisites are in place: 35 | 36 | 1. **Flutter SDK (Version 3.5.2 or later)**: 37 | - Follow the Flutter [installation guide](https://flutter.dev/docs/get-started/install) for setup instructions. 38 | - Add Flutter to your system’s PATH to facilitate running Flutter commands from the terminal. 39 | 40 | 2. **Dart SDK**: 41 | - Included with Flutter SDK 3.5.2, so no separate installation is required. 42 | 43 | 3. **Appwrite Server (Optional)**: 44 | - For users who wish to implement backend features, an Appwrite server can be configured. Set up and add relevant Appwrite credentials within the `.env` file (outlined below). 45 | 46 | ## Steps to Install and Run MoodSync 47 | 48 | ### 1. Clone the Repository 49 | To obtain a local copy of the project, clone the GitHub repository: 50 | ```bash 51 | git clone https://github.com/kathikcr/MoodSync.git 52 | cd MoodSync 53 | ` 54 | -------------------------------------------------------------------------------- /submissions/FashionSathi.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: FashionSathi 2 | ## GitHub handles of Team Members 3 | _Enter the GitHub handles of all your team members (including yourself) as separate bullet points_ 4 | 5 | 6 | @SavantCode 7 | 8 | @nagvanshi9275 9 | 10 | @bhavya123gupta 11 | 12 | @RishiAnand108 13 | 14 | ## Project Title 15 | _What is the name of your project?_ 16 | 17 | FashionSathi 18 | 19 | ## Project Description 20 | _What have you built during the hackathon?_ 21 | 22 | Overview: 23 | FashionSathi is a cutting-edge application that harnesses the power of AI to help users effortlessly decide what to wear. By allowing users to upload images of their entire wardrobe—including clothing items and accessories such as watches, belts, bracelets and suitsour app generates personalized outfit suggestions. 24 | 25 | Purpose: 26 | In today's fast-paced world, choosing the right outfit can be time-consuming and stressful. Our application simplifies this process, saving users valuable time and mental energy by providing tailored outfit combinations that align with their unique style and preferences. 27 | 28 | How It Works: 29 | 30 | User-Friendly Upload: Users upload images of their clothing and accessories just once. 31 | AI-Powered Suggestions: Our advanced AI algorithm analyzes the uploaded items and suggests the best combinations for any given day, taking into account factors such as color coordination, occasion, and personal style. 32 | With HackAppWrite 2024, users can streamline their daily routine, make confident style choices, and step out looking their best. 33 | 34 | ## Inspiration behind the Project 35 | _What is the story behind this project? Why did you choose to work on this specific idea?_ 36 | 37 | FashionSathi was inspired by my own struggles with choosing outfits amidst a busy lifestyle. I realized how overwhelming it can be to pick what to wear every day. This project is all about empowering people to feel their best without the stress of decision-making. By using AI to suggest personalized outfits, we’re not just saving time; we’re helping users express their unique style and walk out the door with confidence. It’s about making fashion fun and accessible for everyone! 38 | 39 | ## Tech Stack 40 | _How have you built this project? Mention the technologies/methods/platforms you used to build your project_ 41 | 42 | Frontend- React 43 | Design- MaterialUI 44 | Backend- Appwrite 45 | Database-Appwrite 46 | 47 | ## Project Repo 48 | _Share a public repo link of your project_ 49 | 50 | https://github.com/SavantCode/FashionSathi 51 | 52 | ## Demo Video/Photos 53 | _Share a 2-3 minute demo video of your project_ 54 | ![1](https://github.com/user-attachments/assets/00a21b17-c605-460d-918d-7d54ac5dd1db) 55 | ![2](https://github.com/user-attachments/assets/7134006a-c45a-4929-9acf-f883fccd8444) 56 | ![3](https://github.com/user-attachments/assets/d884bbea-6998-4364-8b7e-e79dbb562018) 57 | ![4](https://github.com/user-attachments/assets/309ae20a-62f4-46de-917d-1dfd764cd9d6) 58 | ![5](https://github.com/user-attachments/assets/cc9a89da-ca47-4f75-9f25-b0a64b44f20d) 59 | ![6](https://github.com/user-attachments/assets/67719c8a-c2d6-4773-a51d-7da007f8252c) 60 | ![7](https://github.com/user-attachments/assets/e2f5eb04-a0b5-4887-95ad-51c5df767416) 61 | 62 | 63 | 64 | -------------------------------------------------------------------------------- /submissions/SoundStake.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: SoundStake 2 | 3 | ## GitHub handles of Team Members 4 | 5 | - [@Robinaditya1045](https://github.com/Robinaditya1045) 6 | - [@digvijay-555](https://github.com/digvijay-555) 7 | - [@vishal18713](https://github.com/vishal18713) 8 | - [@vedantJadhav0017](https://github.com/VedantJadhav0017) 9 | 10 | 11 | ## Project Title 12 | 13 | ## SoundStake 14 | 15 | 16 | ## Project Description 17 | 18 | Welcome to **Sound-Stake**, a music staking platform designed to revolutionize the relationship between artists and fans. By leveraging **Appwrite**, we enhance the user experience with powerful features like secure user authentication, real-time data synchronization, and efficient database management. These tools allow fans to easily create and manage accounts, track their investments, and stay updated on their favorite music projects. 19 | 20 | Our platform introduces a decentralized, blockchain-based solution that empowers direct interaction and collaboration. Through music staking, fans can invest in projects and share in the financial success of the artists they support. Utilizing blockchain technology, Sound-Stake rewards users with tokens for their contributions. 21 | 22 | ## Inspiration behind the Project 23 | 24 | In the current music industry, artists and creators often struggle to secure fair revenue from their work, as intermediaries such as labels, streaming platforms, and distributors take a significant portion of the profits. Meanwhile, fans and supporters who contribute to an artist’s success have limited opportunities to directly invest in and benefit from the music they love. This traditional model lacks transparency, equitable revenue distribution, and engagement between artists and their audience. 25 | 26 | ## Tech Stack 27 | 28 | - **Next.js**: A powerful React framework for building server-side rendered applications, facilitating the development of dynamic and SEO-friendly components. 29 | - **Solidity**: A smart contract programming language used to develop decentralized applications (dApps) on the Ethereum blockchain. 30 | - **Hardhat**: A development environment for compiling, deploying, testing, and debugging smart contracts on Ethereum-based blockchains. 31 | - **Pinata**: A service for securely managing and sharing files on IPFS, often used for hosting decentralized media or metadata. 32 | - **IPFS**: The InterPlanetary File System, a distributed protocol for storing and sharing files across a decentralized network. 33 | - **Vercel**: A deployment platform optimized for hosting Next.js applications with support for serverless functions, caching, and performance optimization. 34 | - **Appwrite**: An open-source backend server that provides a suite of tools for building applications, including user authentication, real-time data synchronization, and file storage. Appwrite enhances our platform by ensuring a secure, efficient, and user-friendly experience for both artists and fans. 35 | 36 | ## Project Repo 37 | 38 | GitHub repo : [SoundStake](https://github.com/Robinaditya1045/appwrite_soundstake) 39 | 40 | 41 | ## Demo Video/Photos 42 | 43 | Demo Video : [Video Link](https://www.youtube.com/watch?v=12YQQaCb86E&t=273s&pp=ygUKc291bmRzdGFrZQ%3D%3D) 44 | 45 | Deployment url : [soundstake.vercel.app](https://soundstake.vercel.app/) 46 | -------------------------------------------------------------------------------- /submissions/brieffly.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Brieffly 2 | 3 | ## GitHub handles of Team Members 4 | _Enter the GitHub handles of all your team members (including yourself) as separate bullet points_ 5 | 6 | - [Adithya Hegde Kota](https://github.com/hegdeadithyak) 7 | - [Honey Gyani](https://github.com/honeygyani) 8 | 9 | 10 | ## Project Title 11 | _What is the name of your project?_ 12 | 13 | - Brieffly 14 | 15 | ## Project Description 16 | _What have you built during the hackathon?_ 17 | 18 | - During the hackathon, I built Brieffly, an educational app aimed at simplifying complex study materials for competitive exams like IIT JEE by breaking down complicated formulas and theories into concise, easy-to-understand cards. Brieffly tackles a common problem faced by students – the overwhelming volume of information that they need to remember and understand during exam prep. Students often spend countless hours reviewing and revising, struggling to retain crucial information, which can be both mentally draining and time-consuming. 19 | 20 | - Brieffly **generates multiple cards** for each chapter, with each card containing an important formula or concept. Every card summarises the concept in less than 60 words, and it categorises it based on difficulty (beginner, intermediate, hard,advanced). The frontend interacts with the backend, which uses the Gemini API to create these concise summaries and Appwrite DB for managing user data. 21 | 22 | - Brieffly is designed to make revision sessions more efficient, giving students an effective tool for quick revision with a clear, accessible layout and efficient content delivery. 23 | 24 | 25 | ## Inspiration behind the Project 26 | _What is the story behind this project? Why did you choose to work on this specific idea?_ 27 | 28 | During my preparation for competitive exams like KVPY and IIT JEE, I often felt overwhelmed by the sheer volume of material to memorize and understand. I wished for a tool that could condense complex topics into quick, easy summaries for efficient revision. That experience inspired me to create Brieffly – a solution to simplify study sessions and make it easier for students to retain essential information. By turning dense concepts into short, digestible cards, I hope Brieffly can give students the resource I always needed during my own journey. 29 | 30 | ## Tech Stack 31 | _How have you built this project? Mention the technologies/methods/platforms you used to build your project_ 32 | 33 | To build Brieffly, I used Next.js for both the frontend and backend, leveraging its full-stack capabilities to streamline the app's development. The frontend in Next.js creates an interactive, responsive interface, while the backend handles API routes and manages data flow. I integrated the Gemini API to generate concise summaries for complex concepts and formulas, while **Appwrite DB** stores and manages user data efficiently. 34 | 35 | ## Project Repo 36 | _Share a public repo link of your project 37 | 38 | https://github.com/hegdeadithyak/Brieffly 39 | 40 | https://brieffly-ten.vercel.app/ 41 | 42 | ## Demo Video/Photos 43 | _Share a 2-3 minute demo video of your project_ 44 | 45 | https://github.com/user-attachments/assets/ce215641-81e4-4426-b467-1c7361e528bb 46 | 47 | https://github.com/user-attachments/assets/00025bc4-b146-486e-8c01-c7869ff3108e 48 | 49 | 50 | 51 | -------------------------------------------------------------------------------- /submissions/app-comment.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: app-comment 2 | 3 | 4 | ## GitHub handles of Team Members 5 | @atybdot 6 | 7 | 8 | ## Project Title 9 | app-comment: elevating user engagement 10 | 11 | ## Project Description 12 | seamlessly integrate a comment section into your React or Astro project with app-comment. This tool simplifies the process of creating and embedding a comment feature, allowing you to enhance user engagement without the technical hassle. 13 | No more headaches with complicated setups—just plug it in and let your users chat.It comes with features like real-time updates, user authentication. 14 | 15 | ### Features 16 | - customizable 17 | - Real-time updates 18 | - Not much setup required 19 | - Easy Onboarding 20 | - Easily integrate 21 | 22 | ## Inspiration behind the Project 23 | 24 | The inspiration for app-comment arose from observing the challenges bloggers face when trying to foster community engagement. Many existing solutions are either too complex or lock behind a paywall. We wanted to create a straightforward tool that not only simplifies the integration process but also enriches the user experience. By leveraging Appwrite's powerful services, we aimed to empower bloggers to create vibrant discussions around their content. 25 | 26 | 27 | ## Tech Stack 28 | 29 | - React for components 30 | - Appwrite for back-end services 31 | - tailwind for styling 32 | - biome - for consistent styling 33 | 34 | 35 | ### Usage of Appwrite 36 | 37 | - Auth : To keep things secure and let users sign up easily 38 | - Database : For storing comments, ensuring they load fast and are easy to manage. 39 | - Buckets : For user to upload custom pictures for their avatar 40 | // is not implemented yet 41 | 42 | 43 | ## Project Repo 44 | [github repo](https://github.com/atybdot/app-comment) 45 | 46 | 47 | ## Demo Video/Photos/Link 48 | [deployed link](https://app-comment.vercel.app/) 49 | 50 | home page 51 | ![](https://i.ibb.co/ZTmMdcz/screenzy-1730369746745.png) 52 | 53 | homepage after user login 54 | ![](https://i.ibb.co/VH8SKTM/screenzy-1730369982150.png) 55 | 56 | login 57 | ![](https://i.ibb.co/3r7DfcK/screenzy-1730370125971.png) 58 | 59 | sign-up 60 | ![](https://i.ibb.co/jZnFLvF/screenzy-1730370139127.png) 61 | 62 | editing comment 63 | ![](https://i.ibb.co/g7S2dL6/screenzy-1730370053341.png) 64 | 65 | ## Anything Else You Want To Share With Us? 66 | ### Project Goal 67 | The eventual goal of this project is to add comment section in your blogs / project with as little hassle as possible using appwrite. 68 | 69 | such that you just install this as 70 | ```bash 71 | npm i app-comment 72 | ``` 73 | then in your layout project 74 | ```jsx 75 | // layout.jsx 76 | import CommentSection from "app-comment" 77 | .... your code 78 | 79 | ``` 80 | This pkg is available on npm but it has error when importing 81 | you can check the main branch for npm pkg code 82 | [or check app-comment on npm](https://www.npmjs.com/package/app-comment) 83 | 84 | --- 85 | 86 | To make onboarding more easy i'm also developing a cli-app that will help users to integrate app-comment easily in their existing project 87 | e.g : 88 | ```bash 89 | npm @app-comment/cli 90 | ``` 91 | this will ask bunch of questions and then integrate app-comment in the existing project -------------------------------------------------------------------------------- /submissions/aChief.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: aChief 2 | 3 | ## GitHub handles of Team Members 4 | - @floherzler 5 | 6 | ## Project Title 7 | aChief: Own Your Stats, Lead the Game! 8 | 9 | ## Project Description 10 | I have built a webscraping service to bundle all available basketball game data of german professional basketball players in the second-highest leagues ProA and ProB. 11 | From these game statistics, I compute career overview statistics as a starting point for future usage in achieving you personal sports performance goals. 12 | 13 | Try it out here: [achief.vercel.app](https://achief.vercel.app/) 14 | 15 | ## Inspiration behind the Project 16 | I have played with the idea of creating something like this since last year but never got around to it. 17 | The initial idea was developed together with my friends from [LeadPeak](https://www.leadpeak.de/) performance program who manually keep track of all their player's data by checking the websites and copying numbers to Excel (ouch). 18 | This would greatly improve their data tracking and goal setting, since especially for aspiring youth players these metrics are important for their future success! 19 | 20 | ## Tech Stack 21 | - Next.js template project, nothing fancy (not a web dev) 22 | - [shadcn](https://ui.shadcn.com/) (I'm not a designer either) 23 | - [axios](https://axios-http.com/) and [cheerio](https://cheerio.js.org/) for web scraping via POST requests 24 | - Appwrite 25 | - Database with collections for players / league games 26 | - Realtime for updating the UI when data is entered / deleted 27 | ### Next Steps w/ Appwrite 28 | I'm planning on leveraging Appwrite even more: 29 | I would like to use Authentication to create Teams of player-coach like in LeadPeak and provide a platform for coordinated goal setting and achieving. 30 | This is a niche that is currently not filled, at least not in german basketball. 31 | I will use Appwrite Functions to update the manually added players with scheduled runs during weekdays in-season after each game. 32 | Additionally, I will create indices of my final database structures to create a searchable database of individual performances that does not exist in this general form in Germany yet. 33 | Season stats can be expanded to game stats and comparisons between players can be made. 34 | 35 | I used these two YouTube tutorials as heavy inspiration (repos in resp. description: 36 | - NetNinja [Realtime Tutorial](https://www.youtube.com/playlist?list=PL4cUxeGkcC9gXxY0nrh9N4CYHtwnoHjV2) 37 | - Hitesh Choudhary [Next.js Tutorial + Stackoverflow Clone](https://www.youtube.com/playlist?list=PLRAV69dS1uWRJcxXk1omgcMI07ygMxSRl) 38 | 39 | ## Project Repo 40 | [https://github.com/floherzler/achief-web](https://github.com/floherzler/achief-web) 41 | 42 | ## Demo Video/Photos 43 | There is only one landing page so far with adisplay carousel of added players and a create player form. 44 | Since a video would be overkill here, feel free to check out [my Notion page](https://floherzler.notion.site/aChief-Website-cb54878823344934a566818e971e903b) for a Screenshot. 45 | 46 | Or visit [achief.vercel.app](https://achief.vercel.app/)directly! 47 | 48 | Adding new players might not work at the moment after deploying to Vercel due to the timeout limitation, so I might need to move it somewhere else or lload seasons in batches. 49 | I added some players that you can browse through! 50 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # The Hack Code Of Conduct 2 | 3 | ## The Quick Version 4 | 5 | Our hackathon is dedicated to providing a safe and comfortable environment and harassment-free experience for everyone, regardless of the following: 6 | 7 | * gender 8 | * gender identity and expression 9 | * age 10 | * sexual orientation 11 | * disability 12 | * physical appearance 13 | * body size 14 | * race 15 | * ethnicity 16 | * nationality 17 | * religion 18 | * political views 19 | * previous hackathon attendance or lack of 20 | * computing experience or lack of 21 | * chosen programming language or tech stack 22 | 23 | We do not tolerate harassment of hackathon participants in any form. Sexual language and imagery is not appropriate at any hackathon venue, this includes the following. 24 | 25 | * hacks 26 | * talks, presentations, or demos 27 | * workshops 28 | * any parties associated to the hackathon 29 | * social media 30 | * any other online media 31 | 32 | --- 33 | 34 | ## The Less Quick Version 35 | 36 | Harassment includes offensive verbal comments related to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, nationality, religion or political views, sexual images in public spaces, deliberate intimidation, stalking, following, photography or audio/video recording against reasonable consent, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention. 37 | 38 | Photography is encouraged, but other participants must be given a reasonable chance to opt out from being photographed. If they object to the taking of their photograph, comply with their request. It is inappropriate to take photographs in contexts where people have a reasonable expectation of privacy (in bathrooms or where participants are sleeping). 39 | 40 | Participants asked to stop any harassing behavior are expected to comply immediately. 41 | 42 | As this is a hackathon, we like to explicitly note that the hacks created at our hackathon are equally subject to the anti-harassment policy. 43 | 44 | Sponsors and partners are also subject to the anti-harassment policy. In particular, sponsors should not use sexualised images, activities, or other material. Sponsor representatives (including volunteers) should not use sexualised clothing/uniforms/costumes, or otherwise create a sexualised environment. 45 | 46 | If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of hackathon staff immediately. 47 | 48 | Hackathon staff will be happy to help participants contact any local security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the hackathon. We value your attendance. 49 | 50 | If a participant engages in harassing behavior, the hackathon organisers may take any action they deem appropriate. This includes warning the offender, expulsion from the hackathon with no refund (if applicable), or reporting their behaviour to local law enforcement. 51 | 52 | We expect participants to follow these rules at hackathon and workshop venues and hackathon-related social events. 53 | 54 | --- 55 | 56 | ## Attribution 57 | 58 | This Code of Conduct has been taken from [hackcodeofconduct.org](https://hackcodeofconduct.org/) and created by [Cristiano Betta](https://betta.io/). 59 | The Code is available [here on GitHub](https://github.com/cbetta/hackcoc/). 60 | Feel free to make any suggestions or create your own version. 61 | -------------------------------------------------------------------------------- /submissions/Browser-Power-Tools.md: -------------------------------------------------------------------------------- 1 | 2 | # Hackathon Submission: Browser Power Toys 3 | 4 | ## GitHub handles of Team Members 5 | 6 | - @LohitNimbagal 7 | 8 | ## Browser Power Toys 9 | 10 | ## Project Description 11 | The Project I created is Browser Power Toys, a set of tools designed specifically for power users who want to maximize productivity directly within the browser. The first tool in this suite is YouTube Power Toys, which enhances the YouTube experience. 12 | 13 | ## Inspiration behind the Project 14 | The story behind **Browser Power Toys** started with my own experiences as a dedicated YouTube user. YouTube is an amazing free resource for both learning and entertainment, and its recommendation algorithm consistently serves up valuable content. But as someone who uses YouTube daily, I found myself hitting the **5,000-video** limit on the **Watch Later playlist** - a frustrating cap that forced me to create new playlists and go through extras steps just to save new videos. This interrupted my focus, especially when I was deep into learning. 15 | 16 | This experience sparked the idea for **YouTube Power Toys** - a tool that would streamline video management, helping power users like me stay organized without extra distractions. 17 | Currently, YouTube Power Toys is the first tool in the Browser Power Toys suite, designed to enhance the YouTube experience. Although right now it focuses on YouTube, the plan is to expand Browser Power Toys to include similar productivity tools for other platforms, ultimately creating a complete toolkit for power users across the web. 18 | 19 | ### Browser Power Toys 20 | 21 | 1. **YouTube Power Tools**: This tool displays an icon on every video on YouTube. When clicked, it automatically finds the playlist for the current month (if one doesn't exist, it creates a new playlist for the month) and adds the video to it. This feature streamlines the process of organizing and saving videos for easy access later. 22 | 23 | 24 | ## Tech Stack 25 | 26 | I built **Browser Power Toys Extension**, using **vanilla JavaScript** and **CSS** with **Manifest V3** for the Chrome extension framework. 27 | 28 | For the **frontend**, I used **Next.js** for server-side rendering and a smooth user experience, combined with **Tailwind CSS** for styling and **Shadcn** for UI components. This combination allows for a responsive, modern interface that enhances usability. 29 | 30 | On the **backend**, I utilized **Next.js API routes** to handle server-side logic and communication. Additionally, I integrated **Appwrite Cloud** for authentication and database management, ensuring secure user management and data storage. 31 | 32 | ## Project Repo 33 | 34 | [LohitNimbagal/browser-power-toys](https://github.com/LohitNimbagal/browser-power-toys) 35 | 36 | ## Demo Video/Photos 37 | 38 | [Browser Power Toys - YouTube Power Tools ( Demo )](https://youtu.be/QbcBiDz5Njo) 39 | 40 | ### More About Browser Power Toys 41 | 42 | **Browser Power Toys** is currently in beta, and I invite you to try it out! Experience the enhanced YouTube browsing features with **YouTube Power Toys** and see how it can improve your productivity. 43 | 44 | - [Try [Browser Power Toys](https://browserpowertoys.xyz/)] 45 | 46 | Your feedback and requests are greatly appreciated! They will help shape the future of this project and ensure it meets the needs of power users like you. Thank you for your support! 47 | 48 | ### Special Thanks 49 | 50 | A special thanks to **Appwrite** for conducting the **Appwrite Hacktoberfest '24** Hackathon, which inspired me to work on **Browser Power Toys**. 51 | -------------------------------------------------------------------------------- /submissions/heart-bridge.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Heart Bridge 2 | 3 | ## GitHub handles of Team Members 4 | 5 | - [@onukwilip](https://github.com/onukwilip) 6 | - [@python-fuse](https://github.com/python-fuse) 7 | - [@maxe01](https://github.com/maxe01) 8 | 9 | ## Project Title 10 | 11 | **Heart Bridge** 12 | 13 | ## Project Description 14 | 15 | The project we created is a crowdfunding platform designed specifically for orphanages, allowing them to set up accounts, add bank details, and list projects in need of funding. Donors, either anonymous or registered, can contribute to these projects, providing an accessible way for orphanages to receive donations and support. 16 | 17 | ## Inspiration behind the Project 18 | 19 | The idea for this project began when I remembered a childhood experience of visiting an orphanage with my mom. We had trouble finding orphanages nearby, and even when we did, they had little online presence for gathering donations or attracting visitors. This inspired me to create a platform where orphanages can set up online profiles, even with simple templates, to receive donations directly. Heart Bridge has since evolved from this initial idea, with some inspiration from platforms like GoFundMe. 20 | 21 | ## Tech Stack 22 | 23 | The technologies I used include: 24 | 25 | - **React & Next.js** - Frontend framework 26 | - **TypeScript** - Type-safe JavaScript 27 | - **Tailwind CSS** - For styling and UI 28 | - **PayStack** - Payment integration for donations 29 | - **Appwrite Authentication** - To manage registered users’ authentication 30 | - **Appwrite Database** - For data management 31 | - **Appwrite Storage** - To store files, photos, and videos uploaded to the platform 32 | - **Appwrite Real-time** - For receiving notifications of new donations 33 | - **Google Maps Places API** - For orphanages to set their exact location, ensuring accurate addresses 34 | - **Google Maps Reverse Geocoding API** - For users to search for orphanages nearby by area, city, or country 35 | 36 | ## Platform Features 37 | 38 | - Allows orphanages to create projects to receive donations from donors or anonymous visitors 39 | - Enables orphanages to set their locations and addresses using the Google Maps API 40 | - Provides donors the ability to search for nearby orphanages using the Google Geocoding API 41 | - Sends real-time notifications to orphanages and donors when donations are made or when a call or visitation is scheduled 42 | - Allows donors to schedule visits and calls with orphanages for authenticity validation 43 | 44 | ## Unique Value Proposition 45 | 46 | Unlike other crowdfunding platforms, Heart Bridge offers unique features to validate the authenticity of orphanage projects by allowing donors to speak with or visit orphanages before making a donation. Furthermore, by using the Google Maps Places API, we validate orphanage locations, ensuring donors can trust the legitimacy of the profiles they choose to support. 47 | 48 | ## Upcoming Features 49 | 50 | - Full implementation of visitation and call scheduling for donors to connect with orphanages more directly 51 | - Registered donors will be able to leave reviews on orphanage profiles and projects to further validate authenticity 52 | - Verification process for orphanages to confirm their legal status and improve platform trustworthiness 53 | - Support for additional payment methods, including Google Pay, Stripe, Venmo, and PayPal 54 | 55 | ## Project Repo 56 | 57 | [Heart Bridge GitHub Repository](https://github.com/onukwilip/heart-bridge) 58 | 59 | ## Demo Video/Photos 60 | 61 | [Demo Video](https://youtu.be/ILej8wSXecU) 62 | -------------------------------------------------------------------------------- /submissions/Patronus_Appwrite_hack_submission.md: -------------------------------------------------------------------------------- 1 | # **Hackathon Submission: Patronus** 2 | ===================================== 3 | 4 | ### **Team Member's GitHub Handle** 5 | - [@Vasu1712](https://github.com/Vasu1712) 6 | 7 | ### **Project Title** 8 | #### Patronus 9 | 10 | ### **Project Description** 11 | Patronus is your personalized web assistant designed to scour the internet for the cheapest flight tickets matching your query, saving you valuable time from hopping between different operator websites. 12 | 13 | 1. **Authentication**: Securely log in to access the intuitive calendar-based UI. 14 | 2. **Setup Your Journey**: 15 | - Select travel dates via our interactive calendar. 16 | - Choose your airports. 17 | - Specify the number of passengers. 18 | 3. **Request Flight Tickets**: With your preferences set, simply submit your request. 19 | 4. **Patronus at Work**: Receive the cheapest available flight tickets directly in your mailbox. 20 | 21 | ### **Inspiration behind Patronus** 22 | This project was born out of personal frustration - the tedious process of sifting through numerous flight options, wasting hours in search of the best deal. Patronus streamlines this process, saving you time, energy, and money. 23 | 24 | ### **Tech Stack** 25 | #### Frontend 26 | - **Built with**: NextJS 27 | - **Key Libraries**: 28 | - **`react-calendar`**: For developing an intuitive Calendar UI to book tickets. 29 | - **`react-select`**: To track date changes seamlessly. 30 | - **`huggingface-inference`**: Integrates Mistral LLM for enhanced flight query processing. 31 | - **`Amadeus API`**: Provides comprehensive flight information to the Mistral LLM for accurate responses. 32 | - **`tailwindcss`**: For a sleek and responsive UI design. 33 | 34 | #### Backend 35 | - **Powered by**: Appwrite 36 | 37 | ### **Usage of Appwrite** 38 | - **Authentication (Auth)**: Manages user signups and guest accounts with ease. 39 | - **Databases**: Securely stores flight ticket queries from the NextJS frontend. 40 | - **Functions**: Processes queries through the ML model and integrates with Mailgun for email responses. 41 | - **Messaging**: Utilizes Mailgun to send detailed flight ticket information (LLM response) to users. 42 | 43 | ### **Project Repository** 44 | [https://github.com/Vasu1712/Patronus.git](https://github.com/Vasu1712/Patronus.git) 45 | 46 | 47 | ## Demo Video/Photos/Link 48 | 49 | A video demo can be viewed here: https://drive.google.com/drive/folders/16b-4YZDSZJGb6B2EklKBjEwLCFsTVARx?usp=sharing 50 | 51 | 52 | The application can also be reached using this link: https://patronus-vasu1712.vercel.app/ 53 | 54 | 55 | ## Future Prospects for Patronus 56 | 57 | One of the most important prospect for Patronus is to build an in house LLM(or SML) ML model and train it on historical flight information using Amedus API and other details so that it can successfully predict the lowest flight ticket date and time and send the booking link to user mail inbox. 58 | 59 | ## Anything Else You Want To Share With Us? 60 | 61 | Appwrite has been one of the most sought after organisations that I have been following from Hacktober'22, I have read several of Dennis Ivy's blogs and followed appwrite over twitter and I have seen AppWrite's growth and when I saw this time they are orgainsing a hackathon, it was a no brainer for me to get around. This is the first time I used any BaaS and I would have to admit that AppWritedoes makes life pretty easy for full-stack devs that too with features to scale and as you say 'build like a team of hundreds'. I really like product, the idea and the problem appwrite is solving and would love to be a part this organization be it open-source, full-time or freelance. -------------------------------------------------------------------------------- /submissions/EduMeet_Web.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: EduMeet 2 | 3 | ## GitHub Handles of Team Members 4 | - @omprakash2929 5 | 6 | ## Project Title 7 | EduMeet: Revolutionizing Virtual Meetings Globally 8 | 9 | ## Project Description 10 | EduMeet is a virtual meeting platform designed to support businesses, educational institutions, and individual users with a powerful, data-driven alternative to traditional video conferencing software. EduMeet integrates tracking, scheduling, and analytics into a streamlined dashboard—all free of cost—making it a highly accessible and robust choice for remote teams, educators, and organizations worldwide. 11 | 12 | ## Inspiration Behind the Project 13 | With many organizations, especially educational institutions and startups, limited by the cost of subscription-based meeting software, EduMeet was created to address the need for a budget-friendly, feature-rich solution. EduMeet aims to bring professional-quality virtual meetings and data-driven insights to users who need cost-effective, reliable, and secure meeting software to maximize engagement, streamline management, and facilitate effective collaboration. 14 | 15 | ## Why EduMeet is Better than Other Platforms 16 | EduMeet offers significant advantages over traditional platforms like Zoom and Google Meet: 17 | - **Cost-Free, High-Quality Meetings**: Provides powerful meeting features without the need for paid plans, making it ideal for nonprofits, startups, and educational institutions. 18 | - **Engagement Tracking & Analytics**: Unlike other platforms, EduMeet tracks participation, join/leave times, screen sharing, and audio/video muting, essential for understanding engagement and attendance. 19 | - **Integrated Dashboard**: Centralizes meeting data, allowing hosts to view insights on engagement and participation, aiding post-meeting analysis. 20 | - **Dedicated Interview Scheduling**: Ideal for HR and recruiters, with tools to simplify interview processes and support recruitment. 21 | - **Session Recording & Compliance**: Offers the ability to record meetings for future reference, training, and compliance needs. 22 | - **Privacy & Data Security**: Built-in privacy features ensure a secure environment, especially important for sensitive information. 23 | 24 | ## Tech Stack 25 | - **Frontend**: React.js, TypeScript, Tailwind CSS 26 | - **Backend**: Node.js, Appwrite (Authentication) 27 | - **Database**: MongoDB 28 | - **Additional Tools**: WebRTC for video calling, third-party APIs (for scalability and screen sharing) 29 | 30 | ## Features Implemented 31 | - **User Authentication**: Using Appwrite to manage secure login and access control. 32 | - **Real-Time Engagement Tracking**: Custom analytics to monitor meeting activity such as join/leave times and screen-sharing frequency. 33 | - **Integrated Dashboard**: Centralized view for meeting data insights, attendance tracking, and participant engagement. 34 | - **Interview Scheduling**: Streamlined tools for scheduling and managing candidate interviews. 35 | - **Session Recording**: Allows meetings to be recorded for post-session review or compliance. 36 | 37 | ## Features in Development 38 | - **Scalable Real-Time Calls**: Exploring integration with WebRTC for real-time video and audio, enhanced by Appwrite’s Realtime Database for event tracking. 39 | - **Screen Sharing**: Leveraging WebRTC-based APIs for screen sharing, managed alongside Appwrite for seamless session control. 40 | 41 | ## Project Repo 42 | [EduMeet_Web GitHub Repository]https://github.com/omprakash2929/EduMeets_Web) 43 | 44 | ## Demo Video/Photos 45 | Check out a brief demo of EduMeet here: [EduMeet_Web Demo Video](https://drive.google.com/file/d/1othusVaPl5vB6p28spXow10zkKK2nfH5/view?usp=sharing) 46 | 47 | > Live Demo Link: [EduMeet Live Demo](https://edumeet.netlify.app/) 48 | (*Note: The initial load may be slow due to deployment on a free Render plan.*) 49 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Appwrite Hacktoberfest '24 Hackathon 2 | 3 | ## Table Of Contents 4 | 5 | - [Timeline](#timeline) 6 | - [Prizes](#prizes) 7 | - [How To Submit Your Project?](#how-to-submit-your-project) 8 | - [Rules and Code of Conduct](#rules-and-code-of-conduct) 9 | - [FAQ](#faq) 10 | 11 | ## Timeline 12 | 13 | * **Start Date and Time:** Oct 1st, 2024 at 12:00 AM PT 14 | * **End Date and Time:** Oct 31st, 2024 at 11:59 PM PT 15 | 16 | ## Prizes 17 | 18 | - **1st Prize** 19 | - Appwriter keyboards 20 | 21 | - **2nd and 3rd Prize** 22 | 23 | - Appwrite swag (hoodies and stickers) 24 | 25 | - **1 Random winner** (selected from all submissions) 26 | 27 | - Appwrite swag (hoodies and stickers) 28 | 29 | ## How To Submit Your Project? 30 | *(Watch [video tutorial on how to submit](https://youtu.be/zEYKnKD7dYE))* 31 | 32 | Follow the steps to submit your project in the hackathon: 33 | 34 | ### Step 1: Sign up 35 | 36 | - [Register](https://hacktoberfest.com/) for Hacktoberfest. 37 | 38 | - [Sign up](https://apwr.dev/htf24-hackathon) for the Hackathon (this must be done by all your team members). 39 | 40 | ### Step 2: Add project submission to this repo 41 | 42 | - Create a new branch/fork with the same name as your project title. 43 | 44 | - Visit the `submissions/` directory and create a copy of the `template_submission.md` with the same filename as your project title. 45 | 46 | - Enter all the necessary details as per the template. 47 | 48 | - Create a pull request. 49 | 50 | *Note: Step 2 must only be completed by only one member of your team if you have multiple team members.* 51 | 52 | ## Rules and Code of Conduct 53 | 54 | All participants must agree to the [Rules](RULES.md) and [Code of Conduct](CODE_OF_CONDUCT.md) to participate in the Hackathon. 55 | 56 | ## FAQ 57 | 58 | 1. What is the maximum team size? 59 | - 1 - 4 people 60 | 61 | 2. Is it mandatory for all hackers to register on the [Hackathon Sign Up page](https://apwr.dev/htf24-hackathon)? 62 | - Yes, this is mandatory for all hackers, even if you are a part of a team. Any participants who make submissions without registering will be disqualified from the final prizes. 63 | 64 | 3. Do I have to use any specific Appwrite product during the hackathon? 65 | - You can use any Appwrite product that you like. However, it is mandatory to use Appwrite Cloud for the hackathon. You can grab some Cloud credits for the hackathon by clicking [here](https://apwr.dev/hacktoberfest). 66 | 67 | 4. Does everyone on a winning team receive a prize? 68 | - If there is more than one member on a winning team, each member will receive the specified prize. 69 | 70 | 5. Are there any specific themes that a project must fit within? 71 | - No, there are not any specified themes. Hackers are free to build on whatever idea they like. 72 | 73 | 6. Who should I reach out to in case I need help building with Appwrite? 74 | - You can ask for help from the Appwrite team and our community of developers in our [Discord server](https://appwrite.io/discord). 75 | 76 | 7. How can I learn how to build with Appwrite? 77 | - You can: 78 | - Learn how to build with Appwrite through the [Appwrite Docs](https://appwrite.io/docs). 79 | - Find tutorials and blogs on Appwrite's services at the [Appwrite blog](https://appwrite.io/blog). 80 | - View our livestreams and video content at the [Appwrite YouTube channel](https://youtube.com/c/Appwrite). 81 | - Discover our community-made projects at the [Awesome Appwrite repo](https://github.com/appwrite/awesome-appwrite) and the [Built With Appwrite website](https://builtwith.appwrite.io/). 82 | 83 | 8. Do I need a debit/credit card to [redeem free Appwrite Cloud credits](https://apwr.dev/hacktoberfest) for this hackathon? 84 | - Yes, you need a debit/credit card to redeem the free Cloud credits. However, your card will not be charged as long as there are credits in your account. 85 | -------------------------------------------------------------------------------- /submissions/Orbit.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Orbit 2 | 3 | ## GitHub handles of Team Members 4 | _Enter the GitHub handles of all your team members (including yourself) as separate bullet points_ 5 | 6 | - [@psycho-baller](https://github.com/psycho-baller) 7 | 8 | ## Project Title 9 | _What is the name of your project?_ 10 | Orbit 11 | 12 | ## Project Description 13 | _What have you built during the hackathon?_ 14 | A mobile app that empowers university students to find and approach other people who share similar interests. Ultimately helping each one of us create lifelong friendships/relationships. Users can, in real-time see a list of other users who are also in the same area. Each user in the list has some information about them like their interests, what they are looking for, etc. Users can then request to meet up any user in that area. If the other user accepts the request, they would be taken to a chat screen where they can chat and decide where to meet or they can even share their precise location to easily find each other. Users can also set their status to "Open to meet" or "Not open to meet" to let other users know if they are looking for friends or not. They can configure certain times and areas where they are not open to meet. 15 | 16 | ## Inspiration behind the Project 17 | _What is the story behind this project? Why did you choose to work on this specific idea?_ 18 | Despite the world being more connected than ever, we are currently facing a loneliness epidemic. I love building products that help people feel more connected with the people around them. I strive to negate the effects social media has on all of us (in mental health and face-to-face social interactions). I am now on a mission to empower every university student the ability to find and approach other people who share similar interests. Ultimately helping each one of us create lifelong friendships. 19 | 20 | 3 years ago, I was a freshman at the University of Calgary. Due to several visa problems, I arrived to university one semester late. As a result, when I first arrived, I struggled to make friends. In the dining hall, I would see people who seemed interesting, but I never had the courage to approach them. I always thought to myself, "What if they don't want to talk to me?" or "What if they think I'm weird?" I always wished there was a way to know if they: 21 | - were open to talking to me 22 | - shared similar interests as me 23 | - were looking for friends too 24 | 25 | All these and several other excuses stopped me from forming friendships with people who could have been my best friend. 26 | 3 years later, I have (mostly) overcomed my fear of approaching strangers. Now, every time I go to the dining hall, I see people who seem to face the same problem as I used to. They would sit alone and just look around hoping someone would approach them and have lunch with them. I decided to approach these people and several others who were sitting alone. Tried to get an understanding of what stops them and what they really need. I found out that most of them were just like me. 27 | 28 | This is why I decided to build Orbit. 29 | 30 | More info in my journal: https://notes.rami-maalouf.tech/My-Greenhouse/How-Orbit-is-different-from-other-social-apps 31 | 32 | ## Tech Stack 33 | _How have you built this project? Mention the technologies/methods/platforms you used to build your project_ 34 | - SwiftUI 35 | - UIKit 36 | - Appwrite 37 | - Database 38 | - Authentication 39 | - Realtime 40 | - To show users who are also in the same area in real-time 41 | - TO help 2 users easily find each other when they both want to meet 42 | - Messaging 43 | - Apple Push Notifications 44 | - Storage to store user profile pictures and other assets 45 | - CoreLocation 46 | - Geofencing 47 | - Precise Location 48 | 49 | ## Project Repo 50 | _Share a public repo link of your project_ 51 | https://github.com/psycho-baller/Orbit 52 | 53 | ## Demo Video/Photos 54 | _Share a 2-3 minute demo video of your project_ 55 | https://youtu.be/ia-JUIwLbdw -------------------------------------------------------------------------------- /submissions/sketchy-board.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Sketchy Board 2 | 3 | 4 | ## GitHub handles of Team Members 5 | 6 | - @dkcoder02 7 | 8 | ## Project Title 9 | 10 | Sketchy Board 11 | 12 | ## Project Description 13 | I am creating Sketchy Board, a virtual system flow design tool tailored for engineers. This product enables users to seamlessly design, visualize, and collaborate on system flows. With support for multiple device logins, users can continue their work across devices without missing a beat. Sketchy Board ensures data reliability by storing user data locally and synchronizing it with a backend database, minimizing the risk of data loss. Whether online or offline, users can trust that their designs are always accessible and safe, making Sketchy Board a dependable tool for engineering system flow visualization. 14 | 15 | 16 | ## Inspiration behind the Project 17 | 18 | The story behind Sketchy Board stems from my own experience as an engineer working on complex system designs. I noticed that many existing tools lacked the simplicity and flexibility needed for engineers to quickly sketch and visualize system flows. Often, the available tools were either too cumbersome or didn’t offer robust data management, which could lead to lost progress or difficulty in collaborating across devices. 19 | 20 | I chose to work on Sketchy Board to address these challenges by creating a tool that combines ease of use with strong data reliability. With multiple device login support and data synchronization between local storage and a backend database, I wanted to ensure that engineers could design without the fear of losing their work. My goal is to make system flow design accessible, efficient, and seamless for engineers, no matter where they are or what device they use. 21 | 22 | ## Tech Stack 23 | 24 | I have built **Sketchy Board** using a modern and scalable tech stack. The frontend is powered by **Next.js**, ensuring high performance and responsiveness. I've incorporated **TypeScript** to enhance type safety and maintainability. To handle data validation, I'm using the **Zod schema validation library**, ensuring that all inputs are correct and secure. 25 | 26 | For the UI, I've integrated the **Shadcn component library**, which helps create a professional and intuitive interface without much overhead. On the backend, **Appwrite** serves as the backend-as-a-service, managing **user authentication**, **data storage**, and synchronization. This combination of technologies ensures that **Sketchy Board** is reliable, fast, and user-friendly, allowing engineers to focus on designing system flows without worrying about data loss or performance issues. 27 | 28 | ### Usage of Appwrite 29 | In Sketchy Board, I utilized the following Appwrite products: 30 | 31 | - Appwrite Authentication: I used Appwrite's auth services to manage user login and authentication securely. It allows users to access their accounts across multiple devices, ensuring a seamless experience. 32 | 33 | - Appwrite Storage: I leveraged Appwrite Storage to manage and store user data efficiently. This ensures that all user data, including system flow designs, is securely saved and can be synchronized between local storage and the backend, providing data consistency and reliability. 34 | 35 | These Appwrite services play a crucial role in ensuring secure and robust functionality for Sketchy Board. 36 | 37 | ## Project Repo 38 | 39 | https://github.com/dkcoder02/sketchy-touch 40 | 41 | 42 | ## Demo Video/Photos/Link 43 | 44 | https://sketchy-touch.vercel.app 45 | 46 | ## Anything Else You Want To Share With Us? 47 | 48 | I want to extend a big thank you to the Appwrite team for providing such an incredible platform that made building **Sketchy Board** seamless and efficient. The powerful backend services, especially **authentication** and **storage**, played a huge role in the success of this project. Your continuous support and innovative tools have been essential in bringing this idea to life. 49 | 50 | Thank you, Appwrite team! 51 | -------------------------------------------------------------------------------- /submissions/joblier.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Joblier 2 | 3 | ## GitHub handles of Team Members 4 | 5 | - @fasakinhenry 6 | - @fisayo-dev 7 | 8 | ## Project Title 9 | 10 | Joblier 11 | 12 | ## Project Description 13 | 14 | **AI-powered Job Search Platform** 15 | 16 | We created a platform that simplifies the process of Finding jobs with the help of AI. 17 | 18 | The app has two category of users: 19 | 20 | - Recruiters 21 | - Job Seekers 22 | 23 | The Recruiters have their portal which allows them to post jobs with requirement and see job seekers profile with their stats and all garnered through their portal. They can also see top professionals in the fields and initiate conversations with them. 24 | 25 | Job seekers platform has been built and has many of the following features that makes users get the job by helping them build their **skills**, **connection** and **reputation**. 26 | 27 | ### Features 28 | 29 | - Search for jobs by keyword, location, and category with job filters 30 | - View detailed job descriptions 31 | - Apply for jobs directly through the app 32 | - Save favorite jobs for later 33 | - Responsive design for mobile and desktop 34 | - AI powered Job search 35 | - Community to build connections with people 36 | - Bounties and challenges for professionals to prove their expertise 37 | - Jobs AI 38 | - AI-generated interview questions to prepare people for interview 39 | - Automated Notifications for developers 40 | - Feeback and rating system 41 | - Team collaboration tool(we only implemented hubs for co-creating tools) 42 | 43 | ## Inspiration behind the Project 44 | 45 | From my personal experience, the best ways to get jobs are by following three startegies that works 100% of the time. These strategies are: 46 | 47 | - Building your skills 48 | - Connecting with people(Building your connection) 49 | - Building your reputation 50 | 51 | These steps are really explanatory and these three concepts must be mastered so you can regarded when it comes to Job. 52 | 53 | It is advisable that you build your skills and then connect with people and build your reputation as a good and knowledgeable person that can be trusted with Jobs and would deliver with satisfaction. You can do all at once and that's why we built Joblier. 54 | 55 | Joblier aims to help you get the hang of these three concepts all at a time with the best user experience for everyone. Both the employers and people searching for Jobs. 56 | 57 | ## Tech Stack 58 | 59 | - **React JS**: Used to build the frontend interface. 60 | - **Appwrite**: Served as a robust backend for database records and management of user authentication 61 | - **Appwrite Databases**: For storing user and job details. 62 | - **Appwrite Authentication**: To manage user sessions, signup, and login functionality. 63 | - **Styling**: Tailwind CSS 64 | - **Build Tool**: Vite 65 | - **Linting**: ESLint 66 | - **Icons**: Iconify 67 | - **Languages**: JavaScript 68 | - **Deployment and Hosting**: Vercel for cloud hosting and deployment 69 | 70 | ## Project Repo 71 | 72 | https://github.com/fasakinhenry/jobsearch 73 | 74 | ## Demo Video/Photos 75 | 76 | https://www.loom.com/share/420bf3f52038429dbed610143e738a51?sid=b9155f91-04ba-4de3-85a2-aae2fbc1a9c4 77 | 78 | Landing Page 79 | 80 | ![image](https://github.com/user-attachments/assets/d14090d9-2ab7-45b1-85b2-e48f239ec0bd) 81 | 82 | Signup 83 | 84 | ![image](https://github.com/user-attachments/assets/bacc46e4-5bd2-4c68-a1ed-1bb5d17d1270) 85 | 86 | Login 87 | 88 | ![image](https://github.com/user-attachments/assets/a38d2181-4bab-4b3e-b88f-69b694178194) 89 | 90 | Home 91 | 92 | ![image](https://github.com/user-attachments/assets/8a265c92-183d-448d-9d32-246c2978f281) 93 | 94 | Find Jobs 95 | 96 | ![image](https://github.com/user-attachments/assets/8a0a9fab-e2e5-475a-801f-efd38c25d3bb) 97 | 98 | Community Home 99 | 100 | ![image](https://github.com/user-attachments/assets/42476e7f-703a-4df4-9256-6e45a3225bb4) 101 | 102 | Community Post 103 | 104 | ![image](https://github.com/user-attachments/assets/fce6e7da-8418-427e-89b0-647e8e21ab97) 105 | 106 | -------------------------------------------------------------------------------- /submissions/attendify.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: attendify 2 | 3 | ## GitHub handles of Team Members 4 | 5 | 12 | 13 | - @atulya-srivastava 14 | 15 | - @capsule11 16 | 17 | - @Sreejit-Sengupto 18 | 19 | ## Project Title 20 | 21 | attendify 22 | 23 | 26 | 27 | ## Project Description 28 | 29 | 32 | 33 | attendify is an attendance management application made for institutes for marking attendance of students at no extra infrastructure cost, it uses webauthentication to verify and mark attendance of the students. 34 | 35 | The application leverages webauthentication, to register user's device (public key), then the user can authenticate themselves using their device's lockscreen (password, pattern or even fingerprint). 36 | 37 | Here is the basic flow 38 | 39 | 1. The student sign up for the application and register their passkey from their device. 40 | 2. When a new class is started the student can enter their credentials (email or roll number) and click on mark attendance. 41 | 3. They will be prompted, and they need to scan a QR code, then they will get a prompt in their registered device to verify the passkey using fingerprint or lock screen password/pattern/etc. if the passkey is valid attendance will be marked successfully. 42 | 43 | ## Inspiration behind the Project 44 | 45 | 48 | 49 | WebAuthentication is a fairly recent technology. It became an official W3C standard in 2019 and is part of the FIDO2 Project, which aims to replace passwords with more secure, user-friendly authentication methods. 50 | 51 | WebAuthn allows users to authenticate on websites using public-key cryptography and devices like fingerprint scanners, facial recognition, or security keys. 52 | 53 | This technology has been adopted mainly as 2FA, like for confirming authenticity user before any payment but it can be used in other cases as well. Like the idea which inspired this project. To build an attendance system that reduces extra infrastructure cost for the Institutes/Organisations, like setting up Biometric Attendance systems. 54 | 55 | Users can simply register their passkeys which will eventually be used for confirming their authenticity. 56 | 57 | The application need not to be distributed individually to Institues like the current Biometric attendance systems and therefore this application can be built as a SaaS. 58 | 59 | Admins from Institute can register their organisation and provide the users with their organisation code, the users can then register themselves in the application for the Institute. 60 | 61 | This was the very basic motivation behind this project. We are still working on making it more secure and better and plan to work on it even after this hackathon submission. 62 | 63 | ## Tech Stack 64 | 65 | 68 | 69 | - React 70 | - Express 71 | - appwrite 72 | - Material UI 73 | - Tailwind 74 | - react-toastify 75 | - simplewebauthn 76 | 77 | ## Usage of appwrite 78 | 79 | We have utilised appwrite's accounts and databases for registering and segregating users as organisation and students and storing public passkeys. 80 | 81 | We will be working on the project even after the hackathon and we have planned to use - 82 | 83 | - Messaging: For notifying user's on successfull marking of attendance (We were working on this feature but then realised Mailgun doesn't support sending mails to other using a free account) 84 | 85 | - Storage: For storing ID Cards and Photos of student to enhance authenticity and security. 86 | 87 | ## Project Repo 88 | 89 | 92 | 93 | [https://github.com/Sreejit-Sengupto/attendify](https://github.com/Sreejit-Sengupto/attendify) 94 | 95 | ## Demo Video/Photos 96 | 97 | _Share a 2-3 minute demo video of your project_ 98 | 99 | 102 | 103 | [Project Demo Video](https://drive.google.com/file/d/1OuARULNOMJaqzm7wGzPwz4NMLMtAsm_m/view?usp=drive_link) 104 | -------------------------------------------------------------------------------- /submissions/rroist.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Rroist 2 | 3 | ## GitHub handles of Team Members 4 | 5 | - [@Dey11](https://github.com/dey11) 6 | - [@KIWILmao](https://github.com/KIWILmao) 7 | - [@Krish-Gupta07](https://github.com/Krish-Gupta07) 8 | 9 | 10 | ## Project Title 11 | _What is the name of your project?_ 12 | 13 | Rroist 14 | 15 | ## Project Description 16 | _What have you built during the hackathon?_ 17 | 18 | A dynamic form-building platform that enables users to design and host customizable forms with ease. Users can personalize their forms by choosing from various backgrounds or gradients and have full control over form fields, including reordering and adding validations. Once designed, forms can be hosted on our domain to collect responses, with responses visible through a dedicated dashboard. Additionally, users can export their forms as React components using our CLI tool, enabling seamless integration into any codebase, similar to shadcn's approach. This project simplifies form management and expands flexibility for developers and users alike. 19 | 20 | 21 | ## Inspiration behind the Project 22 | _What is the story behind this project? Why did you choose to work on this specific idea?_ 23 | 24 | The inspiration for this project came from the need for a streamlined, flexible solution to create and manage forms without the repetitive and time-consuming setup most developers face. Traditional form builders often lack customization options, making it difficult to fully align with branding or user experience requirements, and integrating these forms into existing projects usually requires additional code and maintenance. 25 | 26 | Our platform addresses these pain points by offering a fully customizable form-building experience with a rich selection of backgrounds and gradients, reorderable and editable fields, and built-in validation. Beyond form creation, we provide a hosted domain to collect responses with ease, all managed through an intuitive dashboard. This approach eliminates the need for separate tools or plugins for form creation, hosting, and response handling, offering a one-stop solution. 27 | 28 | A significant highlight of our project is the CLI tool that exports the form as a React component, which developers can integrate directly into their codebase. Inspired by tools like shadcn, this CLI enables developers to add complete form code into their projects with a single command, significantly speeding up the development process. This not only boosts productivity but also ensures consistency and modularity, making it a game changer for developers who want to quickly deploy forms without sacrificing customization. 29 | 30 | Currently in beta, this project will continue to evolve, with future updates and features that enhance the experience for both developers and end-users. We’re committed to making form management simpler, faster, and more adaptable to real-world needs. 31 | 32 | ## Future Scope 33 | The future scope of this project is expansive, with a roadmap aimed at enhancing functionality and user experience. Planned updates include: 34 | 35 | - **Component Expansion**: We plan to introduce additional customizable components, like testimonial sections and other common UI elements, that can be seamlessly integrated with the form builder. Also plan to make a documentation section for the same for ease of use. 36 | 37 | - **AI-Powered Insights**: By integrating AI capabilities, users will be able to analyze and summarize form responses, helping them derive actionable insights and saving time on data analysis. 38 | 39 | - **Advanced Customization Options**: Further personalization features, such as custom animations, multi-step forms, and conditional logic, are in the works to increase flexibility and user engagement. 40 | 41 | - **Enhanced Dashboard Analytics**: The dashboard will be upgraded to include more in-depth analytics, helping users track trends and response metrics with ease. 42 | 43 | - **Enhanced Security**: Increase security and privacy features. Allow form makers to accept only one response per user. 44 | 45 | These upcoming features will further establish our platform as a comprehensive, flexible tool that adapts to a wide range of use cases in form management and beyond. 46 | 47 | ## Tech Stack 48 | _How have you built this project? Mention the technologies/methods/platforms you used to build your project_ 49 | 50 | The technologies I used are: 51 | - Nextjs 52 | - Appwrite 53 | - Commander 54 | - Inquirer 55 | 56 | ## Usage of Appwrite 57 | - Auth 58 | - Databases 59 | - Storage 60 | 61 | ## Project Repo 62 | _Share a public repo link of your project_ 63 | 64 | [Rroist](https://github.com/Dey11/Appwrite-hackathon) 65 | 66 | ## Demo Video/Photos 67 | _Share a 2-3 minute demo video of your project_ 68 | 69 | [YouTube link](https://youtu.be/S2Z-rImbO2E) 70 | [Deployed link](https://rroist.vercel.app) 71 | -------------------------------------------------------------------------------- /submissions/Trackpot.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Trackpot 2 | 3 | ## Team Members 4 | - [@seemantshekhar43](https://github.com/seemantshekhar43) 5 | 6 | ## Project Title 7 | Trackpot - Smart Group Expense Tracker 8 | 9 | ## Project Description 10 | Trackpot is a modern expense tracking application built with Flutter that simplifies group expense management. It helps users track shared expenses, manage group finances, and settle balances effortlessly. The app features real-time expense tracking, intelligent bill splitting, and comprehensive payment management, making it perfect for roommates, trips, or any shared financial situations. 11 | 12 | Key features include: 13 | - Smart expense splitting with multiple split types 14 | - Real-time group balance tracking 15 | - Detailed payment management with media attachments 16 | - Comprehensive activity logging 17 | - Real-time notifications for expense-related activities 18 | - Multi-currency support 19 | - Rich media support for receipts and payments 20 | 21 | ## Inspiration behind the Project 22 | Managing shared expenses in groups has always been a challenging task, often leading to confusion, awkward conversations, and strained relationships. The inspiration behind Trackpot came from personal experiences of managing expenses during trips and with roommates. Traditional methods like spreadsheets or notes become cumbersome as the number of transactions grows. 23 | 24 | Trackpot aims to solve these pain points by providing a seamless, transparent, and user-friendly platform for group expense management. The goal is to eliminate the friction in shared finances and make expense tracking a breeze. 25 | 26 | ## Tech Stack 27 | 28 | ### Frontend 29 | - **Flutter**: Cross-platform mobile development framework 30 | - **Bloc**: State management solution 31 | - **GetIt**: Dependency injection 32 | - **Material 3**: Design system for modern UI/UX 33 | - **Custom Theme**: Implemented for both light and dark modes 34 | 35 | ### Backend (Appwrite) 36 | - **Appwrite Cloud**: Backend-as-a-Service solution 37 | - **Real-time Database**: For live updates 38 | - **Authentication**: Secure user management 39 | - **Storage**: Media file management 40 | - **Functions**: Server-side computations 41 | 42 | ### Architecture 43 | - **Clean Architecture**: For maintainable and scalable codebase 44 | - **Feature-first**: Organization structure 45 | - **Repository Pattern**: Data management 46 | - **Domain-driven Design**: Business logic organization 47 | 48 | ## Appwrite Feature Usage 49 | 50 | ### Authentication 51 | - **Email Authentication**: User registration and login 52 | - **Account Management**: Profile updates and user settings 53 | - **Session Handling**: Secure token management 54 | 55 | ### Database 56 | - **Users Collection**: 57 | - Stores user profiles 58 | - Manages user preferences 59 | - Tracks user metadata 60 | - **Groups Collection**: 61 | - Group details and members 62 | - Group settings and preferences 63 | - **Expenses Collection**: 64 | - Expense records with metadata 65 | - Split calculations 66 | - Payment status 67 | - **Payments Collection**: 68 | - Payment records 69 | - Settlement tracking 70 | - Payment proof references 71 | 72 | ### Storage 73 | - **Expense Receipts**: 74 | - Store and manage expense receipt images 75 | - Organize receipts by group and date 76 | - **Payment Proofs**: 77 | - Store payment screenshots/proofs 78 | - Manage payment verification documents 79 | - **Profile Pictures**: 80 | - User avatar storage 81 | - Profile image management 82 | 83 | ### Realtime 84 | - **Live Updates**: 85 | - Expense additions/modifications 86 | - Payment status changes 87 | - Group member updates 88 | - **Notifications**: 89 | - New expense alerts 90 | - Payment reminders 91 | - Group activity updates 92 | 93 | ### Messaging 94 | - **Push Notifications**: 95 | - Device token management for mobile devices 96 | - Real-time expense notifications 97 | - Payment request alerts 98 | - Group invitation notifications 99 | - Settlement reminders 100 | - New member notifications 101 | - Activity updates 102 | - **Notification Topics**: 103 | - Group-based notification channels 104 | - Custom notification preferences 105 | - Priority-based message delivery 106 | 107 | ### Functions 108 | - **Balance Calculations**: 109 | - Group balance computation 110 | - Individual share calculations 111 | - **Currency Conversions**: 112 | - Multi-currency support 113 | - Exchange rate updates 114 | 115 | ## Project Repository 116 | https://github.com/seemantshekhar43/trackpot 117 | 118 | ## Demo Video/Photos 119 | https://drive.google.com/drive/folders/1Mua3pZQpVpnc7Wvxtj2tBBHTZvfuZNZV?usp=sharing 120 | [Demo video and app screenshots are present in this google drive folder] 121 | -------------------------------------------------------------------------------- /submissions/NyxAPI.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: NyxAPI 2 | 3 | 4 | ## GitHub handles of Team Members 5 | - [Sushil Pandey](https://github.com/sushilpandeyy) 6 | - [Sahil Sharma](https://github.com/Sahil-Sharma06) 7 | - [Raj Singh](https://github.com/Rajsingh251) 8 | - [Sachin Kumar](https://github.com/SACHINKUMAR1728) 9 | 10 | ## Project Title 11 | 12 | #NyxAPI 13 | 14 | ## Project Description 15 | NyxAPI is a tool that helps developers quickly create mock APIs, so front-end and back-end teams can work independently and stay productive even when certain parts of the project are still being developed. With NyxAPI, front-end developers can start building and testing features right away, even before the back-end is ready. This reduces delays and dependency on other team members, making it easier to keep the project moving forward. 16 | 17 | 18 | 23 | 24 | ## Inspiration behind the Project 25 | The inspiration for NyxAPI came during my experience at Smart India Hackathon (SIH). I was part of a project where our frontend team faced significant roadblocks because the backend development wasn't ready yet. This created a bottleneck that slowed our progress; we couldn’t start testing or refining our UI and functionality without those APIs in place. When the backend was finally ready, we had very limited time left to integrate everything and iron out any issues. 26 | 27 | This experience highlighted how crucial it is for front-end and back-end teams to be able to work independently. With NyxAPI, I aimed to create a tool that enables frontend developers to start building and testing their interfaces right from the start, without waiting on the backend. NyxAPI empowers teams to stay agile, ensuring that projects keep moving forward smoothly regardless of dependencies. 28 | 33 | 34 | ## Tech Stack for NyxAPI 35 | 36 | NyxAPI was built with a robust and modern tech stack, designed for scalability, performance, and ease of use. Here’s a breakdown of the technologies and tools used to bring NyxAPI to life: 37 | 38 | - **Frontend**: Built with **React** and styled using **Tailwind CSS**, the frontend provides a responsive and interactive user interface. React’s component-based architecture allows us to efficiently manage state and UI, while Tailwind CSS makes designing flexible and highly customizable. 39 | 40 | - **Backend**: The backend is powered by **Python** with **SQLAlchemy** as the ORM (Object Relational Mapper), making database management efficient and code more readable. SQLAlchemy’s flexibility allows us to easily connect with our **PostgreSQL** database, which serves as the primary data store, offering reliable and scalable data management. 41 | 42 | - **Database**: **PostgreSQL** was chosen for its performance and robust data integrity. Its ACID-compliance and ability to handle complex queries make it a great fit for handling the mock data generated by NyxAPI. 43 | 44 | - **Deployment**: NyxAPI's backend is deployed on **AWS EC2** for reliable hosting, leveraging Amazon’s scalable infrastructure. For enhanced security and performance, **Cloudflare** is used for frontend deployment. 45 | 46 | - **Image Handling**: For handling image uploads, **Appwrite** was integrated into the project. Appwrite provides a straightforward and developer-friendly platform to store and manage media, ensuring images are securely uploaded and accessed when needed. 47 | 48 | Together, this tech stack powers NyxAPI’s seamless mock API generation, helping development teams stay productive and collaborate effectively. 49 | 50 | 51 | 56 | 57 | ### Usage of Appwrite 58 | 59 | NyxAPI utilizes **Appwrite** for efficient image storage and management, allowing seamless uploading, storing, and serving of user-uploaded images while ensuring secure access and smooth user experience. In the future, we plan to implement **One-Time Password (OTP) authentication** with Appwrite, adding an extra layer of security during user login. This integration will help safeguard sensitive information and ensure that only authorized users can access their accounts. 60 | 61 | 76 | 77 | ## Project Repo 78 | 79 | 80 | ### [Github Public Repo Link](https://github.com/sushilpandeyy/NyxAPI) 81 | 86 | 87 | ## Demo Video/Photos/Link 88 | 89 | [Demo Video](https://youtu.be/PqZGlVOtCkg) 90 | 91 | 92 | 93 | 98 | 99 | ## Anything Else You Want To Share With Us? 100 | 101 | -------------------------------------------------------------------------------- /submissions/wisdoma.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Wisdoma: Your Note-Taking App, Visualizing Your Notes through Knowledge Graphs 2 | 3 | ## GitHub handles of Team Members 4 | [@OMGATE23](https://github.com/OMGATE23) 5 | 6 | ## Project Title 7 | **Wisdom: Your Notes Visualized through Knowledge Graphs** 8 | 9 | ## Project Description 10 | Wisdoma is a cutting-edge note-taking application designed to enhance your learning journey through exceptional organisation and visualisation solutions. With Wisdoma, you can visualise your notes using intuitive Knowledge Graphs, radial layouts, and simple tree structures, transforming the way you interact with your notes. Whether you prefer quick, messy notes or a meticulously organised system, Wisdoma scales with your workflow, providing a flexible environment that adapts to your unique note-taking style. Experience the power of interconnectedness and clarity in your notes like never before. 11 | 12 | ### Key Features 13 | 14 | 1. Knowledge Graphs for Enhanced Connectivity: Visualize your notes and folders through Knowledge Graphs, which illustrate the relationships within your content. With advanced visualisation options like intuitive graphs, radial layouts, and tree structures, you can effortlessly explore interconnected ideas and information. This dynamic feature enhances your understanding and retention by allowing you to see connections at a glance, making it easy to locate key information, recognise patterns, and derive insights from your entire note collection. 15 | 16 | 2. Powerful WYSIWYG Editor: A user-friendly text editor that simplifies formatting, catering to all users from students to professionals, making note-taking intuitive and enjoyable. 17 | 18 | 3. Intuitive File and Folder Organization: Wisdoma employs a structured folder system that helps you categorize and store your notes effectively. This organization keeps related content grouped, making it easy to retrieve and reference notes as your collection grows. 19 | 20 | ## Inspiration behind the Project 21 | I’ve always loved taking notes, but they often got buried across multiple documents, leaving me with scattered information and no cohesive way to bring them all together. I couldn’t find a solution that let me quickly jot down ideas while also supporting more structured, interconnected notes that I could easily reference and build upon. 22 | 23 | Wisdoma was born from this need. It is a flexible platform where notes aren’t isolated bits of information but parts of a cohesive, evolving system. With Wisdoma, I wanted to create an experience that would make it simple to organize, connect, and visualize my notes in a way that’s both intuitive and powerful. 24 | 25 | ## Tech Stack 26 | Technologies Used: 27 | 28 | Frontend: **React, TypeScript, and TailwindCSS** 29 | 30 | Backend and BaaS: **Appwrite** 31 | 32 | ### Usage of Appwrite 33 | 34 | 1. Appwrite Auth: Used it to authenticate and authorise users of Wisdoma 35 | 36 | 2. Appwrite DB: Used to store notes and folders as securely and elegantly as possible 37 | 38 | 3. Appwrite Storage: Store images and videos in your notes to make your notes more informative 39 | 40 | ### How Appwrite Helped Build This App Quickly 41 | 42 | 1. Authentication: Appwrite’s built-in auth service integrated seamlessly in my app. Plus, the fact that Appwrite’s features like DB and Storage operate within its Authorization layer makes it an extremely secure solution. 43 | 44 | 2. Structured Database Collections: Appwrite’s collection setup proved invaluable for supporting Wisdoma’s requirements. Appwrite’s schema made data reliable and removed the burden of client-side validations, resulting in a robust, dependable database. 45 | 46 | 3. Efficient SDK and API: Appwrite’s SDK is intuitive, with a minimal learning curve, making it incredibly efficient to implement in Wisdoma and saving valuable development time. 47 | 48 | 4. Secure Media Storage: As a media-rich notes app, Wisdoma needed reliable storage for images and videos, which Appwrite’s secure file storage provided seamlessly. The built-in security layer makes storing media a safe experience, offering users a product they can trust 49 | 50 | ## Project Repo 51 | https://github.com/OMGATE23/wisdoma 52 | 53 | ## Demo Video/Photos 54 | https://www.youtube.com/watch?v=0iKMxoUFH0w 55 | 56 | Visit Wisdoma at: [https://getwisdoma.vercel.app/](https://getwisdoma.vercel.app/) 57 | 58 | ### Wisdoma Dashboard 59 | Screenshot 2024-11-01 at 11 31 38 AM 60 | 61 | ### Your notes in Wisdoma 62 | Screenshot 2024-11-01 at 11 31 58 AM 63 | 64 | ### Your Knowledge Graph in Wisdoma 65 | Screenshot 2024-11-01 at 11 32 41 AM 66 | 67 | 68 | -------------------------------------------------------------------------------- /submissions/Askinator.md: -------------------------------------------------------------------------------- 1 | # Hackathon Submission: Askinator 2 | 3 | ## GitHub handles of Team Members 4 | _Enter the GitHub handles of all your team members (including yourself) as separate bullet points_ 5 | 6 | - @tanguypouriel 7 | - @BLKKKBVSIK 8 | 9 | 10 | ## Project Title 11 | _What is the name of your project?_ 12 | 13 | Askinator 14 | 15 | ## Project Description 16 | _What have you built during the hackathon?_ 17 | 18 | Askinator, a spooky twist on the classic [Akinator](https://en.akinator.com/) game! 19 | In this project, the AI has chosen a character, and your goal is to uncover it by asking questions. 20 | But beware—the AI can only answer 'Yes' or 'No'! 21 | 22 | ## Inspiration behind the Project 23 | _What is the story behind this project? Why did you choose to work on this specific idea?_ 24 | 25 | Inspired by [Akinator](https://en.akinator.com/)’s character-guessing mechanics, we wanted to reverse the roles, where the AI picks the character, and the user has to ask the right questions to figure it out. 26 | Halloween’s iconic characters provided a fun, seasonal layer to the gameplay perfectly aligning with the October 31st submission date. 27 | 28 | ## Tech Stack 29 | _How have you built this project? Mention the technologies/methods/platforms you used to build your project_ 30 | 31 | 32 | The project is made using [Flutter](https://flutter.dev/) a Google UI framework created in 2017. 33 | It uses the Google language Dart created in 2011, [Dart](https://dartlang.org/). 34 | 35 | This approach enabled us to target the three main platforms we aimed to develop for: Android, iOS, and the web. 36 | 37 | The application is based on a MVVM architecture using [Stacked](https://pub.dev/packages/stacked) by FilledStacks as a state management. 38 | The usage of [Stacked](https://pub.dev/packages/stacked) is for maintainability and readability. 39 | [Stacked](https://pub.dev/packages/stacked) uses implicitly the [Provider](https://pub.dev/packages/provider) package. 40 | The main idea is to use an MVVM pattern to remove any business logic from the UI layouts by putting this logic in a separated view model. This adds more clarity and maintainability. 41 | 42 | We can decompose the project into 3 layers: the Models, The Views, and finally the ViewModels. 43 | 44 |

45 | 46 |

47 | 48 | In the project, the views are for display only. 49 | They can trigger interactions through Buttons/GestureDetector/Events that will call ViewModel methods. 50 | 51 | The ViewModel class can extend different types of abstract ViewModels such as: 52 | 53 | - [BaseViewModel](https://github.com/Stacked-Org/stacked/blob/master/README_old.md#baseviewmodel-functionality) 54 | - [ReactiveViewModel](https://github.com/Stacked-Org/stacked/blob/master/README_old.md#reactiveviewmodel) 55 | - And many more, but we mostly use those ones, you can refer to the [stacked documentation](https://pub.dev/documentation/stacked/latest/stacked/stacked-library.html#classes) 56 | 57 | The ViewModel data-bind all the data from the services and models and create getters for the view and notify the view of any changes (using a ReactiveServiceMixin or a NotifyListeners) 58 | 59 | #### **And of course we used AppWrite.io** 60 | 61 | The project utilizes [AppWrite.io](https://appwrite.io/) as a cloud backend to handle: 62 | 63 | - Database Management: Stores information about the leaderboard. 64 | - Anonymous Authentication: Allows players to start the game without requiring sign-in, making it easy and accessible for quick sessions. 65 | - Cloud Functions: Calls a Hugging Face API to enable the AI to respond with a "Yes" or "No" to user questions. 66 | 67 | This integration allows the app to offer a seamless, interactive experience by handling backend processing efficiently, while Hugging Face provides the natural language processing capability for AI responses. 68 | 69 | ## Project Repo 70 | _Share a public repo link of your project_ 71 | 72 | [https://github.com/BLKKKBVSIK/Askinator](https://github.com/BLKKKBVSIK/Askinator) 73 | 74 | ## Demo Video/Photos 75 | _Share a 2-3 minute demo video of your project_ 76 | 77 | 78 | [![Watch the video](https://github.com/user-attachments/assets/71dfad97-f872-42a8-b668-e593f5e5a864)](https://www.youtube.com/watch?v=pXO6IXGCl1s) 79 | [![Watch the video](https://github.com/user-attachments/assets/e5618563-2ef9-417a-ba76-f2054041744b)](https://www.youtube.com/watch?v=pXO6IXGCl1s) 80 | 81 | 82 | You can see the promo video by clicking [this link](https://www.youtube.com/watch?v=pXO6IXGCl1s). 83 | 84 | Play on your browser: [https://askinator-c6fe5.web.app/](https://askinator-c6fe5.web.app/) 85 | Play on your iPhone by joining the beta: [TestFlight](https://testflight.apple.com/join/UDH124NH) 86 | Play on your Android by downloading the APK file in [this release](https://github.com/BLKKKBVSIK/Askinator/releases/tag/v1.0.0) 87 | --------------------------------------------------------------------------------