[null,null,["最后更新时间 (UTC)：2025-07-25。"],[[["\u003cp\u003eGoogle Fit provides a central platform and APIs for storing, accessing, and sharing health and wellness data from various apps and devices.\u003c/p\u003e\n"],["\u003cp\u003eUsers have control over their data and must grant permission for apps to access it.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers can build apps that integrate with Google Fit using Android or REST APIs, supporting cross-platform functionality.\u003c/p\u003e\n"],["\u003cp\u003eData is organized using data sources, data types, data points, datasets, and sessions for efficient storage and retrieval.\u003c/p\u003e\n"],["\u003cp\u003eCompliance with the Google Fit Developer and User Data Policy and Terms and Conditions is essential when utilizing the platform.\u003c/p\u003e\n"]]],[],null,["# Platform Overview\n\nGoogle Fit is an open ecosystem. It lets developers upload health and wellness\ndata to a central repository where users can access their data from different\ndevices and apps in one location. They can still access their data if they\nupgrade to a new device.\n\nYour health and wellness app can store data from any wearable or sensor, and\naccess data created by other apps.\n| **Note:** The Google Fit app uses the Google Fit platform, which is included in Google Play services. Your app can use this platform without needing users to install the Google Fit app.\n\nRead the [Google Fit Developer and User Data Policy](/fit/policy) thoroughly and\nmake sure your app complies with it. Carefully review the [Google Fit Terms and\nConditions](/fit/terms) before using Google Fit. By using the API, you agree to\nthe Google Fit Terms and Conditions.\n\nComponents\n----------\n\nGoogle Fit consists of the following components: \n**Figure 1** : Platform overview.\n\nThe fitness store\n: A central repository that stores data from a variety of devices and apps. The\n fitness store is a cloud service that is transparent to clients.\n\nThe sensor framework\n: A set of high-level representations that make it easy to work with the fitness\n store. You use these representations with the Google Fit APIs.\n\nPermissions and user controls\n: A set of authorization scopes to request user permission to work with health\n and wellness data. Google Fit requires user consent to access health and\n wellness data.\n\nGoogle Fit APIs\n: Android and REST APIs to access the fitness store. You can create apps that\n support Google Fit on multiple platforms and devices, such as Android, iOS, and\n Web apps.\n\nThe fitness store\n-----------------\n\nThe fitness store is a cloud service that persists health and wellness data using Google's\ninfrastructure. Apps on different platforms and devices can store data and\naccess data created by other apps. Google Fit provides a set of APIs that make\nit easy to insert data and query the fitness store.\n\nThe sensor framework\n--------------------\n\nThe sensor framework defines high-level representations for sensors,\ndata types, data points, and sessions. These representations make it easy to\nwork with the fitness store on any platform.\n\nData Sources\n: Data sources represent sensors and consist of a name, the type of data\n collected, and other sensor details. A data source may represent a hardware\n sensor or a software sensor. You can define software sensors in your apps.\n\nData Types\n: Data types represent different kinds of health and wellness data, like step count or heart\n rate. Data types establish a schema through which different apps can understand\n each other's data. A data type consists of a name and an ordered list of fields,\n where each field represents a dimension. For example, a data type for location\n contains three fields (latitude, longitude, and accuracy), whereas a data type\n for weight contains only one field.\n\nData Points\n: Data points consist of a timestamped array of values for a data type, read\n from a data source. You use data points to record and insert health and wellness data in the\n fitness store, and to read raw data from a data source. Points that contain a\n start time represent a time range instead of an instantaneous reading.\n\nDatasets\n: Datasets represent a set of data points of the same type from a particular\n data source covering some time interval. You use datasets to insert data into\n the fitness store. Queries to read data from the fitness store also return\n datasets.\n\nSessions\n: Sessions represent a time interval during which users perform a fitness\n activity, such as a run, a bike ride, and so on. Sessions help organize data and\n perform detailed or aggregate queries on the fitness store for a fitness\n activity.\n\nPermissions and user controls\n-----------------------------\n\nGoogle Fit requires user consent before apps can read or store health and wellness data.\nGoogle Fit defines OAuth scopes that map to a number of permission groups with\nseparate read and write privileges: activity, body, location, nutrition and\nhealth-related data types (health-related data types are grouped with finer\ngranularity). Each permission group grants apps access to a set of data types.\nApps specify one or more of these scopes to work with health and wellness data, and Google\nFit requests the corresponding permissions from the user.\n\nGoogle Fit APIs\n---------------\n\nGoogle Fit provides the following APIs:\n\n- [Android APIs](/fit/android) for Android apps.\n- [REST API](/fit/rest) for apps on any platform."]]
