About

Last updated: June 10, 2026

I built TrueTo because I needed it.

I get motion sick. Not dramatically — no vomiting, no ER visits — but enough that looping video in apps, animated screen transitions, and certain scroll effects make me feel wrong for hours afterward. I have an Android phone, which is otherwise excellent. The settings to fix most of this exist. They're just nowhere near where you'd look.

The problem isn't the settings

Spotify has a toggle to disable Canvas — the looping video that plays behind songs. It works. It's in Settings and privacy → Content and display, filed next to explicit content warnings. Not in Accessibility. Not anywhere intuitive. Five taps from the home screen if you already know where it is.

Android has animation scale controls buried in Developer Options, which requires a separate unlock sequence most users don't know exists. Chrome has a force-zoom toggle that websites can't override — also not where you'd look.

These settings are real and they help. The problem is finding them under time pressure, when you're already symptomatic, staring at a phone that's making you feel worse.

What TrueTo does

TrueTo navigates to those settings for you. One tap, and you're at the toggle — not hunting through menus. That's the whole product.

It uses Android's Accessibility Service to open the right settings screen and locate the correct control. It does nothing else.

The free tier has no account, no usage analytics, and no ads. The app downloads its automation steps from Google Firebase, which is how a broken step gets fixed without waiting for an app update, and if it crashes it sends an automatic crash report to Google's Crashlytics service so I can fix it. Crash reports contain no screen content, no personal content, and no account information.

Premium adds an optional account that syncs your scan results across your devices. Everything the app collects, free or Premium, is listed in the privacy policy.

On verification

Every setting listed in TrueTo is one I've navigated to personally on a real Android device. App menus change with updates; what worked in one version of Spotify may be in a different location in the next. I re-verify after significant app updates. When a path changes, I update the app.

The blog posts work the same way. If a post describes a settings path, I've followed that path on device before publishing.

Why it keeps working

A settings tool that phones home before every tap isn't reliable. TrueTo's navigation runs entirely on your device: no tap waits on a server.

The network has two narrow jobs — downloading updated automation steps when an app rearranges its settings, and carrying a crash report if the app breaks. On a plane, in a basement, on throttled data, the steps already on your phone keep working.


Questions or feedback: support@trueto.app