Flutter basic implementation for Classical Bluetooth.
Based on flutter_blue.
The first goal of this project is making an interface for Serial Port Protocol (HC-05 Adapter).
This plugin needs a lot of improvements, so I need your help. Any kind of collaboration will be awesome.
Click on the ⭐ above to support the project!
Only for Android.
If you have any problem with invoke-customs, verify this issue #14.
Demonstrates how to use the flutter_bluetooth_serial plugin.
For help getting started with Flutter, view our online documentation.
Add this to your package's pubspec.yaml file:
dependencies: flutter_bluetooth_serial: ^0.0.5
You can install packages from the command line:
$ flutter packages get
Alternatively, your editor might support
flutter packages get.
Check the docs for your editor to learn more.
Now in your Dart code, you can use:
|0.0.5||Mar 19, 2019|
|0.0.4||Dec 20, 2018|
|0.0.3||Nov 22, 2018|
|0.0.2||Sep 27, 2018|
|0.0.1||Aug 20, 2018|
Describes how popular the package is relative to other packages. [more]
Code health derived from static analysis. [more]
Reflects how tidy and up-to-date the package is. [more]
Weighted score of the above. [more]
We analyzed this package on Mar 19, 2019, and provided a score, details, and suggestions below. Analysis was completed with status completed using:
Detected platforms: Flutter
References Flutter, and has no conflicting libraries.
Document public APIs. (-0.17 points)
34 out of 35 API elements have no dartdoc comment.Providing good documentation for libraries, classes, functions, and other API elements improves code readability and helps developers find and use your API.
lib/flutter_bluetooth_serial.dart. (-0.50 points)
lib/flutter_bluetooth_serial.dart reported 1 hint:
line 35 col 26: The getter '_methodStream' isn't used.
The package description is too short. (-20 points)
Add more detail to the
description field of
pubspec.yaml. Use 60 to 180 characters to describe the package, what it does, and its target use case.
Package is pre-v0.1 release. (-10 points)
While nothing is inherently wrong with versions of
0.0.*, it might mean that the author is still experimenting with the general direction of the API.