├── .github ├── CODEOWNERS ├── ISSUE_TEMPLATE │ ├── bug_report.yaml │ ├── build.yaml │ ├── chore.yaml │ ├── ci.yaml │ ├── config.yml │ ├── documentation.yaml │ ├── feature_request.yaml │ ├── performance.yaml │ ├── refactor.yaml │ ├── revert.yaml │ ├── style.yaml │ └── test.yaml ├── PULL_REQUEST_TEMPLATE.md └── workflows │ └── sync_labels.yaml ├── .gitignore ├── CONTRIBUTING.md ├── LICENSE └── README.md /.github/CODEOWNERS: -------------------------------------------------------------------------------- 1 | # Every request must be reviewed and accepted by: 2 | 3 | * @VeryGoodOpenSource/codeowners 4 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug_report.yaml: -------------------------------------------------------------------------------- 1 | name: Bug Report 2 | description: Create a report to help us improve 3 | title: "fix: " 4 | labels: [bug] 5 | body: 6 | - type: textarea 7 | id: description 8 | attributes: 9 | label: Description 10 | description: A clear and concise description of what the bug is. 11 | placeholder: "Describe the bug." 12 | validations: 13 | required: true 14 | - type: textarea 15 | id: setps-to-reproduce 16 | attributes: 17 | label: Steps To Reproduce 18 | description: A set of instructions, step by step, explaining how to reproduce the bug. 19 | placeholder: | 20 | 1. Go to '...' 21 | 2. Click on '....' 22 | 3. Scroll down to '....' 23 | 4. See error 24 | validations: 25 | required: true 26 | - type: textarea 27 | id: expected-behavior 28 | attributes: 29 | label: Expected Behavior 30 | description: A clear and concise description of what you expected to happen. 31 | placeholder: "Describe what you expected to happen." 32 | validations: 33 | required: true 34 | - type: textarea 35 | id: additional-context 36 | attributes: 37 | label: Additional Context 38 | description: Add any other context, including links/screenshots/video recordings/etc about the problem here. 39 | placeholder: "Provide context here." 40 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/build.yaml: -------------------------------------------------------------------------------- 1 | name: Build System 2 | description: Changes that affect the build system or external dependencies 3 | title: "build: " 4 | labels: [build] 5 | body: 6 | - type: textarea 7 | id: description 8 | attributes: 9 | label: Description 10 | description: Describe what changes need to be done to the build system and why 11 | placeholder: "Describe the build system change." 12 | validations: 13 | required: true 14 | - type: textarea 15 | id: requirements 16 | attributes: 17 | label: Requirements 18 | description: The list of requirements that need to be met in order to consider the ticket to be completed. Please be as explicit as possible. 19 | value: | 20 | - [ ] All CI/CD checks are passing. 21 | - [ ] There is no drop in the test coverage percentage. 22 | validations: 23 | required: true 24 | - type: textarea 25 | id: additional-context 26 | attributes: 27 | label: Additional Context 28 | description: Add any other context, including links/screenshots/video recordings/etc about the problem here. 29 | placeholder: "Provide context here." 30 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/chore.yaml: -------------------------------------------------------------------------------- 1 | name: Chore 2 | description: Other changes that don't modify source or test files 3 | title: "chore: " 4 | labels: [chore] 5 | body: 6 | - type: textarea 7 | id: description 8 | attributes: 9 | label: Description 10 | description: Clearly describe what change is needed and why. If this changes code then please use another issue type. 11 | placeholder: "Provide a description of the chore." 12 | validations: 13 | required: true 14 | - type: textarea 15 | id: requirements 16 | attributes: 17 | label: Requirements 18 | description: The list of requirements that need to be met in order to consider the ticket to be completed. Please be as explicit as possible. 19 | value: | 20 | - [ ] No functional changes to the code. 21 | - [ ] All CI/CD checks are passing. 22 | - [ ] There is no drop in the test coverage percentage. 23 | validations: 24 | required: true 25 | - type: textarea 26 | id: additional-context 27 | attributes: 28 | label: Additional Context 29 | description: Add any other context, including links/screenshots/video recordings/etc about the problem here. 30 | placeholder: "Provide context here." 31 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/ci.yaml: -------------------------------------------------------------------------------- 1 | name: Continuous Integration 2 | description: Changes to the CI configuration files and scripts 3 | title: "ci: " 4 | labels: [ci] 5 | body: 6 | - type: textarea 7 | id: description 8 | attributes: 9 | label: Description 10 | description: Describe what changes need to be done to the CI/CD system and why. 11 | placeholder: "Provide a description of the changes that need to be done to the CI/CD system." 12 | validations: 13 | required: true 14 | - type: textarea 15 | id: requirements 16 | attributes: 17 | label: Requirements 18 | description: The list of requirements that need to be met in order to consider the ticket to be completed. Please be as explicit as possible. 19 | value: | 20 | - [ ] All CI/CD checks are passing. 21 | - [ ] There is no drop in the test coverage percentage. 22 | validations: 23 | required: true 24 | - type: textarea 25 | id: additional-context 26 | attributes: 27 | label: Additional Context 28 | description: Add any other context, including links/screenshots/video recordings/etc about the problem here. 29 | placeholder: "Provide context here." 30 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/config.yml: -------------------------------------------------------------------------------- 1 | blank_issues_enabled: false -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/documentation.yaml: -------------------------------------------------------------------------------- 1 | name: Documentation 2 | description: Improve the documentation so all collaborators have a common understanding 3 | title: "docs: " 4 | labels: [documentation] 5 | body: 6 | - type: textarea 7 | id: description 8 | attributes: 9 | label: Description 10 | description: Clearly describe what documentation you are looking to add or improve. 11 | placeholder: "Provide a description of the documentation changes." 12 | validations: 13 | required: true 14 | - type: textarea 15 | id: requirements 16 | attributes: 17 | label: Requirements 18 | description: The list of requirements that need to be met in order to consider the ticket to be completed. Please be as explicit as possible. 19 | value: | 20 | - [ ] No functional changes to the code. 21 | - [ ] All CI/CD checks are passing. 22 | - [ ] There is no drop in the test coverage percentage. 23 | validations: 24 | required: true 25 | - type: textarea 26 | id: additional-context 27 | attributes: 28 | label: Additional Context 29 | description: Add any other context, including links/screenshots/video recordings/etc about the problem here. 30 | placeholder: "Provide context here." 31 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.yaml: -------------------------------------------------------------------------------- 1 | name: Feature Request 2 | description: A new feature to be added to the project 3 | title: "feat: " 4 | labels: [feature] 5 | body: 6 | - type: textarea 7 | id: description 8 | attributes: 9 | label: Description 10 | description: Clearly describe what you are looking to add. The more business/user context the better. 11 | placeholder: "Provide a description of the feature." 12 | validations: 13 | required: true 14 | - type: textarea 15 | id: requirements 16 | attributes: 17 | label: Requirements 18 | description: The list of requirements that need to be met in order to consider the ticket to be completed. Please be as explicit as possible. 19 | value: | 20 | - [ ] All CI/CD checks are passing. 21 | - [ ] There is no drop in the test coverage percentage. 22 | validations: 23 | required: true 24 | - type: textarea 25 | id: additional-context 26 | attributes: 27 | label: Additional Context 28 | description: Add any other context, including links/screenshots/video recordings/etc about the problem here. 29 | placeholder: "Provide context here." 30 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/performance.yaml: -------------------------------------------------------------------------------- 1 | name: Performance Update 2 | description: A code change that improves performance 3 | title: "perf: " 4 | labels: [performance] 5 | body: 6 | - type: textarea 7 | id: description 8 | attributes: 9 | label: Description 10 | description: Clearly describe what code needs to be changed and what the performance impact is going to be. Bonus point's if you can tie this directly to user experience. 11 | placeholder: " Provide a description of the performance update." 12 | validations: 13 | required: true 14 | - type: textarea 15 | id: requirements 16 | attributes: 17 | label: Requirements 18 | description: The list of requirements that need to be met in order to consider the ticket to be completed. Please be as explicit as possible. 19 | value: | 20 | - [ ] All CI/CD checks are passing. 21 | - [ ] There is no drop in the test coverage percentage. 22 | validations: 23 | required: true 24 | - type: textarea 25 | id: additional-context 26 | attributes: 27 | label: Additional Context 28 | description: Add any other context, including links/screenshots/video recordings/etc about the problem here. 29 | placeholder: "Provide context here." 30 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/refactor.yaml: -------------------------------------------------------------------------------- 1 | name: Refactor 2 | description: A code change that neither fixes a bug nor adds a feature 3 | title: "refactor: " 4 | labels: [refactor] 5 | body: 6 | - type: textarea 7 | id: description 8 | attributes: 9 | label: Description 10 | description: Clearly describe what needs to be refactored and why. Please provide links to related issues (bugs or upcoming features) in order to help prioritize. 11 | placeholder: "Provide a description of the refactor." 12 | validations: 13 | required: true 14 | - type: textarea 15 | id: requirements 16 | attributes: 17 | label: Requirements 18 | description: The list of requirements that need to be met in order to consider the ticket to be completed. Please be as explicit as possible. 19 | value: | 20 | - [ ] All CI/CD checks are passing. 21 | - [ ] There is no drop in the test coverage percentage. 22 | validations: 23 | required: true 24 | - type: textarea 25 | id: additional-context 26 | attributes: 27 | label: Additional Context 28 | description: Add any other context, including links/screenshots/video recordings/etc about the problem here. 29 | placeholder: "Provide context here." 30 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/revert.yaml: -------------------------------------------------------------------------------- 1 | name: Revert 2 | description: Revert a previous commit 3 | title: "revert: " 4 | labels: [revert] 5 | body: 6 | - type: textarea 7 | id: description 8 | attributes: 9 | label: Description 10 | description: Provide a link to a PR/Commit that you are looking to revert and why. 11 | placeholder: "Provide a description of and link to the commit that needs to be reverted." 12 | validations: 13 | required: true 14 | - type: textarea 15 | id: requirements 16 | attributes: 17 | label: Requirements 18 | description: The list of requirements that need to be met in order to consider the ticket to be completed. Please be as explicit as possible. 19 | value: | 20 | - [ ] Change has been reverted. 21 | - [ ] No change in unit/widget test coverage has happened. 22 | - [ ] A new ticket is created for any follow on work that needs to happen. 23 | validations: 24 | required: true 25 | - type: textarea 26 | id: additional-context 27 | attributes: 28 | label: Additional Context 29 | description: Add any other context, including links/screenshots/video recordings/etc about the problem here. 30 | placeholder: "Provide context here." 31 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/style.yaml: -------------------------------------------------------------------------------- 1 | name: Style 2 | description: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) 3 | title: "style: " 4 | labels: [style] 5 | body: 6 | - type: textarea 7 | id: description 8 | attributes: 9 | label: Description 10 | description: Clearly describe what you are looking to change and why. 11 | placeholder: "Provide a description of the style changes." 12 | validations: 13 | required: true 14 | - type: textarea 15 | id: requirements 16 | attributes: 17 | label: Requirements 18 | description: The list of requirements that need to be met in order to consider the ticket to be completed. Please be as explicit as possible. 19 | value: | 20 | - [ ] All CI/CD checks are passing. 21 | - [ ] There is no drop in the unit or widget test coverage percentage. 22 | validations: 23 | required: true 24 | - type: textarea 25 | id: additional-context 26 | attributes: 27 | label: Additional Context 28 | description: Add any other context, including links/screenshots/video recordings/etc about the problem here. 29 | placeholder: "Provide context here." 30 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/test.yaml: -------------------------------------------------------------------------------- 1 | name: Test 2 | description: Adding missing tests or correcting existing tests 3 | title: "test: " 4 | labels: [test] 5 | body: 6 | - type: textarea 7 | id: description 8 | attributes: 9 | label: Description 10 | description: List out the tests that need to be added or changed. Please also include any information as to why this was not covered in the past. 11 | placeholder: "Provide a description of the tests that need to be added or changed." 12 | validations: 13 | required: true 14 | - type: textarea 15 | id: requirements 16 | attributes: 17 | label: Requirements 18 | description: The list of requirements that need to be met in order to consider the ticket to be completed. Please be as explicit as possible. 19 | value: | 20 | - [ ] All CI/CD checks are passing. 21 | - [ ] There is no drop in the test coverage percentage. 22 | validations: 23 | required: true 24 | - type: textarea 25 | id: additional-context 26 | attributes: 27 | label: Additional Context 28 | description: Add any other context, including links/screenshots/video recordings/etc about the problem here. 29 | placeholder: "Provide context here." 30 | -------------------------------------------------------------------------------- /.github/PULL_REQUEST_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | 8 | 9 | ## Status 10 | 11 | **READY/IN DEVELOPMENT/HOLD** 12 | 13 | ## Description 14 | 15 | 16 | 17 | ## Type of Change 18 | 19 | 20 | 21 | - [ ] ✨ New feature (non-breaking change which adds functionality) 22 | - [ ] 🛠️ Bug fix (non-breaking change which fixes an issue) 23 | - [ ] ❌ Breaking change (fix or feature that would cause existing functionality to change) 24 | - [ ] 🧹 Code refactor 25 | - [ ] ✅ Build configuration change 26 | - [ ] 📝 Documentation 27 | - [ ] 🗑️ Chore 28 | -------------------------------------------------------------------------------- /.github/workflows/sync_labels.yaml: -------------------------------------------------------------------------------- 1 | name: ♻️ Sync Labels 2 | 3 | on: 4 | push: 5 | paths: 6 | - .github/labels.yml 7 | branches: 8 | - main 9 | workflow_dispatch: 10 | 11 | jobs: 12 | labels: 13 | name: ♻️ Sync labels 14 | runs-on: ubuntu-20.04 15 | steps: 16 | - name: ⤵️ Check out code from GitHub 17 | uses: actions/checkout@v4 18 | 19 | - name: 🚀 Run Label Sync 20 | uses: srealmoreno/label-sync-action@v1 21 | with: 22 | config-file: https://raw.githubusercontent.com/VeryGoodOpenSource/.github/main/.github/labels.yml 23 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | .DS_Store -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing to Awesome Dart Frog 2 | 3 | First off, thanks for taking the time to contribute! 🎉👍 4 | 5 | 6 | ## Submitting to the Awesome Dart Frog repo 7 | 8 | If you have a very good resource for Dart Frog that is worth showcasing, please feel free to submit a PR for consideration. 9 | 10 | 11 | ## Creating a Pull Request 12 | 13 | Before creating a pull request please: 14 | 1. Fork the repository and create your branch from `main`. 15 | 2. Add your changes to the README.md file where it makes the most sense (e.g. Articles and tutorials, Libraries and plugins, etc.). Feel free to add a new section if you're adding a new type of resource. Don’t forget to include a link to the resource you’re adding! 16 | 3. Squash your commits and ensure you have a meaningful, [semantic](https://www.conventionalcommits.org/en/v1.0.0) commit message. 17 | 4. Create the Pull Request. 18 | 19 | While the prerequisites above must be satisfied prior to having your pull request reviewed, the reviewer(s) may ask you to complete additional work or other changes before your pull request can be ultimately accepted. 20 | 21 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2023 Very Good Ventures 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | [![Dart Frog Logo][logo_white]][dart_frog_link_dark] 2 | [![Dart Frog Logo][logo_black]][dart_frog_link_light] 3 | 4 | [![Awesome](https://awesome.re/badge-flat2.svg)](https://awesome.re) 5 | 6 | # Awesome Dart Frog 7 | 8 | Welcome! This repo is intended to highlight some awesome Dart Frog resources — articles, videos, open source projects, and more! If you have something to add, please review the [contributing guide](https://github.com/VeryGoodOpenSource/awesome_dart_frog/blob/main/CONTRIBUTING.md) before opening a PR. 9 | 10 | [Dart Frog](https://github.com/VeryGoodOpenSource/dart_frog) is a fast, minimalistic backend framework for Dart built by [Very Good Ventures](https://verygood.ventures/). It can increase efficiency by allowing you to share code, tooling, and processes across the front and backend. 11 | 12 | ## Contents 13 | 14 | - [Awesome Dart Frog](#awesome-dart-frog) 15 | - [Contents](#contents) 16 | - [Articles and tutorials](#articles-and-tutorials) 17 | - [Series](#series) 18 | - [Articles by Felix Angelov](#articles-by-felix-angelov) 19 | - [Livestreams by Craig Labenz on the Flutter YouTube channel](#livestreams-by-craig-labenz-on-the-flutter-youtube-channel) 20 | - [Articles by Md. Mobin](#articles-by-md-mobin) 21 | - [Articles by Sailesh Dahal](#articles-by-sailesh-dahal) 22 | - [Articles and tutorials](#articles-and-tutorials-1) 23 | - [Libraries and plugins](#libraries-and-plugins) 24 | - [Official](#official) 25 | - [Community](#community) 26 | - [Projects](#projects) 27 | - [Open source repos](#open-source-repos) 28 | - [Apps](#apps) 29 | 30 | ## Articles and tutorials 31 | 32 | ### Series 33 | 34 | #### Articles by [Felix Angelov](https://twitter.com/felangelov) 35 | 36 | - [Dart Frog full stack tutorial](https://verygood.ventures/blog/dart-frog-full-stack-tutorial) 37 | - [Dart Frog is now stable 🎉](https://verygood.ventures/blog/dart-frog-stable) 38 | - [Dart on the server with Dart Frog](https://verygood.ventures/blog/dart-frog) 39 | 40 | #### Livestreams by [Craig Labenz](https://twitter.com/craig_labenz) on the [Flutter YouTube channel](https://www.youtube.com/@flutterdev) 41 | 42 | - [Observable Flutter: Code sharing & Postgres](https://youtu.be/WE-CYXE1xug): Explore code sharing between client and server and connect to a backend Postgres database. This example uses Dart Frog. 43 | - [Observable Flutter: Dart + Postgres](https://youtu.be/g76H6-MeHHk): Picking up from the last video, Craig improves the Postgres connection handling in his Dart Frog server-side app. 44 | 45 | #### Articles by [Md. Mobin](https://dev.to/djsmk123) 46 | 47 | - [Build Full stack application using Flutter ft. Dart frog and MongoDB. Part 1](https://dev.to/djsmk123/build-full-stack-application-using-flutter-ft-dart-frog-and-mongodb-part-1-1e2k) 48 | - [Build Full stack application using Flutter ft. Dart frog and MongoDB. Part 2](https://dev.to/djsmk123/build-full-stack-application-using-flutter-ft-dart-frog-and-mongodb-part-2-m1a) 49 | 50 | #### Articles by [Sailesh Dahal](https://saileshdahal.com.np/) 51 | 52 | - [Building a Fullstack App with dart_frog and Flutter in a Monorepo - Part 1](https://saileshdahal.com.np/building-a-fullstack-app-with-dartfrog-and-flutter-in-a-monorepo-part-1) 53 | - [Building a Fullstack App with dart_frog and Flutter in a Monorepo - Part 2](https://saileshdahal.com.np/building-a-fullstack-app-with-dartfrog-and-flutter-in-a-monorepo-part-2) 54 | - [Building a Fullstack App with dart_frog and Flutter in a Monorepo - Part 3](https://saileshdahal.com.np/building-a-fullstack-app-with-dartfrog-and-flutter-in-a-monorepo-part-3) 55 | - [Building a Fullstack App with dart_frog and Flutter in a Monorepo - Part 4](https://saileshdahal.com.np/building-a-fullstack-app-with-dartfrog-and-flutter-in-a-monorepo-part-4) 56 | - [Building a Fullstack App with dart_frog and Flutter in a Monorepo - Part 5](https://saileshdahal.com.np/building-a-fullstack-app-with-dartfrog-and-flutter-in-a-monorepo-part-5) 57 | - [Building a Fullstack App with dart_frog and Flutter in a Monorepo - Part 6](https://saileshdahal.com.np/building-a-fullstack-app-with-dartfrog-and-flutter-in-a-monorepo-part-6) 58 | 59 | ### Articles and tutorials 60 | 61 | - [Building a Tweet Screenshot API with Dart Frog 🐸, & Puppeteer 🐾 ](https://zfinix.medium.com/building-a-tweet-screenshot-api-with-dart-frog-puppeteer-7e8da301dd32) by Chiziaruhoma Ogbonda 62 | - [Dart Frog in 15 mins | Dart Frog for Server Apps 🎯🐸 | Dart on Server | Zero to Prod](https://www.youtube.com/watch?v=U0PqwMrIJcE) by aseem wangoo 63 | - [Use Dart on Servers with Dart Frog — The complete crash course](https://tomicriedel.medium.com/cff6fc9f033b) by Tomic Riedel 64 | - [Real-Time Games with Dart :: Flutter Forward](https://youtu.be/TGKipiJhpXo) by Dominik Roszkowski and Felix Angelov 65 | - [How to Create User Registration and Login API with Dart Frog + MongoDB + JWT](https://medium.com/@karokojnr/how-to-create-user-registration-and-login-api-with-dart-frog-mongodb-jwt-c4fb7f3f6086) by Kennedy Karoko 66 | - [Bridging the gap: Distributed tracing for Flutter and Backend](https://medium.com/@jonasuekoetter/bridging-the-gap-distributed-tracing-for-flutter-and-backend-4943799b0ea9) by Jonas Uekötter 67 | - [Crash Course: Basics of Dart Frog](https://www.youtube.com/watch?v=bN5XsAPr-oc) by UltrasDzCoder 68 | - [Elevate Your Flutter Web Hosting with Dart_Frog](https://jxstxn.dev/elevate-your-flutter-web-hosting-with-dartfrog) by Justin Baumann 69 | - [Building a Full Stack App with Dart and Flutter | MonoRepo, Melos, and Dart 3 Course](https://youtu.be/_LhSRbekY5k) by Codepur 70 | - [Dart Frog — The Frog Prince 🐸, Building Book Library Apis with Dart Frog](https://medium.com/@yousefsalah_85714/dart-frog-the-frog-prince-8dbb647b3e99) by Yousef Salah Kassem 71 | - [Seamless Full Stack Development using Flutter & Dart Frog](https://verygood.ventures/blog/seamless-full-stack-development-using-flutter-dart-frog) by Tom Arra 72 | - [Video Version](https://www.youtube.com/watch?v=2DJhzbhW0lQ) 73 | 74 | ## Libraries and plugins 75 | 76 | ### Official 77 | 78 | - [dart_frog_web_socket](https://pub.dev/packages/dart_frog_web_socket) by [Very Good Ventures](https://github.com/VeryGoodOpenSource): WebSocket support for Dart Frog. 79 | - [dart_frog_auth](https://pub.dev/packages/dart_frog_auth) by [Very Good Ventures](https://github.com/VeryGoodOpenSource): Header Authorization support for Dart Frog. 80 | 81 | ### Community 82 | 83 | - [sentry_dart_frog](https://pub.dev/packages/sentry_dart_frog) by [ueman](https://github.com/ueman): Sentry integration for dart_frog. Capture errors and trace performance. 84 | - [shelf_helmet](https://pub.dev/packages/shelf_helmet) by [jxstxn1](https://github.com/jxstxn1): A port of the NodeJS helmet package to Dart. Helmet helps you secure your Dart Shelf/Frog apps by setting various HTTP headers. 85 | - [shelf_enforces_ssl](https://pub.dev/packages/shelf_enforces_ssl) by [jxstxn1](https://github.com/jxstxn1): Enforces that users can only make API requests over HTTPS (SSL). 86 | 87 | ## Projects 88 | 89 | ### Open source repos 90 | 91 | - [I/O FLIP](https://github.com/flutter/io_flip): An AI-designed card game built with Flutter and Firebase for Google I/O 2023, by [Google](https://github.com/flutter) and [Very Good Ventures](https://github.com/VGVentures). 92 | - [Flutter News Toolkit](https://github.com/flutter/news_toolkit): A news template application built in Flutter, by [Google](https://github.com/flutter) and [Very Good Ventures](https://github.com/VGVentures). 93 | - [Talk Stream](https://github.com/Yczar/talk-stream-backend): A chat application built using Flutter & Dart Frog, by [Yczar](https://github.com/Yczar). 94 | - [Rive Live](https://github.com/rive-app/rive_live): An app built by the [Rive team](https://rive.app/) to interact with their team during their [livestreams](https://www.youtube.com/watch?v=1Nilq-avNc4). 95 | - [Book Library System](https://github.com/YousefSalahKassem/book_library): A book library system built using Dart Frog including Postman collection by [Yousef Salah kassem](https://github.com/YousefSalahKassem). 96 | 97 | ### Apps 98 | 99 | - [Hespress](https://verygood.ventures/success-stories/hespress-case-study): A news app for Morocco’s first digital media outlet. 100 | 101 | [dart_frog_link_dark]: https://github.com/verygoodopensource/dart_frog#gh-dark-mode-only 102 | [dart_frog_link_light]: https://github.com/verygoodopensource/dart_frog#gh-light-mode-only 103 | [logo_black]: https://raw.githubusercontent.com/VeryGoodOpenSource/dart_frog/main/assets/dart_frog_logo_black.png#gh-light-mode-only 104 | [logo_white]: https://raw.githubusercontent.com/VeryGoodOpenSource/dart_frog/main/assets/dart_frog_logo_white.png#gh-dark-mode-only 105 | --------------------------------------------------------------------------------