A new Flutter plugin for ios health kit
Getting Started #
Add to pubspec.yaml: ios_health
Add to ios/Podfile: platform :ios, '10.0'
Open your iOS Xcode project (Runner.xcworkspace)
Capabilities: Enable HealthKit
Add: NSHealthUpdateUsageDescription, NSHealthShareUsageDescription.
- TODO: Describe initial release.
*Fixed a bug.
Demonstrates how to use the ios_health plugin.
Getting Started #
This project is a starting point for a Flutter application.
A few resources to get you started if this is your first Flutter project:
For help getting started with Flutter, view our online documentation, which offers tutorials, samples, guidance on mobile development, and a full API reference.
Use this package as a library
1. Depend on it
Add this to your package's pubspec.yaml file:
dependencies: ios_health: ^0.0.2
2. Install it
You can install packages from the command line:
$ flutter pub get
Alternatively, your editor might support
flutter pub get.
Check the docs for your editor to learn more.
3. Import it
Now in your Dart code, you can use:
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 Sep 20, 2019, and provided a score, details, and suggestions below. Analysis was completed with status completed using:
- Dart: 2.5.0
- pana: 0.12.21
- Flutter: 1.9.1+hotfix.2
Detected platforms: Flutter
References Flutter, and has no conflicting libraries.
lib/ios_health.dart. (-4.89 points)
lib/ios_health.dart reported 10 hints, including:
line 38 col 49: Name non-constant identifiers using lowerCamelCase.
line 38 col 66: Name non-constant identifiers using lowerCamelCase.
line 42 col 69: Name non-constant identifiers using lowerCamelCase.
line 42 col 86: Name non-constant identifiers using lowerCamelCase.
line 46 col 58: Name non-constant identifiers using lowerCamelCase.
flutter format to format
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.
The package description is too short. (-3 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.