이제 Google Fit API가 모듈화되었으므로 앱에 포함할 기능을 선택할 수 있습니다. 이러한 변경으로 인해 Google 피트니스를 사용 설정하는 앱의 메모리 요구사항이 크게 줄어들고 API에 액세스하는 방식이 영향을 받습니다. 코드를 업데이트하는 방법에 관한 자세한 내용은 피트니스 서비스에 연결을 참고하세요.
이제 피트니스 플랫폼에서 거리를 계산합니다. 데이터에 액세스하려면 com.google.distance.delta 데이터 유형을 사용합니다. 데이터 유형에 관한 자세한 내용은 피트니스 데이터 유형을 참고하세요.
이제 개발자는 세분화된 수면 데이터를 읽고 쓸 수 있습니다.
여기에는 얕은 수면, 깊은 수면, 렘수면 및 깨어 있는 활동이 포함됩니다. 이러한 세분화된 활동 유형이 FitnessActivities 열거 유형에 추가되었습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["필요한 정보가 없음","missingTheInformationINeed","thumb-down"],["너무 복잡함/단계 수가 너무 많음","tooComplicatedTooManySteps","thumb-down"],["오래됨","outOfDate","thumb-down"],["번역 문제","translationIssue","thumb-down"],["샘플/코드 문제","samplesCodeIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-07-25(UTC)"],[[["\u003cp\u003eThis page lists Google Fit API releases, including new features, bug fixes, and performance improvements.\u003c/p\u003e\n"],["\u003cp\u003eThe Google Fit API has undergone authorization changes, including new data types and scopes for heart rate and sleep data.\u003c/p\u003e\n"],["\u003cp\u003eStarting May 4, 2021, Google Fit authorization changes went into effect, along with the Google Fit Developer and User Data Policy, and app verification began.\u003c/p\u003e\n"],["\u003cp\u003eWriting to Health data types became generally available on August 2, 2021, with authorization consistent with other data types.\u003c/p\u003e\n"],["\u003cp\u003eThe Google Fit API introduced GoogleApi-based clients in November 2017, automatically managing service connections and offering new features like BLE device support and custom data type access.\u003c/p\u003e\n"]]],[],null,["This page contains information about Google Fit API releases.\nThe changelog lists releases by date and includes any new\nfeatures, bug fixes or significant performance improvements.\n\nAugust 2, 2021\n\nWriting to [Health data types](/fit/datatypes/health) is now generally available\nto developers. Authorization to access Health data types is consistent with all\nother data types. More details [here](/fit/datatypes#authorization_scopes).\n\nApril 27, 2021\n\nThere has been a small delay to enforcement of the [authorization changes](/fit/improvements#what_are_the_authorization_changes)\nannounced on October 10, 2020. The authorization changes will now be enforced\nfrom May 4, 2021.\n\nThe [Google Fit Developer and User Data Policy](/fit/policy) will also become\nenforceable on May 4, 2021. [App verification](/fit/improvements#strengthening_the_review_system_for_apps_using_google_fit)\n, as part of enforcement of the Fit developer policy, will start start in due\ncourse.\n\nOctober 19, 2020\n\nAs part of our ongoing efforts to enhance the security and privacy of Google Fit\nfor developers and users, we've made some changes to the Google Fit policies and\nAPIs:\n\n- There is a new [Google Fit Developer and User Data Policy](/fit/policy). Please review the policy, and if relevant, make appropriate changes to your apps and services.\n- Write-access will now only let an app read data it has written. To continue reading data written by *other apps* from the Google Fit platform, update your code to request read-access scopes for the relevant data types.\n- Heart rate data has its own scopes.\n- Sleep data has its own scopes and a new data type.\n- When working with the `SessionsClient`, you now need to specify what type of session your app needs to access, using the appropriate methods from `FitnessOptions`.\n\nThese changes to the API will be available for developers to use from 19 October\n2020. Enforcement will start from 27 April 2021.\n\nSee [here](/fit/improvements) for more details and instructions on these\nchanges.\n\nMarch 21, 2019\n\nThe Google Fit app now displays sleep sessions written to the Android API.\nLearn more about [writing](/fit/scenarios/write-sleep-data) and [reading](/fit/scenarios/read-sleep-data) sleep data.\n\nNovember 19, 2018\n\nThe following changes have been made to the Google Fit API:\n\n- Read requests for datatypes `com.google.location.sample` and `com.google.location.bounding_box` will only return data for the same app that has written the data.\n\nSeptember 26, 2018\n\nGoogle Play services fitness 16.0.0 provides access to two new data types and\ntheir respective aggregates:\n\n- [`TYPE_HEART_POINTS`](/android/reference/com/google/android/gms/fitness/data/DataType#TYPE_HEART_POINTS)\n- [`AGGREGATE_HEART_POINTS`](/android/reference/com/google/android/gms/fitness/data/DataType#AGGREGATE_HEART_POINTS)\n- [`TYPE_MOVE_MINUTES`](/android/reference/com/google/android/gms/fitness/data/DataType#TYPE_MOVE_MINUTES)\n- [`AGGREGATE_MOVE_MINUTES`](/android/reference/com/google/android/gms/fitness/data/DataType#AGGREGATE_MOVE_MINUTES)\n\nArtifacts released on maven.google.com\n\n- com.google.android.gms:play-services-fitness:16.0.0\n\nNovember 2017\n\n[Google Play services 11.6.0](//developer.android.com/google/play-services/index.html)\nintroduces the following new Google Fit features:\n\n- Updated the Fitness API for the new [`GoogleApi`](/android/reference/com/google/android/gms/common/api/GoogleApi)-based clients, which automatically manage connections to services and require less boilerplate code to use:\n - Added the [`BleClient`](/android/reference/com/google/android/gms/fitness/BleClient) class and the [`Fitness.getBleClient()`](/android/reference/com/google/android/gms/fitness/Fitness#getBleClient(android.app.Activity,%20com.google.android.gms.auth.api.signin.GoogleSignInAccount)) methods. `BleClient` provides the entry point for scanning, claiming, and using Bluetooth Low Energy devices in Google Fit.\n - Added the [`ConfigClient`](/android/reference/com/google/android/gms/fitness/ConfigClient) class and the [`Fitness.getConfigClient()`](/android/reference/com/google/android/gms/fitness/Fitness#getConfigClient(android.content.Context,%20com.google.android.gms.auth.api.signin.GoogleSignInAccount)) methods. `ConfigClient` provides the entry point for accessing custom data types and settings in Google Fit.\n - Added the [`GoalsClient`](/android/reference/com/google/android/gms/fitness/GoalsClient) class and the [`Fitness.getGoalsClient()`](/android/reference/com/google/android/gms/fitness/Fitness#getGoalsClient(android.content.Context,%20com.google.android.gms.auth.api.signin.GoogleSignInAccount)) methods. `GoalsClient` provides the entry point for reading fitness [`Goal`](/android/reference/com/google/android/gms/fitness/data/Goal)s created by users in Google Fit.\n - Added the [`HistoryClient`](/android/reference/com/google/android/gms/fitness/HistoryClient) class and the [`Fitness.getHistoryClient()`](/android/reference/com/google/android/gms/fitness/Fitness#getHistoryClient(android.content.Context,%20com.google.android.gms.auth.api.signin.GoogleSignInAccount)) methods. `HistoryClient` provides the entry point for inserting, deleting, and reading data in Google Fit.\n - Added the [`RecordingClient`](/android/reference/com/google/android/gms/fitness/RecordingClient) class and the [`Fitness.getRecordingClient()`](/android/reference/com/google/android/gms/fitness/Fitness#getRecordingClient(android.content.Context,%20com.google.android.gms.auth.api.signin.GoogleSignInAccount)) methods. `RecordingClient` provides the entry point for enabling low-power, always-on background collection of sensor data in Google Fit.\n - Added the [`SensorsClient`](/android/reference/com/google/android/gms/fitness/SensorsClient) class and the [`Fitness.getSensorsClient()`](/android/reference/com/google/android/gms/fitness/Fitness#getSensorsClient(android.content.Context,%20com.google.android.gms.auth.api.signin.GoogleSignInAccount)) methods. `SensorsClient` provides the entry point for exposing different sources of fitness data in local and connected devices, and delivering live events to listeners.\n - Added the [`SessionsClient`](/android/reference/com/google/android/gms/fitness/SessionsClient) class and the [`getSessionsClient`](/android/reference/com/google/android/gms/fitness/Fitness#getSessionsClient(android.content.Context,%20com.google.android.gms.auth.api.signin.GoogleSignInAccount)) methods. `SessionsClient` provides the entry point for creating and managing [`Session`](/android/reference/com/google/android/gms/fitness/data/Session)s of user activity in Google Fit.\n\nMay 2015\n\n[Google Play services 7.5](//developer.android.com/google/play-services/index.html)\nintroduces the following new Google Fit features:\n\n- Distance traveled and calories expended computations are available for subscription.\n - The Fit platform starts tracking distance and calorie data as soon as an app on the device subscribes to the data. For more information on how to subscribe to data types, see [Record Fitness Data](/fit/android/record).\n - The data is not available in real-time with the [Sensors API](/fit/android/sensors).\n- The Fit platform can now store exercise routine data, such as bicep curls and squats, with the `com.google.activity.exercise` data type. For more information on the exercises Fit can store, see [`WorkoutExercises`](/android-gcore/reference/com/google/android/gms/fitness/data/WorkoutExercises).\n\nApril 2015\n\n[Google Play services 7.3](//developer.android.com/google/play-services/index.html)\nintroduces the following new Google Fit features:\n\n- The Fit platform can now track nutrition data with the `com.google.fitness` data type.\n - The `com.google.calories.consumed` data type is now deprecated. Calorie consumption can be recorded with the `com.google.fitness.item` data type.\n - For more information on data types, see [Fitness Data Types](/fit/android/data-types).\n- Developers can retrieve daily aggregate step counts for use in areas such as Android Wear watch faces. For more information, see [Read daily total data](/fit/android/history#read_daily_total_data).\n\nMarch 2015\n\n[Google Play services 7.0](//developer.android.com/google/play-services/index.html)\nintroduces the following new Google Fit features:\n\n- The Google Fit API is now modularized so that you can choose which features to include in your app. This change significantly reduces the memory requirement for apps that enable Google Fit and affects how you access the APIs. For more information on how to update your code, see [Connect to the fitness service](/fit/android/get-started#step_5_connect_to_the_fitness_service).\n- The Fit platform now calculates distance. To access the data, use the `com.google.distance.delta` data type. For more information on data types, see [Fitness Data Types](/fit/android/data-types).\n- Developers can now read and write granular sleep data. This includes light sleep, deep sleep, REM, and awake activities. These granular activity types have been added to the [`FitnessActivities`](/android/reference/com/google/android/gms/fitness/FitnessActivities) enumerated type.\n - To insert sleep data, create a session of type [`FitnessActivities.SLEEP`](/android/reference/com/google/android/gms/fitness/FitnessActivities#SLEEP).\n - To detect granularity in your session, insert activity segments of types:\n - [`FitnessActivities.SLEEP_LIGHT`](/android/reference/com/google/android/gms/fitness/FitnessActivities#SLEEP_LIGHT)\n - [`FitnessActivities.SLEEP_DEEP`](/android/reference/com/google/android/gms/fitness/FitnessActivities#SLEEP_DEEP)\n - [`FitnessActivities.SLEEP_REM`](/android/reference/com/google/android/gms/fitness/FitnessActivities#SLEEP_REM)\n - [`FitnessActivities.SLEEP_AWAKE`](/android/reference/com/google/android/gms/fitness/FitnessActivities#SLEEP_AWAKE)\n - To read sleep data, query the sleep sessions for sleep activity segments as you would do with normal fitness activities."]]
