Add direct pub.dev package links

[glenn-jocher]

Summary

• add direct links to the pub.dev package in the main docs entry points
• update the install snippets from to

Testing

• not run (docs-only change)

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

📦 This PR refreshes the Flutter app documentation to point users to ultralytics_yolo version ^0.3.0 and adds direct package links for easier setup.

📊 Key Changes

• Updated the documented Flutter dependency version from ultralytics_yolo: ^0.2.0 to ultralytics_yolo: ^0.3.0.
• Added a direct link to the package on pub.dev for ultralytics_yolo in:
  • README.md
  • README.zh-CN.md
  • doc/install.md
  • doc/quickstart.md
• Kept both English and Chinese documentation aligned ✅

🎯 Purpose & Impact

• Makes installation instructions match the latest published Flutter plugin version 🚀
• Helps developers find the official package faster through a direct pub.dev package page link
• Reduces setup confusion and lowers the chance of users installing an older documented version
• Improves documentation consistency across the main README and setup guides for a smoother onboarding experience 📘

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/yolo-flutter-app 🚀 PR! This is an automated message to help streamline review; an Ultralytics engineer will assist you shortly. Please review the checklist below to support a smooth integration of your changes 📋

• ✅ Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
• ✅ Synchronize with Source: Confirm your PR is synchronized with the ultralytics/yolo-flutter-app main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
• ✅ Update Documentation: Update the relevant documentation for any new or modified features.
• ✅ Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
• ✅ Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
• ✅ Minimize Changes: Limit your changes to the minimum necessary for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

For more guidance, please refer to our Contributing Guide. Don't hesitate to leave a comment if you have any questions. Thank you for contributing to Ultralytics! 🚀

[UltralyticsAssistant]

🔍 PR Review

_{Made with ❤️ by Ultralytics Actions}

The version bump to ^0.3.0 is applied consistently, and adding package links is helpful. The only issues I found are documentation consistency concerns: the new raw URLs should use descriptive Markdown anchor text, and the Latest version comment in doc/install.md is likely to become misleading again.

💬 Posted 2 inline comments

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[UltralyticsAssistant]

🎉 Huge thanks for merging this, @glenn-jocher!

Updating the docs to ultralytics_yolo ^0.3.0, adding direct pub.dev package links, and keeping both English and Chinese guides aligned makes onboarding much smoother for everyone. It’s a great example of how small documentation improvements can create a big impact for the community.

As Confucius said, “The man who moves a mountain begins by carrying away small stones.” This PR reflects that perfectly, removing friction step by step and helping more developers get started with confidence.

Really appreciate the care and consistency behind this update 🙌