Android Step Counters Without Google Fit: 2026 Guide
Disclosure: We build StepMelon. This guide explains the Android choices we think shoppers should verify, including how the current StepMelon Android app works. Check the current Google Play listing and permission screens before deciding whether any app fits your devices and preferences.
Do you need Google Fit to count steps on Android? Not necessarily. An app can read a device step sensor, read step records through Health Connect, or use an account-based service. Those are different technical paths, and an app may combine more than one of them.
Google Fit APIs in 2026: what is actually changing?
Google’s current developer guidance says the Google Fit APIs are supported until the end of 2026. It directs mobile-first step-tracking apps toward Health Connect and cloud integrations toward the Google Health API. Google also says developers can no longer register for the Google Fit APIs. See Google’s Fit migration guide and migration FAQ.
That is an API transition for developers. It is not evidence that every Google Fit consumer feature, device integration, or stored record shares one universal shutdown date. If existing Fit data matters to you, check Google’s current product help before changing apps or deleting anything.
Three ways an Android app can get a step count
| Path | What it means | What to verify |
|---|---|---|
| Direct device sensor | The app reads a phone or watch step-counter sensor. Device support varies, and Android may require Physical Activity permission. | Confirm the app supports your phone or watch, which permission it requests, and how it handles reboots or background restrictions. |
| Health Connect aggregation | With your permission, the app reads step records that compatible apps or devices write to Health Connect. Google documents that Health Connect can aggregate steps and apply source-priority rules. | Review connected apps, allowed data types, source priority, and the time range being read. |
| Account or cloud ecosystem | The app relies on a provider account or cloud API to sync activity across services. | Check account requirements, supported devices, retention, export, deletion, and what happens if the service changes. |
Health Connect is not the same product as Google Fit. Android’s step-data guidance describes how apps can read aggregated step totals and manage source priority. Google’s consumer help explains how to review Health Connect access and connected apps.
You do not need Health Connect for every possible Android pedometer. Whether you need it depends on how a particular app is built and whether you want data from multiple sources combined.
What “without Google Fit” should mean on a store listing
Before installing, look for a concrete answer to these questions:
- Does the app depend on Google Fit APIs? “Works without Google Fit” should describe an actual data path, not just marketing copy.
- Does it use Health Connect? If so, identify which data types it reads or writes and whether the feature is required or optional.
- Can it read a phone or watch sensor directly? Confirm device compatibility rather than assuming every Android device exposes the same sensor.
- Which permissions are requested? Android apps may request Physical Activity permission for step counting. Additional permissions should map to features you intend to use.
- Where does history come from? A live sensor count, Health Connect history, and a provider cloud account can produce different histories and update timing.
- What happens in the background? Battery and background behavior varies by Android version and manufacturer. No app can promise identical behavior on every phone.
- Can you export or delete your data? Check the current app controls and privacy policy rather than assuming that “standalone” means on-device-only.
How StepMelon currently works on Android
StepMelon’s current Android implementation does not use the Google Fit APIs. It combines Android step-counter sensors with Health Connect on compatible phones: the live service can read the phone’s TYPE_STEP_COUNTER sensor, while Health Connect supplies authorized aggregated history and related records. The Wear OS app reads the watch step-counter sensor and exchanges authorized step updates with the phone.
This means “without Google Fit” does not mean “without Android Health APIs.” StepMelon asks for the permissions needed by the data sources you enable. Review those prompts on your device.
StepMelon’s goals-first features include:
- minimum, target, and stretch step goals;
- configurable rest days;
- Android phone and Wear OS experiences;
- optional private Social features that require an account when you choose to use them.
Core step tracking and optional Social have different data flows. Read the current StepMelon privacy guide and the Google Play Data safety section before enabling features.
Setup checklist after installing a step counter
1. Review permissions
Grant Physical Activity or Health Connect access only when the requested access matches the feature you want. In Health Connect, you can review connected apps and data permissions later.
2. Confirm the selected source
If both a phone and watch record steps, check how the app selects or combines sources. Two apps can show different totals because of source priority, time windows, delayed writes, or their own reconciliation logic.
3. Carry or wear the counting device
A phone sensor cannot detect steps while the phone is left behind. A watch-based path depends on wearing a supported watch and granting the required activity permission.
4. Check background restrictions only when needed
Start with the device’s normal battery setting. If the count is zero or delayed, check whether Android has placed the app in a restricted or sleeping state. Less restrictive settings can use more battery.
If you already installed an app and its count is missing, delayed, or lower than expected, use the separate Android step-counter troubleshooting checklist. That guide covers permission, background, phone-source, and Wear OS checks without changing this page’s app-selection focus.
Common questions
Will switching away from Google Fit preserve my old history?
Do not assume that it will. History migration depends on the old service, the new app, supported export formats, and any Health Connect or cloud integration both sides currently provide. Verify and export important records before changing or deleting an account.
Is direct sensor counting more accurate than Health Connect?
Neither path is universally more accurate. A direct sensor reading, an aggregated Health Connect total, and a watch/phone combination can differ because they cover different devices, time windows, and source-priority rules. Compare results on your own supported setup.
Can a Wear OS app count without Google Fit?
It can if the app reads a supported watch sensor or another supported Android health source without using the Google Fit APIs. Confirm the watch app, permissions, phone companion requirements, and current device compatibility.
Does Health Connect keep everything only on the device?
Do not use that as a universal assumption. Health Connect manages Android health permissions and data on the device, but a connected app may separately sync data to its own account or cloud service. Review each connected app’s behavior and privacy policy.
The practical choice
Choose the data path before choosing the feature list:
- Pick a direct-sensor app when you want a focused count from one supported device.
- Pick a Health Connect-aware app when you want authorized data from compatible sources combined.
- Pick an account or cloud ecosystem when cross-service synchronization matters more than platform independence.
Then compare goal flexibility, rest-day behavior, phone and watch support, permissions, privacy controls, and current pricing. “Works without Google Fit” is useful only when the listing also explains what the app uses instead.
StepMelon is available on Google Play. Review the current listing for compatibility, permissions, plans, offers, and Data safety details.