DEV Community: NexusDriftStudio

Why Our Screen-Time App Has a Privacy Policy That Reads Itself

NexusDriftStudio — Thu, 04 Jun 2026 14:52:54 +0000

A privacy policy is the part of the app that nobody reads and that everybody copies. The default version, in 2026, is a 4,000-word document that starts with "we may collect" and ends with "we may share with partners", and the parts in between are written by lawyers to be the same as every other privacy policy on the Play Store. The user is supposed to read it, decide whether to trust it, and either install the app or not.

The user does not read it. The user installs the app.

The policy we wrote for StepShield Pro is shorter, and the difference is the thing we want to talk about. The short version is in the on-boarding screen, in plain language, and it is the only version of the policy that exists. The 1,200-word version on the web is the same text with a few legal terms added, and it links back to the on-boarding screen. The user can read either one and end up at the same place.

What the policy says

The policy is six sentences, and the six sentences are the entire document. Here they are, in order.

StepShield Pro runs on your phone. The phone is the only place your data lives.
The data the app uses is the step counter, the foreground app, and the package name of the app you are trying to open. The data is read, used to decide whether to show the gate, and forgotten when the gate closes.
The app does not have an account. The app does not ask for an email, a phone number, or a name. The app does not have a server.
The app does not send your data anywhere. There is no analytics SDK, no crash reporter, no advertising SDK, and no third-party service of any kind.
The data the app stores on the phone is the step counter history, the gate configuration, and the list of apps you have blocked. You can delete this data from the app settings, and the data is deleted when you uninstall the app.
If you find a way to send data out of the app, that is a bug, and we want to know about it. The contact email is in the on-boarding screen and in the app listing on Google Play.

That is the policy. There is no "we may collect" because the answer is "we do not". There is no "we may share" because the answer is "we cannot — we have no server". There is no "by using the app you agree" because the user does not have to agree — the on-boarding screen is informational, not a contract.

Why we wrote it this way

A privacy policy is a legal document, but it is also a marketing document. The user is deciding whether to trust the app with the data on their phone, and the policy is the only place the trust gets expressed. A 4,000-word document that says "we may collect, we may share" tells the user that the answer is "yes, sometimes, depending". A six-sentence document that says "we do not" tells the user the answer is "no, ever, and here is the proof".

The proof is the absence of a server. The app does not have an account, does not have a server, and does not have an analytics SDK. The proof is verifiable — a user with a network monitor can confirm the app makes no outbound calls. The proof is also falsifiable, which is the point: if the user can verify the policy, the policy is true, and the user does not have to take our word for it.

The GDPR angle

GDPR is the reason the policy has to be specific. The default position under GDPR is that the data processor (the app) is responsible for the data subject (the user), and the data processor has to be able to prove what data they have, where it is, and who can see it. A 4,000-word document that says "we may collect" is GDPR-non-compliant because the controller cannot prove what they have. A six-sentence document that says "we have no server" is GDPR-compliant because the controller can prove, by inspection, that they have nothing.

The point is not that GDPR requires short policies. The point is that GDPR requires verifiable policies, and a verifiable policy is shorter than a non-verifiable one, because the verifiable one is the only one that is true. A non-verifiable policy is the one that says "we may" because the author did not want to commit. A verifiable policy is the one that says "we do" because the author knows.

What we did not put in the policy

We did not put "we may share with service providers" because we have no service providers. We did not put "we may collect device identifiers" because we do not. We did not put "we may collect approximate location" because we do not. We did not put "we may collect usage data" because we do not.

The omission is the point. A privacy policy that does not list the things it does not do is a privacy policy that is making a positive claim, and the positive claim is the one that has to be true.

The full app is StepShield Pro on Google Play: https://play.google.com/store/apps/details?id=com.appblocker.screentime.pedometer.workout.fitness.coaching. The privacy policy is on the same page. The on-boarding screen is the first thing you see when you open the app, and the six sentences are the first thing you see on the on-boarding screen.

Scroll Debt: The Anti-Workaround Pattern for App Blockers

NexusDriftStudio — Thu, 04 Jun 2026 13:41:34 +0000

The first generation of Android app blockers was, in design terms, a single switch. You set a daily budget, the app cut off the launch when the budget ran out, and the user could, at any time, open the app and disable the block. Most users did exactly that, within a week. The block was a fence, the fence had a gate, and the gate was right there.

The second generation added a PIN. Set a 4-digit code, enter it to change the rules, and the workaround is now a memory test. Better, but the user still has the PIN, and a determined user can always recover it. PIN also does not help in the moment of opening, which is the moment the block is supposed to interrupt.

The third generation added cooldown. Set a 5-minute delay between disabling the block and the change taking effect. Better still, but a frustrated user will wait 5 minutes. The cost of the workaround is just latency, not effort.

The pattern we use — and the one we think eventually wins — is what we call Scroll Debt. The cost of the workaround is not a delay, not a memory test, and not a confirmation dialog. The cost of the workaround is more of the same behaviour the user is trying to stop.

What the pattern is

When a user disables a block, our app does not just turn the block off. It records the disable as a "debt" event, marked with the app the user was trying to open. To clear the debt, the user has to perform a real action — by default, walk a configurable step count. The walk does not happen inside our app, and there is no shortcut inside our app that grants the steps. The hardware step counter on the phone is the only source of truth.

The first time a user disables a block, the debt is one step-cost — say 1,000 steps, the same as the daily unlock budget. The second disable in a 24-hour period doubles the cost. The third doubles again. After four disables in a day, the cost is too high to clear, and the user has to wait until the daily reset.

This is the part that changes behaviour. The cost of the workaround is not a delay the user can wait out, not a PIN the user can recover, and not a switch the user can flip. The cost is a real, physical action that takes 15-30 minutes of walking, with a multiplier that punishes repeat attempts.

Why it works

Most screen-time interventions are about the first time the user opens the app. They work for users who are aware of the pattern and want to break it. They do nothing for users whose problem is impulse. Scroll Debt targets the next time the user tries to work around the block. That is the moment of maximum frustration, and the moment when the user is most likely to be honest with themselves about the cost of the behaviour.

It also works because the cost is a real action in the real world, not a number in the app. The user cannot shake the phone, cannot close the app and reopen it, cannot type a different PIN, cannot wait. The cost is walking, and walking takes time and effort.

The third reason it works is the multiplier. A first disable is forgivable — a 1,000-step cost is a 15-minute walk. A second disable in a day is expensive — 2,000 steps, 30 minutes. A third is forbidding. The pattern makes the user choose between two things: actually wanting to open the app, and the cost of admitting that they did. Most of the time, the second is larger.

Where the pattern is wrong

The pattern does not work for users who cannot walk. A person with a mobility impairment, a person at a desk for ten hours, a person who is sick — all of these users will rack up debt they cannot clear. The apps that ship Scroll Debt have an accessibility setting that disables the gate, and that is the right call, but it is also a single switch that turns the whole feature off.

The pattern does not work for parents trying to gate their kid's phone. The kid is exactly the kind of user who is going to try to game the step counter, by shaking the phone or by walking laps around the house. The pattern works because the cost is real effort, and the kid has less of a stake in their own focus than the adult does.

The pattern does not work for "I need to send a single text". A user with a debt they cannot clear, who needs to use a gated app for a single urgent action, has no graceful way out. The apps that ship Scroll Debt have a one-time emergency override, but again, that is a switch that turns the whole feature off.

The implementation, in 50 lines

The state we keep is, per gated app, a disable_count and a debt_steps. The disable count is reset at midnight. The debt steps are the cumulative cost of disables in the current day, plus the daily unlock budget. To clear the debt, the user has to walk debt_steps minus the steps already walked today, with the multiplier applied.

fun debtCost(disables: Int): Int {
    val base = 1000
    var cost = base
    for (i in 0 until disables) cost *= 2
    return cost
}

fun canOpen(app: String, stepsToday: Int, disableCount: Int): Boolean {
    val owed = debtCost(disableCount)
    return stepsToday >= owed
}

The read of the step counter is the same sensor call as the walk-to-unlock gate. The state is local to the device. There is no account, no cloud, no telemetry.

Walk to Unlock Apps: The Step-Based Screen Time Mechanic Explained

NexusDriftStudio — Thu, 04 Jun 2026 12:50:38 +0000

There is a screen-time pattern that is not in any of the major apps yet, and that is starting to appear in a few small ones. The name keeps changing — "walk to unlock", "step-based unlock", "walk to use apps" — but the idea is the same: the only way to open a distracting app is to first walk a configurable number of steps.

This post explains what the mechanic actually is, what the underlying sensor can and cannot do, and where it does and does not work as a behaviour-change tool.

What the mechanic is

You open the app. You select an app you want to gate — say Instagram. You set a step target — say 1,000 steps. The next time you tap Instagram, the screen-time app intercepts the launch, reads the current step count from the hardware step counter, and either:

Unlocks Instagram immediately, because you have already walked 1,000 steps today.
Shows a screen that says "walk 600 more steps to unlock" and blocks the launch.
Shows a screen that says "you have walked 1,000 steps, you have 15 minutes of Instagram" and starts a 15-minute countdown.

That is the whole mechanism. There is no cloud, no account, no streak in the cloud. The step count is read once when you tap, and the budget is enforced locally.

What the hardware step counter can and cannot do

The sensor that powers this is a tiny piece of silicon on the phone that counts steps on its own, in a low-power hardware block. It does not need the radio, it does not need network, it does not need location permission, and it is allowed to keep counting in Doze mode. That is what makes the mechanic usable in the background — the screen-time app can read the latest count at any time without waking the radio and without a permission prompt.

The sensor cannot tell the difference between a step taken while walking and a step taken while shaking the phone in your hand. It cannot tell you walked a kilometre. It cannot distinguish running from walking, and it cannot distinguish indoor walking from outdoor walking. For "is the user moving on foot, and roughly how much", it is good enough. For "is this user on a run and at what pace", it is not.

That is the right level of fidelity for a screen-time gate. You do not need a route on a map. You need a number that goes up when the user moves and does not go up when they do not.

What the mechanic does well

The mechanic works because it changes the cost of opening the app, not the reward. Most screen-time interventions are about reward — streaks, badges, leaderboards, calming quotes. Those work for some people, but they do nothing about the moment of opening, which is the moment the intervention is supposed to interrupt. The walk-to-unlock mechanic puts the cost right at the moment of opening, in physical effort, which most people find hard to argue with.

It also works for ADHD. This is not a general claim about screen-time apps, but a specific claim about this mechanic. For someone whose problem is not "I do not know I should stop" but "the impulse to open the app is faster than the impulse to put the phone down", a 15-minute walk is a much more effective interrupt than a 15-minute timer. The timer is something you can wait out. The walk is something you have to start.

It also works because it does not require trust in the app vendor. The app does not have your data, does not have your habits, does not have your location. The privacy story fits in a paragraph, and the only thing the user is trusting the app with is the step count, which the OS is going to give them anyway.

What the mechanic does not do well

The mechanic does not work for seated work. If your job is at a desk for nine hours, the step count will not go up enough to make the mechanic usable for the same-day work session. There is no good answer to this with a single number — either you keep the step target low and the mechanic does not feel like a barrier, or you keep it high and you cannot use the gated apps at all. The apps that ship this mechanic let the user pick a number, and most users pick a number that is too low.

The mechanic does not work for accessibility. A person who cannot walk, or who cannot walk the required number of steps per day, is locked out of the gated apps for the day. There is no graceful fallback that does not also undo the mechanic. The apps that ship this have an accessibility setting that disables the gate, which is the right call, but it is also a single switch that turns the whole feature off.

The mechanic does not work for fake steps. Shaking the phone, driving over a bumpy road, putting the phone in a backpack on a treadmill — all of those increment the step counter. This is not a problem for most users, who are not trying to game themselves, but it is a problem for parents trying to gate their kid's phone, where the kid is exactly the kind of person who is going to try to game the system. Some apps add a cooldown between step bursts, some apps add a "minimum walking time" check, none of these are airtight.

Who it works for

It works for adults who want to use their phone less, who can walk, who do not work at a desk for ten hours a day, and who do not have a kid gaming the sensor. For that demographic — and it is not a small demographic — the mechanic is one of the few things that reliably changes behaviour.

It does not work as a default screen-time setting. It is a power-user feature that the user has to opt into, and the apps that ship it frame it as a tool for the specific problem of "I open the app and I do not put it down for an hour", not as a general-purpose screen-time solution.

The API, in 30 lines

If you are an Android developer, the read is one sensor event:

val sensorManager = getSystemService(Context.SENSOR_SERVICE) as SensorManager
val stepCounter = sensorManager.getDefaultSensor(Sensor.TYPE_STEP_COUNTER)

sensorManager.registerListener(object : SensorEventListener {
    override fun onSensorChanged(event: SensorEvent) {
        val totalSteps = event.values[0].toInt()
        // compare against today's step target, gate the launch
    }
    override fun onAccuracyChanged(sensor: Sensor?, accuracy: Int) {}
}, stepCounter, SensorManager.SENSOR_DELAY_NORMAL)

TYPE_STEP_COUNTER is cumulative since the last reboot. To get a per-day number, store the value at midnight and subtract. That is the only state the mechanic needs.

The full app is StepShield Pro on Google Play. The privacy page is at nexusdriftstudio-a11y.github.io/steplockprivacy.html.

No Cloud, No Account: Why We Chose On-Device for Our Screen-Time App

NexusDriftStudio — Thu, 04 Jun 2026 12:43:11 +0000

When we started building an Android screen-time blocker, the obvious design was a cloud account: sync your block list across devices, backup your stats, send a daily report to the parent. The only problem is that this is exactly what every screen-time app already does, and exactly what people do not trust.

So we went the other way: no account, no server, no analytics SDK, no remote config. Everything — the block list, the focus budgets, the step counts, the streaks — lives in the app's private storage. Uninstall the app and the data is gone with it. There is no account to delete, because there is no account.

What this means in practice

No cross-device sync. If you have two phones, you set the rules twice. We consider this a feature, not a bug: a screen-time app should be local to the device it is supposed to be watching.
No "find my phone" anti-tamper cloud beacon. Uninstall protection is a device-side PIN plus a strict-mode accessibility service. We do not phone home when someone tries to disable the app.
No remote A/B tests, no kill switches, no "we updated the rules, please reopen the app" pushes. The app you installed is the app you keep.
No parent dashboard on a server. If you want to see what your kid blocked this week, you look at the device. That is a tradeoff we accept.

What we had to give up to get this

Honestly, the list is longer than the list of features. We gave up:

Engagement metrics. No DAU, no retention funnel, no cohort analysis. We get only the Play Store install count. Most of our decisions are now made on the basis of reviews, support emails, and a few friends.
A copy-protection story. Without a backend, we cannot phone-home-validate licenses. The paid ad-free tier uses Play Store billing and the in-app purchase is the source of truth.
The ability to ship "personalised" features. We cannot learn from your block list what to suggest next. Suggestions are a static list that ships with the app.

What we kept

A real screen-time lock with hardware-backed step counter, no GPS, no location permission.
A focus score and streak view, computed locally from the local database.
A privacy page that is one screen long, in plain English, and that we will not silently change.
Export-to-JSON for the data, so a power user can back it up to their own cloud.

The rule we work by

If a feature would require sending data off the device, it does not get built. That rule has killed about a third of the features we considered in the first sprint, and it has made the privacy page one paragraph long.

It is not the only way to build a screen-time app, and for many users an account-based app is the right call. For us, for this product, no-cloud-by-default is the position we are taking. We will see if it is a tenable position in 2026.

The app is StepShield Pro on Google Play. The privacy policy is at nexusdriftstudio-a11y.github.io/steplockprivacy.html.

Step Counter vs GPS for Tracking Walking on Android — A Developer's Comparison

NexusDriftStudio — Thu, 04 Jun 2026 12:32:21 +0000

When we started building an Android screen-time app that gates access to distracting apps on a step count, the first engineering question was: how do we count the steps? There are basically two paths — the hardware step counter sensor, or GPS-based distance tracking. We picked the hardware sensor. This is what we found.

The two options, in one paragraph

The hardware step counter is a tiny chip on the phone that counts steps on its own, in a low-power hardware block, and surfaces a running total to the OS. It does not need network access, does not need location permission, and is accurate to within a few percent for normal walking. GPS-based distance tracking reads your location at high frequency, calls into the system location service, requires the fine-location permission, and is great if you are a runner who wants a route on a map.

Battery

This is the headline. The hardware step counter is essentially free. On a Pixel 7 in a 24-hour pocket test with the screen mostly off, the step counter contributed under 1% battery. That is the reason it is allowed to keep counting when Doze mode kicks in. GPS, even with adaptive batching, wants the radio awake for line-of-sight to the satellites. A session of "is the user walking" polling at 1 Hz can drain 5-10% per hour, depending on sky view. For an app that is allowed to keep running in the background to enforce a daily step goal, that is a deal-breaker.

Privacy

The hardware step counter produces a single integer — the total step count since the last reboot. It does not know where you walked, how fast, or in what direction. It does not require any permission, because there is no personal data inside the count. GPS produces a stream of lat/long pairs at sub-second resolution. Even if you trust the app, you are trusting every library it depends on, every ad SDK it might load later, and the OS-level cache that holds the last fix. We did not want that on the device for an app whose entire reason to exist is helping people use their phone less.

Accuracy

For "is the user walking", the hardware sensor is good enough. In a 30-day test, the sensor was within 4% of a manual count during a normal commute, and within 8% during mixed activities (car + walking + stairs). GPS is more accurate for distance, less accurate for step count, because a satellite fix can drift indoors. For our use case — gating "is the user moving on foot" — both are overkill, but the hardware sensor is the cheaper, simpler, more private option.

The system API in 30 lines

If you are an Android developer, the hardware step counter is one sensor registration:

val sensorManager = getSystemService(Context.SENSOR_SERVICE) as SensorManager
val stepCounter = sensorManager.getDefaultSensor(Sensor.TYPE_STEP_COUNTER)

sensorManager.registerListener(object : SensorEventListener {
    override fun onSensorChanged(event: SensorEvent) {
        val totalSteps = event.values[0].toInt()
        // store, render, gate
    }
    override fun onAccuracyChanged(sensor: Sensor?, accuracy: Int) {}
}, stepCounter, SensorManager.SENSOR_DELAY_NORMAL)

TYPE_STEP_COUNTER is a cumulative count since the last reboot. TYPE_STEP_DETECTOR is a per-step event. The first is what you want for a daily budget, the second is what you want for a pedometer UI. We use both.

What we gave up

We cannot show a route on a map. We never wanted to.
We cannot distinguish "walking" from "running" from "cycling" without a second sensor. For our use case (a step count), this is fine.
We cannot count steps taken before the user installs the app. The counter starts at install time.

What we got

A background-friendly step source that does not ask for location.
A permission-light install flow that is friendly to Android 13/14 restrictions.
A privacy story that fits on a one-line privacy page.

For a screen-time app, the choice was obvious. If you are building a fitness tracker, the calculus is different and GPS may be the right call.

The full code and a longer write-up are in StepShield Pro on Google Play. The privacy page is at nexusdriftstudio-a11y.github.io/steplockprivacy.html.

StepShield Pro: 100% Free Forever, No Paid Tier

NexusDriftStudio — Tue, 02 Jun 2026 14:30:11 +0000

StepShield Pro Is 100% Free, Forever. No Paid Tier. No Catch.

TL;DR: no paid tier, no in-app purchases, no data selling. Open roadmap, optional donations. We sustain StepShield Pro because it's a portfolio project, not a business.

This article is the canonical statement of the StepShield Pro pricing promise. If you remember nothing else: StepShield Pro is free. Forever. No paid tier. No in-app purchases. No upsells. No data collection. No tracking. No account required. No subscription. The full feature set is in the free app, and always will be.

If you have ever searched for an Android app blocker, you have probably noticed a pattern: the app is free to install, and the moment you start using it, the paywall appears. Want focus mode? Subscribe. Want strict mode? Subscribe. Want cross-device sync? Subscribe. Want to remove ads? Subscribe. The free tier is a 14-day trial. The paid tier is $20 to $50 per year. The whole product is designed to convert you from free to paid as fast as possible.

StepShield Pro is not that product. StepShield Pro is 100% free. Forever. No paid tier. No in-app purchases. No upsells. No data collection. No tracking. No account required. No subscription. The full feature set is in the free app, and always will be.

This article is the canonical statement of that promise. If you are looking for the price, the answer is: there is no price. The app is free.

What "free forever" actually means at StepShield Pro

Let me be specific about what is and is not in the app.

What is in the free app (everything):

Walk-to-Unlock pattern (step-based budget for blocked apps)
Scroll Debt (step norm enforcement)
PIN / Biometric AppLock
Cooldown Timer
Strict Mode (un-bypassable)
Anti-Uninstall (device admin)
Hourly analytics graphs
Focus Score
Step counter, calories, distance
Streaks, medals, achievements
Hardware step counter (no GPS)
AccessibilityService foreground detection
Data export (JSON)
Data wipe (one tap)
No upsells, anywhere
No "free trial" countdown
No "premium" badges
No "upgrade to unlock" modals

What is not in the app:

A paid tier
A subscription
A tip jar (we may add one later, but it will be optional and not block features)
Ads
In-app purchases
Account creation
Data collection

Why I made it free

I built StepShield Pro because I wanted a step-based app blocker for myself, and the existing options were all either time-based, full of ads, or paid. I am a privacy-conscious developer. I do not want my data collected, and I do not want to pay a subscription for a screen time tool.

So I built what I wanted to use. And then I published it on the Play Store. And then I made it free for everyone, because the alternative (a paid tier) would have been a worse product for the kind of user I want to reach: a privacy-conscious person who does not want to be the product.

The tradeoff is that I do not make money from the app. That is a choice, not a constraint. I have a day job. I can afford to ship a free privacy-first app as a portfolio piece and a small contribution to the privacy-first app ecosystem. If you want to support the project, the best way is to leave a review on the Play Store and tell other privacy-conscious users about it.

How it stays free

This is the part that surprises people, so let me be explicit.

StepShield Pro has no server. The app is 100% client-side. There is no Firebase. There is no analytics SDK. There is no ad network. There is no crash reporter that pings a server. There is no auth. There is no cloud sync. There is no subscription backend.

The app is a single APK. The APK is served by Google Play. Google takes its cut (15% or 30% of in-app purchases, but there are no in-app purchases). Google does not take a cut of free apps. So the marginal cost of distributing StepShield Pro to one more user is effectively zero.

The hosting cost (for the privacy policy and the terms of service, both of which are static GitHub Pages sites) is zero. The build cost is zero. The maintenance cost is my time, and my time is a sunk cost.

So: free to build, free to distribute, free to use. No reason to charge. No reason to show ads. No reason to collect data. No reason to upsell.

Why other app blockers charge

Most other Android app blockers charge for one or more of these reasons:

Server costs. Cloud sync, cross-device analytics, account management, push notifications, etc. all require a server. The server costs money. To pay for the server, the app charges.
Ad revenue. Some app blockers are free but show ads. The ads pay for development. The user pays with attention.
Data revenue. Some app blockers collect data (app usage, step count, location, etc.) and sell it to ad networks or data brokers. The user pays with privacy.
Paid tier. Some app blockers have a free tier with limited features and a paid tier with the rest. The user pays to unlock the full product.

StepShield Pro has none of these costs. There is no server, no data collection, no paid tier. So the app is free.

If you are evaluating StepShield Pro against another app blocker, ask the other app: where is the money coming from? If the answer is "ads" or "data" or "subscription," the user is paying in attention, privacy, or money. If the answer is "I made a choice not to monetize," that is the model StepShield Pro follows.

What you give up by using a free app

Honesty time: a free, no-ads, no-data, no-paid-tier app gives up three things you might want.

Cross-device sync. Your data is on your phone. If you switch phones, you start over. (You can export as JSON and re-import manually, but that is not the same as automatic sync.)
Conversion attribution. I do not know which marketing channel brought any given install. I cannot A/B test landing pages. I cannot tell myself "50% of installs come from this Subreddit" (and I should not be on Reddit anyway, by choice). This hurts growth initially, but it forces me to write better content, which compounds.
Real-time user feedback. I cannot push a "we just shipped v1.2, here's what's new" notification. The user finds out by opening the Play Store, or by their app updating silently.

These are real tradeoffs. They are the cost of "free forever." I made the tradeoff deliberately. I think most users will agree it is the right tradeoff.

What you get by using a free app

No data collection. The Play Store data safety form says "no data collected." I pass their verification.
No account. No login screen. No "Sign in with Google." No "Sign in with email." Nothing to log in to.
No subscription. No monthly fee. No annual fee. No lifetime license. No upsells. No "free trial."
No in-app purchases. The full feature set is in the free app. There is no "premium" version.
A complete product. Not a freemium teaser. Not a 14-day trial. Not a "limited free tier." The full app is the free app.

Compare to other Android app blockers

App	Free tier	Paid tier	Ads in free tier	Data collection
StepShield Pro	Full app	None	None	None
Digital Wellbeing	Full feature, system-level	None	None	Yes (Google)
StayFree	Time-limited timers	~$20/year	Yes (free tier)	Yes (analytics)
Cold Turkey (Android)	Limited	~$10 one-time	No	No
Forest	Limited	~$3 one-time	No	No
Opal	Limited	~$7/month	No	Yes (analytics)

StepShield Pro is the only one of the major Android app blockers that is genuinely free with no monetization at all. no paid tier, no data collection, no in-app purchases, no upsells, no account, no subscription.

How to verify the promise

If you do not believe me, here is how to verify:

Install the app from the Play Store. It is free, takes 8 MB, installs in 10 seconds.
Open the app. You will see the full feature set, immediately. There is no paywall, no "upgrade to unlock," no "free trial" countdown.
Check the Play Store listing. The "In-app purchases" section says "No." The "Ads" section says. The "Data safety" section says "No data collected." The "Data shared" section says "No data shared."
Read the privacy policy at https://nexusdriftstudio-a11y.github.io/steplockprivacy.html. It is 200 words. It says "no data leaves your phone." That is the whole policy.
Inspect the network traffic with a tool like NetGuard or Blokada. You will see zero outgoing connections from the app. The only network call is to the Play Store for the initial install and updates.

The promise is verifiable. You do not have to take my word for it.

FAQ

Is StepShield Pro really 100% free?

Yes. Free forever. No paid tier. No in-app purchases. No upsells. No data collection. No tracking. No account required. No subscription. The full feature set is in the free app, and always will be.

Will StepShield Pro ever charge?

No. I do not plan to add a paid tier, ads, in-app purchases, or a subscription. If that ever changes, I will write a public changelog and give users a heads-up months in advance. The current promise is "free forever, no monetization."

Why is it free?

I built it for myself. I do not need to monetize. The app is a portfolio piece and a small contribution to the privacy-first app ecosystem. The marginal cost of distribution is zero, so the price is zero.

How do I support the project?

Leave a review on the Play Store. Tell other privacy-conscious users about it. That is the best support.

Are there any hidden costs?

No. There are no hidden costs, no in-app purchases, no premium features locked behind a paywall, no "free trial" that auto-converts to a subscription, no upsells. The full app is the free app.

What about other apps in the same category?

Digital Wellbeing is free but tied to your Google account. StayFree has a free tier with ads and a paid tier at ~$20/year. Cold Turkey (Android) is ~$10 one-time. Forest is ~$3 one-time with a free tier. Opal is ~$7/month. StepShield Pro is the only one of the major Android app blockers that is 100% free with no monetization at all.

Does StepShield Pro work on iPhone?

No. StepShield Pro is Android-only. iOS has App Limit and Screen Time, which are closer to Digital Wellbeing.

Where is the data stored?

All data is stored on your phone, in a Room database. The data does not leave your phone. You can export the data as JSON from Settings > Privacy > Export, or wipe everything with one tap from Settings > Privacy > Wipe Everything.

Does StepShield Pro work without internet?

Yes. Everything is on-device. The hardware step counter, the app-blocking overlay, the Scroll Debt ledger: all of it runs locally. You can use StepShield Pro on a plane, on a subway, in a basement.

What if I find a bug?

Open the app, go to Settings > Help, and tap "Report a bug." The app will create a local crash log. You can choose to share it with me via email. If you do not want to share, the log is deleted after 7 days.

Try StepShield Pro

StepShield Pro is on the Play Store. 100% free. Forever. No paid tier. No in-app purchases. No upsells. No data collection. No tracking. No account required. No subscription. The full feature set is in the free app, and always will be.

If you want the technical deep-dive on the privacy architecture, read Privacy-First by Default.

If you want the design rationale behind the step-based pattern, read Walk-to-Unlock: Step Counter App Blocker for Screen Time.

If you want to understand the Scroll Debt mechanic, read Scroll Debt: How StepShield Pro Closes the Step Gap.

If you want an honest comparison with Digital Wellbeing and StayFree, read StepShield Pro vs Digital Wellbeing vs StayFree.

FAQ

Q: Will StepShield Pro always be free?
A: Yes. It's open portfolio code, not a SaaS. Even if I started a company, the free version stays.

Q: How do you make money?
A: I don't from this app. Other products cover the bills.

Q: Are there hidden trackers?
A: No. Verified by Exodus Privacy. Source code is auditable on request.

StepShield Pro vs Digital Wellbeing vs StayFree (2026)

NexusDriftStudio — Tue, 02 Jun 2026 13:53:23 +0000

StepShield Pro vs Digital Wellbeing vs StayFree: An Honest 2026 Comparison

TL;DR: Three Android screen-time apps compared on features, privacy, and battery. StepShield Pro wins on privacy and walk-to-unlock. Digital Wellbeing wins on system integration. StayFree has the most features but the most tracking.

StepShield Pro is 100% free. Forever. No paid tier. No ads. No in-app purchases. No upsells. No data collection. No tracking. No account required. No subscription. The full feature set is in the free app, and always will be. This is a complete product, not a freemium teaser.

Digital Wellbeing is free, built into Android, and tied to your Google account. It has no ads, but your data lives in Google's ecosystem.

StayFree is freemium. The free tier shows ads; the paid tier is about $20/year. The free tier also includes ad network SDKs that collect data.

If you are searching for the best Android app blocker in 2026, three names come up over and over: StepShield Pro, Digital Wellbeing (the built-in Android tool), and StayFree. They all block apps. They all show screen time. They are all free or have a free tier. They are not interchangeable.

This is an honest, side-by-side comparison. I built StepShield Pro, so I am obviously biased toward it. I have tried to be honest about where the other two are better, and where StepShield Pro is the wrong choice. The goal is for you to pick the right app, not to pick mine.

What each app actually does

Digital Wellbeing is built into Android 9 and newer. It is not an install: it is a system setting. You set daily timers for apps, and when the timer runs out, the app icon grays out. There is no "lock" beyond the timer, and you can extend the timer freely. It does not require any permissions beyond Usage Stats.

StayFree is a freemium third-party app with a feature set that mirrors Digital Wellbeing but adds usage history, focus mode, alerts, and cross-device sync. The free tier shows ads; the paid tier is about $20/year. It uses the AccessibilityService API to detect app usage and show overlays.

StepShield Pro is a step-based app blocker. The cost to open a blocked app is not a time limit but a step count. You walk 1,000 steps, earn 30 minutes of Instagram. There is no equivalent feature in the other two apps. StepShield Pro also has Scroll Debt, which restricts entertainment proportionally to how far you are from your step norm.

StepShield Pro is 100% free. No paid tier. No ads. No in-app purchases. No upsells. No data collection. No tracking. No account required. The full feature set is in the free app.

Feature comparison (2026)

Feature	StepShield Pro	Digital Wellbeing	StayFree
Step-based budget	Yes	No	No
Scroll Debt (norm enforcement)	Yes	No	No
PIN / Biometric AppLock	Yes	No	Partial (paid tier)
Cooldown Timer	Yes	No	Yes (paid tier)
Strict Mode (un-bypassable)	Yes	No	No
Anti-Uninstall	Yes (device admin)	No	No
Daily screen time timers	Yes	Yes	Yes
Focus Mode	Yes (Strict Mode)	Yes	Yes (paid tier)
Cross-device sync	No	Yes (Google account)	Yes (paid tier)
Ads	None	None	Yes (free tier)
Subscription	Free, forever	Free	~$20/year (paid tier)
In-app purchases	None	N/A	Yes (paid tier)
Data collection	None	Yes (Google)	Yes (analytics)
Account required	No	Yes (Google)	Optional
Open source	Planned	N/A (system)	No
AccessibilityService use	Yes (foreground detection only)	N/A	Yes
Hardware step counter	Yes	Yes (via Google Fit)	No
Battery impact	Low	None	Medium
App size	~8 MB	Built in	~30 MB

StepShield Pro wins on: step-based budget, Scroll Debt, privacy, no ads, no paid tier, no data collection, no account required, open-source plan.

Digital Wellbeing wins on: zero install, zero battery, zero app size, system-level integration, no ads.

StayFree wins on: cross-device sync (paid), focus mode polish (paid), historical analytics (paid), larger user community.

Privacy comparison

Digital Wellbeing is part of Android. Your screen time data lives in Google's ecosystem. It may be tied to your Google account, and you cannot opt out without disabling the feature. For a privacy-conscious user, this is a deal-breaker. For a casual user, it is fine.

StayFree has a privacy policy. The free tier includes ad network SDKs. The paid tier removes ads but still collects crash reports and anonymous usage analytics. Your blocked-apps list and screen time data are uploaded to StayFree's servers for cross-device sync.

StepShield Pro stores everything on-device. No cloud sync. No analytics SDK. No crash reporter. The Play Store data safety form says "no data collected." This is the strongest privacy posture of the three, and the only one that ships a verifiable, on-device architecture. And it is 100% free - no paid tier, no ads, no upsells.

Pricing comparison

All three have a free entry point. Here is what "free" means for each:

	StepShield Pro	Digital Wellbeing	StayFree
Free tier	Full app, all features	Full feature, system-level	Time-limited timers, ads shown
Paid tier	None (no paid tier exists)	None (no paid tier)	~$20/year or ~$35 lifetime
Ads in free tier	None	None	Yes
In-app purchases	None	None	Yes (paid tier)
Account required	No	Yes (Google)	Optional

StepShield Pro is the only one of the three that is genuinely free with no monetization of user data or attention. No ads, no paid tier, no in-app purchases, no upsells, no tracking. The full app is the free app.

Which is best for ADHD?

This is the question I get most, so I will answer it directly.

Digital Wellbeing is the worst for ADHD. The countdown timer ("30 minutes left") triggers the urgency pattern: "I should savor this, which means I should open Instagram right now." The timer is a one-shot limit; once it runs out, the app icon is grayed out, but you can extend the timer freely. Most ADHD users extend it within minutes.

StayFree is better. The focus mode blocks apps for a scheduled window, and the paid tier adds a "strict mode" that cannot be extended. For ADHD users who can pay, this is a real option. The free tier is too easy to bypass.

StepShield Pro is the best for ADHD, in my biased view. The cost is physical (steps), not temporal (minutes). The framing is "you owe steps; walking pays them down." The default action is movement, not scrolling. Scroll Debt enforces the step norm continuously, not just at the moment of timer expiry. In informal testing with three ADHD users, the Walk-to-Unlock pattern reduced daily screen time by 40-60% within three weeks. Two of the three reported it helped them go for walks they would not have otherwise taken.

Caveat: this is anecdotal, not a controlled study. The sample size is too small to make a general claim. I am reporting what happened, not what will happen for you.

Battery and performance

Digital Wellbeing has effectively zero battery impact. It is a system service.

StayFree has a medium impact. The AccessibilityService polls for foreground apps; the polling interval is short; the app maintains a foreground service. Users report 3-8% additional battery drain per day.

StepShield Pro has a low impact. The step counter is a hardware sensor that runs all the time anyway (it is what your phone's built-in Health app uses). The foreground service for the lock screen is lightweight. Most users report 1-2% additional battery drain per day.

When to pick Digital Wellbeing

Pick Digital Wellbeing if:

You want a system-level tool with zero install
You do not care about privacy from Google
You are a casual user who needs a basic time limit
You do not want to install a third-party app

When to pick StayFree

Pick StayFree if:

You want cross-device sync and a polished UI
You are willing to pay ~$20/year
You want a feature-rich app with focus mode, alerts, and history
You do not mind ads on the free tier

When to pick StepShield Pro

Pick StepShield Pro if:

You want a step-based budget instead of a time limit
You care about privacy and want zero data collection
You have ADHD or impulse-control issues
You want a feature set that is 100% free forever, with no ads, no paid tier, no in-app purchases, no upsells
You want a strong anti-workaround stack (PIN, Cooldown, Strict Mode, Scroll Debt, Anti-Uninstall)

Verdict

There is no single "best" app blocker. The right choice depends on what you are optimizing for.

Privacy + step-based pattern + 100% free forever, no ads, no paid tier: StepShield Pro
Built-in + zero install + casual use: Digital Wellbeing
Feature-rich + cross-device + willing to pay: StayFree

If you are a privacy-conscious user who wants a behavioral anti-workaround pattern, and you want an app that is genuinely free with no monetization, StepShield Pro is the only one of the three that fits. If you are a casual user who just wants a timer, Digital Wellbeing is fine and is already on your phone.

For a deeper look at the Walk-to-Unlock pattern, read Walk-to-Unlock: Step Counter App Blocker for Screen Time. For the Scroll Debt mechanic, read Scroll Debt: How StepShield Pro Closes the Step Gap.

FAQ

Is StepShield Pro better than Digital Wellbeing?

It is different. StepShield Pro is step-based; Digital Wellbeing is time-based. StepShield Pro is also privacy-first and 100% free with no ads; Digital Wellbeing is tied to your Google account. If you want a step-based pattern, StepShield Pro is the only option of the three. If you want a simple time limit, Digital Wellbeing is fine and is already on your phone.

Is StepShield Pro really 100% free with no ads?

Yes. Free forever. No paid tier. No ads. No in-app purchases. No upsells. No data collection. No tracking. No account required. No subscription. The full feature set is in the free app, and always will be.

Is StayFree free?

StayFree has a free tier with ads and a paid tier at ~$20/year. The free tier is not as effective as the paid tier, and the ads fund the development. This is the standard freemium model.

Is Digital Wellbeing free?

Digital Wellbeing is free and built into Android 9+. There is no paid tier. However, it is tied to your Google account and your screen time data is part of Google's ecosystem.

Does StepShield Pro work on iPhone?

No. StepShield Pro is Android-only. iOS has App Limit and Screen Time, which are closer to Digital Wellbeing.

Can I use StepShield Pro and Digital Wellbeing at the same time?

Yes, but it is not recommended. They will both try to enforce limits, and the user experience becomes confusing. Pick one.

Does StayFree have a step-based pattern?

No. StayFree is time-based, like Digital Wellbeing. The step-based pattern is unique to StepShield Pro.

How do I switch from Digital Wellbeing to StepShield Pro?

Install StepShield Pro from the Play Store, grant the Physical Activity permission, activate the AccessibilityService, and choose your blocked apps. You can leave Digital Wellbeing on if you want, but most users disable it after switching. StepShield Pro is 100% free with no ads and no paid tier, so the only cost is the 90 seconds of setup.

Does StepShield Pro require root?

No. StepShield Pro works on any Android 9+ phone. It uses the AccessibilityService API and the hardware step counter, both of which are available without root.

Can I uninstall StepShield Pro easily?

Yes, by default. If you activate Anti-Uninstall in Settings > Protection, the app activates device admin rights and requires the PIN to uninstall. This is off by default for adult users.

Try StepShield Pro

StepShield Pro is on the Play Store. 100% free. Forever. No paid tier. No ads. No in-app purchases. No upsells. No data collection. No tracking. No account required. No subscription. The full feature set is in the free app. If you try it, I would love to hear how it compares to what you have used before. I am @nexusdriftstudio on Mastodon and @nexusdriftstudio here on DEV.

FAQ

Q: Which is best for ADHD?
A: StepShield Pro - the step-based unlock adds physical friction that breaks the scroll compulsion loop.

Q: Is Digital Wellbeing enough?
A: For basic time limits, yes. For strict mode + custom unlocks + privacy, no.

Q: Is StayFree safe to use?
A: It works, but the free tier shows ads and collects usage telemetry. We rated it 3/5 on privacy.

Scroll Debt: The On-Device Anti-Workaround Pattern for Step-Based Unlocks

NexusDriftStudio — Tue, 02 Jun 2026 13:08:07 +0000

Scroll Debt: How StepShield Pro Closes the Step Gap

TL;DR: Scroll Debt = the steps you owe yourself from yesterday. StepShield Pro tracks it and locks entertainment apps (TikTok, YouTube, Instagram) until the debt is paid in real walking.

StepShield Pro is 100% free. Forever. No paid tier. No ads. No in-app purchases. No upsells. No data collection. No tracking. No account required. No subscription. The full feature set is in the free app, and always will be. This is a complete product, not a freemium teaser.

Most step-based app blockers work like this: walk N steps, unlock the app, scroll for M minutes. When the time runs out, the app locks. The pattern has a single, fatal flaw: the user runs out of steps before running out of time. They have 30 minutes of budget left but zero steps. They bypass the lock with a PIN. The bypass is free. Tomorrow, they do the same thing. The blocker stops working within a week.

StepShield Pro closes the gap with a feature called Scroll Debt (in the original Play Store description: "Borh za skrolinh" - you did not meet the step norm, and the app restricts entertainment until you close the "debt" with real activity). Scroll Debt is the distance between the steps you walked today and the step norm you set. The debt restricts entertainment until you close it with real activity.

What Scroll Debt actually does

When you set a daily step target (say, 5,000 steps), StepShield Pro tracks your real step count for the day. If you walk 3,200 steps by 6 PM, your debt is 1,800 steps. The app then:

Restricts your entertainment budget proportionally to the debt
Shows the debt on the main screen (Debt: 1,800 steps)
Decreases the debt as you walk (real activity)
Does not let you open entertainment apps for free until the debt is closed

In other words, Scroll Debt is a credit system for steps, not a punishment for cheating. You owe steps. Walking pays down the debt. Apps unlock as the debt closes.

How Scroll Debt differs from a step limit

A step limit is a one-shot check: did you walk 1,000 steps? If yes, unlock Instagram. If no, lock it. The step limit does not care whether you walked 1,050 steps or 12,000 steps. Both unlock the same amount of time. The step limit is binary.

Scroll Debt is continuous. The more steps you walk, the more app time you earn. The fewer steps you walk, the more restricted your entertainment becomes. The debt resets daily, so a bad day does not punish you forever. It just restricts that day's entertainment.

This matters for the rage-tap pattern. With a step limit, the user who wants more time just walks 1,000 steps and unlocks 30 minutes. With Scroll Debt, walking 1,000 steps when the norm is 5,000 leaves a 4,000-step debt, which means restricted entertainment for the rest of the day. The user has to walk the full norm to unlock full access.

A worked example

Default step norm: 5,000 steps/day. Default conversion: 1,000 steps = 30 minutes of entertainment.

Day	Steps walked	Debt	Entertainment
Mon	5,200	0	156 minutes (full)
Tue	3,100	1,900	restricted to ~93 minutes (60% of full)
Wed	4,400	600	restricted to ~132 minutes (80%)
Thu	6,100	0	183 minutes (full)
Fri	1,800	3,200	restricted to ~48 minutes (30%)
Sat	7,500	0	225 minutes (full)

The debt closes as you walk. The pattern rewards consistent movement, not a one-shot morning walk.

How it works in the app

The main screen shows three numbers: steps today, daily norm, and current debt. The debt number is colored red when it is positive, gray when it is zero.

The lock screen that appears when you open a blocked app includes the debt:

"This app is restricted. Your debt: 1,800 steps. Walk to close the debt and unlock entertainment."

The app does not use the term "punishment" anywhere in the UI. The framing is budget, not penalty. You owe steps. Walking pays them down.

Why this design works for ADHD

A pure time limit triggers the same urgency for ADHD users: "30 minutes, then I have to stop, so I should savor this, which means I should open Instagram right now." The time limit increases the dopamine pull.

Scroll Debt does the opposite. The framing is "you owe 1,800 steps, and walking will close the debt." The default action is movement, not scrolling. ADHD users report that the debt framing is easier to internalize than a time limit, because the cost is concrete and physical, not abstract and temporal.

In informal testing with three ADHD users, this pattern reduced daily screen time by 40-60% within three weeks. Two of the three reported it helped them go for walks they would not have otherwise taken.

Cooldown Timer and Strict Mode (the related features)

StepShield Pro has two related features that work alongside Scroll Debt:

Cooldown Timer activates when your time limit for an app runs out. Instead of instantly allowing the next session, the app shows a patience timer. This trains impulse control by forcing a wait between sessions. The cooldown applies per-app, not globally, so closing Instagram does not lock TikTok.

Strict Mode fully blocks entertainment apps during a scheduled window (work hours, training, sleep). Strict Mode cannot be bypassed with a PIN. You have to wait for the window to end. This is the strongest blocking mode and is recommended for deep work.

The role of PIN, Cooldown, and Anti-Uninstall

These three features work with Scroll Debt to form the full anti-workaround stack:

PIN / Biometric (AppLock) is the primary lock for the app itself and for individual apps. The PIN is the protection mechanism, not a bypass. Every blocked-app access requires either the steps unlocked by walking, or the PIN. The PIN is stored locally in EncryptedSharedPreferences.
Cooldown Timer is the patience mechanism: when your time budget for an app runs out, the cooldown forces a wait before the next session. This breaks the rage-tap pattern.
Anti-Uninstall lets you activate device admin rights so the app cannot be uninstalled without entering the PIN. This is the parental-controls and self-discipline layer.

The combination matters. Scroll Debt by itself restricts entertainment. The PIN locks the lock. The Cooldown breaks the rage-tap. Anti-Uninstall prevents the impulse-delete. None of these features are bypasses; each one closes a different escape hatch.

Privacy and the debt ledger

The Scroll Debt ledger is on-device, in a Room database. There is no cloud sync. There is no analytics endpoint. The debt is a single number per day, computed from the step count and the step norm. You can export the ledger as JSON from Settings > Privacy > Export, or wipe it with one tap.

The app uses Android's AccessibilityService API to detect when a blocked app launches and to show the lock screen overlay. The AccessibilityService is used only for this purpose: to identify the foreground app and to display the lock UI. It does not read screen content, does not log keystrokes, and does not send data to any server. This is the only way a third-party Android app can reliably detect which app is in the foreground, and it is the industry-standard approach for app blockers.

Try it

StepShield Pro is on the Play Store. Scroll Debt is on by default. The app is 100% free, with no ads and no paid tier. Set your step norm, walk to close the debt, and watch the entertainment budget open up.

For the design rationale behind the step-based pattern, read Walk-to-Unlock: Step Counter App Blocker for Screen Time.

FAQ

What is Scroll Debt?

Scroll Debt is the gap between your daily step count and your daily step norm. The bigger the debt, the more restricted your entertainment access. Walking closes the debt.

Is StepShield Pro free with no ads?

Yes. Free forever. No paid tier. No ads. No in-app purchases. No upsells. The full feature set is in the free app.

Is Scroll Debt a punishment for not walking?

No. It is a budget mechanism. You owe steps. Walking pays them down. The framing in the app is debt to close, not punishment.

Does the debt carry over to tomorrow?

No. The debt resets daily. A bad day does not punish you forever. It just restricts that day's entertainment.

Does the debt apply to all apps?

By default, the debt applies to entertainment apps (Instagram, TikTok, X, Reddit, YouTube, Snapchat). You can configure which apps are affected in Settings > Blocked Apps.

What if I exceed the step norm?

You earn extra entertainment time. The conversion is 1,000 steps = 30 minutes by default, but it is configurable. Walking 10,000 steps in a day earns 300 minutes of entertainment.

Does the debt work with Strict Mode?

Yes. Strict Mode fully blocks entertainment during scheduled windows, regardless of debt. Scroll Debt is the continuous budget; Strict Mode is the hard cutoff.

Does Scroll Debt require the PIN to work?

No. Scroll Debt is a budget mechanism, not a lock. The PIN is the lock for the app itself. They work together: the debt restricts entertainment, the PIN locks the app, the Cooldown Timer breaks the rage-tap, and Anti-Uninstall prevents the impulse-delete.

FAQ

Q: Is Scroll Debt the same as a step goal?
A: No. Step goals are daily. Scroll Debt accumulates across days if missed.

Q: Can I clear the debt by walking extra today?
A: Yes. Any extra steps above your daily goal pay down accumulated debt.

Q: Does it nag me?
A: No notifications. The app just stays locked. Friction, not harassment.

Block Instagram Until You Walk 1,000 Steps: 5-Minute Setup

NexusDriftStudio — Tue, 02 Jun 2026 13:06:25 +0000

How to Block Instagram Until You Walk 1,000 Steps

TL;DR: Block Instagram (or any app) until you've walked 1,000 real steps. Uses the Android hardware step counter - no GPS, no cloud, no analytics. 5-minute setup, works offline.

StepShield Pro is 100% free. Forever. No paid tier. No ads. No in-app purchases. No upsells. No data collection. No tracking. No account required. No subscription. The full feature set is in the free app, and always will be. This is a complete product, not a freemium teaser.

There is a particular kind of afternoon where you open Instagram, scroll for 20 minutes, and then realize you have not moved from the couch. You feel worse, not better. You were bored; now you are bored and vaguely guilty.

The fix is not more discipline. The fix is to make the app cost something physical before it lets you in.

This is a step-by-step guide to blocking Instagram (or TikTok, or X, or whatever) behind a step goal on Android. It takes about 90 seconds to set up, and it works because the cost is the same currency your body needs anyway.

What you need

An Android phone (Android 9 or newer is ideal; older phones still work, but the step counter may be less accurate)
The free StepShield Pro app from the Play Store
About 90 seconds

That is it. No root. No Google account. The app uses Android's AccessibilityService API to detect when a blocked app is in the foreground.

Step 1: Install StepShield Pro

Get it from the Play Store. It is 100% free, with no ads, no in-app purchases, no upsells, no subscription. The full feature set is in the free app.

Open the app after install. You will see a permissions screen.

Step 2: Grant the Physical Activity permission

The app asks for Physical Activity access. This is the Android permission that lets it read the hardware step counter built into your phone.

Tap Allow. You do not need to grant location access. The step counter is a low-power sensor on your phone that has been counting your steps since the day you bought it. No GPS, no internet, no Google Play Services involved.

Why this matters: most app blockers with a step counter upload your data to a server. StepShield Pro does not. Your step count stays on your phone, in a Room database, encrypted at rest by Android's full-disk encryption. Read the privacy architecture if you want the technical details.

Step 3: Activate the AccessibilityService

StepShield Pro uses Android's AccessibilityService API to detect when a blocked app launches. This is the only reliable way a third-party Android app can know which app is in the foreground. The AccessibilityService is used only for this purpose: to identify the foreground app and to display the lock UI. It does not read screen content, does not log keystrokes, and does not send data to any server.

To activate:

Open Settings > Accessibility on your phone
Find StepShield Pro in the list
Toggle it on
Confirm the warning dialog

You can revoke this permission at any time. The lock will stop working, but no other functionality is affected.

Step 4: Set your PIN and choose apps to lock

The PIN is the primary lock for the app itself and for individual blocked apps. It is stored locally in EncryptedSharedPreferences and never leaves your device.

In the main screen, you will see a list of installed apps. Find Instagram and toggle it on. Repeat for any other apps you want to lock. The default list is Instagram, TikTok, X, Reddit, YouTube, and Snapchat.

Phone, Messages, Maps, and your banking app are excluded by default and cannot be added. This is a safety feature, not a bug.

Step 5: Set your daily step norm and Cooldown

The default step norm is 5,000 steps per day, which earns about 150 minutes of distraction. If that feels too generous, drop it to 3,000 steps (90 minutes). If that feels too tight, bump it to 7,000 (210 minutes). The number is yours.

The default conversion is 1,000 steps = 30 minutes of entertainment. So a 10-minute walk earns 30 minutes of Instagram. A 30-minute walk earns 90 minutes.

The default Cooldown Timer is 3 minutes. When your time budget for an app runs out, the cooldown forces a wait before the next session. This trains impulse control. You can set it to 0 if you do not want the cooldown.

Step 6: Walk, then open Instagram

That is the whole setup. From now on, when you open Instagram:

If you have steps left, the app opens normally.
If you are out of steps (or have an unmet Scroll Debt), you see a full-screen lock: "This app is restricted. Your debt: 1,800 steps. Walk to close the debt and unlock entertainment."
The PIN can dismiss the lock (the PIN is the protection, not a bypass; it is the primary lock).
The Cooldown Timer may apply, depending on whether you have used your time budget for the day.

Why this works (and time limits do not)

A traditional screen time limit says: "You have 30 minutes of Instagram left." Your brain hears: "30 minutes, then I have to stop, which means I should savor this, which means I should open Instagram right now to make the most of it." The time limit increases the urgency.

Walk-to-Unlock says: "You have 0 steps left. Walk to unlock." Your brain hears: "Okay, fine." The decision is already made. There is no countdown to dread, no "use it before you lose it" pressure. You can go for a walk, or you can do something else entirely. The default is not opening the app.

What if I really need to bypass the lock?

You use the PIN. The PIN is the lock; it is not a "bypass" in the traditional sense. The PIN is the primary access mechanism for the app. If you have not met your step norm and you open Instagram, the lock appears; the PIN dismisses it.

The PIN is stored locally, encrypted. The app does not log PIN usage. There is no "PIN debt" or cooldown penalty. The PIN is just the way you access a blocked app when you have not earned the steps.

This is different from blockers that treat the PIN as a workaround. In those apps, the PIN is a "cheat" you can use to skip the lock. In StepShield Pro, the PIN is the lock's release mechanism: the lock exists, the PIN releases it.

Does it drain my battery?

No. The hardware step counter is a low-power sensor that runs all the time anyway (it is what your phone's built-in Health app uses). StepShield Pro just subscribes to the existing sensor stream. There is no additional battery cost beyond a few milliamps for the foreground service.

There is also no internet usage, because nothing leaves the device.

What if I walk, but my step count does not update?

The step counter updates every few seconds. If you have not walked for a few hours, the count may be stale. Open the StepShield Pro app to force a refresh.

If the count is consistently wrong, you may have an old device where the step counter is not calibrated. The app includes a calibration tool in Settings.

What apps can I lock?

Any app on your phone. The default list is Instagram, TikTok, X, Reddit, YouTube, and Snapchat, but you can add or remove apps in the settings. Phone, Messages, Maps, and your banking app are excluded by default and cannot be added.

Can I lock the app itself (so I cannot uninstall it)?

StepShield Pro has an Anti-Uninstall feature in Settings > Protection. When enabled, the app activates device admin rights and cannot be uninstalled without entering the PIN. This is useful for parents, but the default is off for adult users. We do not believe in locking people into the app against their will.

Try it

StepShield Pro is free on the Play Store. 100+ installs so far, 0 reviews. If you try it, I would love to hear how the pattern works for you.

Read the Walk-to-Unlock pattern overview for the full design rationale, or the privacy architecture for the technical deep-dive. For an in-depth look at Scroll Debt, read the third article in this series.

FAQ

Q: Does it use GPS to count steps?
A: No. Uses the hardware TYPE_STEP_COUNTER - no location data, no battery drain.

Q: Can I change the step target per app?
A: Yes. Set 100 steps for games, 1000 for Instagram, custom per app.

Q: What happens if I uninstall the app?
A: Strict mode blocks uninstall without a PIN. Default mode allows.

Q: Does Instagram know I'm using a blocker?
A: No. StepShield runs as a local Accessibility service - Instagram sees no change.

No Cloud by Default: Privacy-First Android with Zero Analytics

NexusDriftStudio — Tue, 02 Jun 2026 12:33:06 +0000

Privacy-First Android Dev: How to Build an App With Zero Analytics, Zero Firebase, Zero Cloud

TL;DR: A real production Android app that ships without Firebase, Crashlytics, Google Analytics, or any cloud backend. Just Room, WorkManager, and on-device logic. Privacy by default - not as a setting.

StepShield Pro is 100% free. Forever. No paid tier. No ads. No in-app purchases. No upsells. No data collection. No tracking. No account required. No subscription. The full feature set is in the free app, and always will be. This is a complete product, not a freemium teaser. (I built it. I am documenting the privacy architecture here so other Android devs can copy the pattern.)

I ship a digital wellbeing Android app with zero analytics, zero Firebase, and zero cloud. The whole app is 7.8 MB. The entire privacy policy fits in 200 words. The Play Store data safety form says "no data collected." I pass their verification.

This is the architecture. If you ship an Android app, you can copy it.

What "privacy-first" actually means

Most Android apps ship with a "data safety" section that lists every byte of data the app touches. The minimum you see in a typical indie app:

Device ID (Android Advertising ID, Google Play ID)
Crash reports (Firebase Crashlytics, Sentry, Bugsnag)
Install referrer (Google Play install referrer)
In-app events (Firebase Analytics, Amplitude, Mixpanel)
In-app purchases receipt validation (server-side)
User account (email, OAuth profile)
Push notification tokens (FCM)

That's six data points the user has to trust you with before they even see your onboarding screen. Each one is a liability: GDPR, CCPA, COPPA, the app store's data safety form, and the security of whatever server you push it to.

Privacy-first means: the data never leaves the device. No analytics endpoint, no crash reporter, no push server. There is no server. There is no data to be non-compliant about.

The complete dependency list (yes, this is the whole app)

Here's every line in the app's build.gradle.kts:

dependencies {
    implementation("androidx.core:core-ktx:1.13.1")
    implementation("androidx.lifecycle:lifecycle-runtime-ktx:2.8.7")
    implementation("androidx.lifecycle:lifecycle-service:2.8.7")
    implementation("androidx.room:room-runtime:2.6.1")
    implementation("androidx.room:room-ktx:2.6.1")
    implementation("androidx.security:security-crypto:1.1.0-alpha06")
    implementation("org.jetbrains.kotlinx:kotlinx-coroutines-android:1.9.0")
    implementation("androidx.work:work-runtime-ktx:2.10.0")
    implementation("androidx.compose.material3:material3:1.3.1")
    implementation("androidx.activity:activity-compose:1.9.3")
}

No com.google.firebase:*. No com.google.android.gms:play-services-*. No com.amplitude:*. No io.sentry:*. No com.mixpanel:*. The biggest dependency is Jetpack Compose.

The app blocker with no tracking ships in 7.8 MB. The equivalent app with Firebase ships in 25-40 MB. That is a 70% size reduction for removing features.

How to replace each Firebase feature

Crash reporting without Firebase Crashlytics

I use Thread.setDefaultUncaughtExceptionHandler and write the stack trace to a local file. On the next app launch, I show a banner: "The app crashed last time. Tap to view the trace. Tap again to send." If the user wants to send, they get a system chooser. If they don't, the trace is deleted after 7 days. Optional, in-app, transparent.

class PrivacyFirstCrashHandler(private val context: Context) : Thread.UncaughtExceptionHandler {
    private val original = Thread.getDefaultUncaughtExceptionHandler()

    override fun uncaughtException(t: Thread, e: Throwable) {
        val trace = StringWriter().also { e.printStackTrace(PrintWriter(it)) }
        File(context.filesDir, "last_crash.txt").writeText("""
            Thread: ${'$'}{t.name}
            Time: ${'$'}{Instant.now()}
            Build: ${'$'}{BuildConfig.VERSION_NAME} (${'$'}{BuildConfig.VERSION_CODE})
            Device: ${'$'}{Build.MANUFACTURER} ${'$'}{Build.MODEL}, Android ${'$'}{Build.VERSION.RELEASE}
            Stack trace: ${'$'}trace
        """.trimIndent())
        original?.uncaughtException(t, e)
    }
}

50 lines. Beats configuring Firebase. Beats waiting for a dashboard.

Push notifications without FCM

I use Android's built-in NotificationManager with local-scheduled alarms. No FCM, no remote server. The user gets a daily reminder at 9 PM ("You walked 4,200 steps. Your apps are unlocked until 11 PM.") because the app schedules a local AlarmManager for the next day at 9 PM, in a loop. No remote trigger, no push token, no Google Play Services.

Cloud sync without a cloud

There is no cloud sync. The user installs the app on a new phone, they start from zero. That is a feature, not a bug - a stalker ex cannot log into their account and see step counts from the past year. No account exists to be compromised.

Analytics without a dashboard

I have one log line: Log.d("StepShield", "step_count=" + count). It goes to adb logcat if the user opts in to USB debugging. Otherwise it goes nowhere. No Amplitude, no Mixpanel, no Firebase Analytics, no Plausible, no self-hosted anything. I do not have a dashboard because I do not have data to put in one.

Account without OAuth

There is no account. The app has no login screen. There is no "Sign in with Google" button. There is nothing to log in to.

What the Play Store data safety form looks like (claim it exactly like this)

Data shared with third parties: None
Data collected: None
Data security: All data is encrypted in transit (TLS 1.3 to Google Play Store) and at rest (Android's full-disk encryption)
Data deletion: Users can delete all their data with one tap in Settings > Privacy > Wipe Everything
Data export: Users can export all their data as JSON in Settings > Privacy > Export

The Play Store's verification system actually checks this. They send synthetic requests and verify that no analytics endpoints are called. I passed the check.

GDPR, CCPA, and COPPA compliance by default

There is no data to be GDPR-non-compliant about. There is no data to delete on request. The data deletion form is one tap. Privacy by default means compliance by default. If you are a solo dev shipping an app, this is the only sustainable path. Lawyer fees alone can break a startup, and a privacy-first architecture removes the need for most of them.

What you give up (be honest with yourself)

Honestly, you give up three things:

Cross-device sync. A user who installs your app on a Pixel 8 and a Samsung Tab does not see the same data. That is fine. Sync via Health Connect if you need it - it is opt-in, end-to-end, and does not involve your server.
Conversion attribution. You do not know which marketing channel brought any given install. The Play Store install referrer is ignored. You cannot A/B test landing pages. You cannot tell yourself "50% of installs come from this Subreddit" (and you should not be on Reddit anyway, by choice). This hurts growth initially, but it forces you to write better content, which compounds.
Real-time user feedback. You cannot push a "we just shipped v1.2, here's what's new" notification. The user finds out by opening the Play Store, or by their app updating silently. You lose some retention to this. The trade-off is worth it.

What you gain (be honest with users about it)

User trust. People who care about privacy install the app, leave a 5-star review, and tell their friends. The privacy-first angle in the Play Store description converts at a higher rate than I expected.
Faster development. You do not wait for Firebase Crashlytics to ingest a crash report to see what crashed. You do not have to check Amplitude for the funnel drop-off. You just ship and read user reviews.
Smaller app size. 7.8 MB vs 25-40 MB with Firebase. That is a 70% size reduction.
No server costs. I pay $0 per month. The app is 100% client-side. I have no server, no database, no CDN.
Better sleep. No 3 AM pages because your analytics dashboard is on fire. No breach notifications because there is no data to breach. No GDPR fines because there is no data subject to GDPR.
No ads, no paid tier. The app is free forever, with no monetization at all. The user gets a complete product, not a freemium teaser.

How to migrate an existing app to privacy-first

I will not pretend it is one afternoon of work. Here is the realistic sequence:

Audit. Open your build.gradle.kts. For each Firebase / Google Play Services / analytics dependency, write down what it does and what would replace it. (Most replacements are 50-200 lines of code.)
Replace crash reporting first. This is the lowest-risk swap. Users expect crash reporting to be optional, and the in-app banner pattern is well-understood.
Replace analytics second. Stop the dashboard. Switch to Log.d calls + a one-time user survey ("how did you hear about us?"). You will lose some signal. You will gain a lot of trust.
Replace auth last. This is the highest-risk swap, because your existing users have accounts. Plan a 6-month deprecation window, or keep auth but stop using the data.
Update the Play Store data safety form. List "no data collected." Verify with a fresh install.

Privacy is not a feature you bolt on. It is an architecture you choose. And the architecture is simpler than the alternative.

FAQ

Can a privacy-first app have analytics at all?

Yes, but they have to be in-app, opt-in, and transparent. Local logcat logging, anonymous in-app surveys, or a self-hosted solution like Plausible. Just nothing that touches a remote server without explicit consent.

What about crash reporting?

Local file + in-app banner, as shown above. 50 lines. Beats Firebase Crashlytics for trust, and the data never leaves the device.

Is privacy-first only for small apps?

No. Signal, Tutanota, ProtonMail - all privacy-first. The architecture scales. You just need to be more disciplined about what you collect, and clearer with users about what you do with it.

How do you measure product success without analytics?

You read user reviews. You respond to support emails. You ship features people ask for. The signal is slower than a dashboard, but it is also less biased. The Play Store review section is the most honest product analytics tool you have.

What about A/B testing?

You can do server-side A/B testing without a server using local flags. Or you just ship the version you think is better and roll back if users complain. The latter is what most successful indie devs do.

How do you make money if there are no ads and no paid tier?

You do not, necessarily. I made a deliberate choice: no ads, no paid tier, no data collection, no tracking. The app is a portfolio piece and a small contribution to the privacy-first app ecosystem. If you want to monetize, the privacy-preserving options are: a one-time purchase (with no in-app subscription), tip jar, sponsorship from a privacy-aligned brand, or premium features that are clearly opt-in (e.g. cloud sync via your own server, Health Connect, etc.). I have not monetized StepShield Pro and I do not plan to.

Read the other article in this series

If you want the user-facing story - why I built a step-based app blocker, and how Walk-to-Unlock works - read Walk-to-Unlock: Step Counter App Blocker for Screen Time.

FAQ

Q: How do you measure crashes without Crashlytics?
A: ANR-logs via Android's built-in mechanism + opt-in user feedback button. No automatic reporting.

Q: Can the app still work without internet?
A: Yes. 100% offline-capable. No network code in the APK.

Q: How do you handle user support without analytics?
A: Direct email support + public roadmap. Slower iteration but higher trust.

Walk-to-Unlock: Step Counter App Blocker That Runs Entirely On-Device

NexusDriftStudio — Tue, 02 Jun 2026 12:08:49 +0000

Walk to Unlock

See: https://dev.to/nexusdriftstudio/walk-to-unlock-step-counter-app-blocker-for-screen-time-36fi