MotionEaseTune: a 100 Hz tone as a motion sickness remedy

What the application actually does

MotionEaseTune is described in one line in the repository description and repeated in the README: it is a simple application that can prevent motion sickness via 100Hz sound. That is the entire product. There is no session plan, no symptom tracking, no training schedule, no profile and no account.

The usage section is four steps, and they are short enough to quote as the specification of the app:

1. Download the application from the releases page and open it. 2. Use it before the onset of motion sickness symptoms. 3. Make sure the volume is the same for both ears. 4. Listen for about one minute.

The third step is the one that deserves attention, because it is a condition rather than a default. If the volume is not matched across the two ears, the app cannot deliver the intended stimulus, and the README does not say what happens in that case. A user with a hearing aid, a recent ear infection or a preference for one-ear audio is in a position where the instruction is harder to satisfy than the app makes it sound.

The fourth step is also a condition. The duration is described as about one minute, and the app is meant to be used before symptoms appear rather than after. The reading order is therefore prophylactic, and the timing advice is the thing to internalize before a trip rather than during one.

The 100 Hz tone is borrowed from a specific study

The README cites a single reference, and it is a precise one: the paper titled "Just 1-min exposure to a pure tone at 100 Hz with daily exposable sound pressure levels may improve motion sickness", linked through a DOI into Environmental Health and Preventive Medicine.

That title is more informative than the app's own description, because it states the four parameters: one minute of exposure, a pure tone at 100 Hz, a sound pressure level that is safe for daily exposure, and an outcome described as an improvement in motion sickness.

Two things follow for a reader. First, the app is a one-screen implementation of a single published result, so the app and the study are the same claim, and the study is the place to look for detail the app does not surface, such as the exact sound pressure level or the population the result was obtained in. Second, the wording of the paper title is careful. It says the exposure "may improve" motion sickness, and the app's README turns that into a flat "can prevent", which is a stronger claim than the citation supports.

That gap between the hedged language in the source and the definite language in the app description is worth keeping in mind when you decide how much to trust it, and it is the reason to read the paper before you rely on the app for a long journey.

A Flutter project with fastlane and localisation set up

The repository layout shows a conventional Flutter application rather than a native Android project. The primary language is Dart, and the top level entries are the usual Flutter set: `lib/`, `android/`, `assets/`, `test/`, `pubspec.yaml`, `pubspec.lock`, `analysis_options.yaml` and a `.metadata` file, with a `fastlane/` directory for release automation and a `l10n.yaml` for localisation.

The `l10n.yaml` file and the presence of `README_zh.md` alongside `README.md` point the same way. The README header links to a Chinese version of the document, and the project is presented in both languages. Flutter's own localisation tooling is set up, so the app is built to carry more than one language, even though the repository shows two README languages.

The `fastlane/` directory matters more than it looks for a project with this scope. It suggests the release builds are produced by an automated pipeline rather than by hand, which is the difference between a project that can publish a new version in an afternoon and one where every update needs a maintainer with a local Android toolchain.

The `test/` directory and `analysis_options.yaml` show a project with the standard Dart analysis and test scaffolding in place. The `assets/` directory holds the icon referenced from the README header, and `screenshots/` holds the main view and the three user guide images that the README displays.

Distribution is a release build plus one app store

There are two documented ways to get the application, and neither is a package manager dependency.

The first is the releases page of the repository, which the README links under an Install label in its header. The user is told to download the application and open it, which means the deliverable is a built APK rather than source you compile.

The second is IzzyOnDroid, where the project has its own listing, linked with a badge in the README pointing at the package `com.bhznjns.motion_ease_tune`. IzzyOnDroid is a third party app repository, and having a listing there is a statement about reach: the project is visible to users of that repository who would never find a GitHub release page on their own.

The release history supports the reading that publishing is a recurring activity rather than a one-off. Tags 1.1.3 from 2025-05-29 and 1.1.2 from 2025-05-12 sit a fortnight apart, with the commit message style of a small project that ships a patch when something needs fixing, and there is a release named for a CI test for IzzyOnDroid, which suggests the store listing is validated in continuous integration.

The practical consequence for a user is that the app is a one-click install with no build step, and for a reader evaluating the project is that the code is packaged for consumption rather than for embedding. There is no library API here, no `pubspec` dependency other people would add, and no way to reuse the tone generator inside another Flutter app as published.

What is missing, and where the alternatives sit

The clearest limitation is the absence of controls. Nothing in the README describes a frequency setting, a duration slider, a volume control inside the app, a timer, or a way to run the tone more than once. The 100 Hz frequency and the one minute duration are fixed properties of the application. Someone who reads the study and wants a different exposure, or someone who wants a longer session, has to leave the app entirely.

The second limitation is platform. The repository contains an `android/` directory and the project is tagged as an Android application, and the README offers a downloadable build rather than a store listing for iOS. There is no iOS artifact described anywhere in the README.

The third limitation is the maintenance horizon. The repository is not archived and the last push was on 2026-04-26, with the newest release tag at 1.1.3 from 2025-05-29. That is a project in a state where the code is available and installable, and where you should not expect a steady stream of fixes.

There is a real alternative, and it is a structural one rather than a competing product. The tone itself is not the contribution: any device or app that can play a sustained 100 Hz sine wave for a minute does the same job. The difference this project makes is packaging, distribution and instruction, so that the correct stimulus is one tap away with the volume-balance step spelled out. If you already have a tone generator, an equalizer, or a media player able to output a single frequency, the functional gap is small, and the honest question is whether the guided routine is worth more to you than the freedom to adjust the parameters.

Editorial conclusion

MotionEaseTune suits an Android user who wants a zero-configuration answer to motion sickness and is willing to follow a one-minute listening routine before travelling, since the app does exactly one thing and gets it right. It does not suit anyone who needs to choose a frequency, adjust the duration, run on iOS, or rely on the project for a long-term support commitment, because the repository documents no settings at all and the last push was on 2026-04-26. Before installing, confirm that your device can play a sustained 100 Hz tone at a comfortable level, check the volume balance between ears as the README instructs, and read the linked study in Environmental Health and Preventive Medicine to understand what the exposure is based on.

Frequently asked questions

Official sources

1. BHznJNs/MotionEaseTune on GitHub
2. Issues
3. License: GPL-3.0
4. README
5. Releases