Editorial policy
How we write, check, and correct what's on this blog
The RambleFix blog covers dictation, voice notes, and speech-to-text tooling. This page explains who writes it, how posts are produced, what we will and won't publish, and how to get something fixed.
Who writes this
Yash Bagal is the founder of RambleFix and the author of the posts here. He builds the RambleFix web, iPhone, and Mac apps, and uses the dictation and transcription tools covered on this blog in his own day-to-day work. Posts are attributed to him because he is responsible for what they say.
RambleFix is made by Appetite for Distraction LLC.
How posts are produced
We use AI writing tools in our process, and we think you should know exactly where. Each post goes through the same pipeline:
- Research. Search demand for the topic is checked with real keyword data before a post is planned, and primary sources — studies, vendor documentation, official support pages — are gathered first.
- Drafting. A first draft is produced with AI assistance, working from that research and our own experience with the tools.
- Automated checks. Every statistic is verified against the page it cites. Every link is checked. Headings, metadata, and structure are reviewed against a fixed rubric, and a draft that fails any of these is rewritten or held.
- Publication. Only drafts that clear all of the above are published. Anything that doesn't is queued for a human to look at.
Because the process is repeatable, we say so plainly rather than pretending each post was hand-typed. What we stand behind is the accuracy of the content, and that is what the checks are for.
Sourcing standards
- We do not publish a statistic we cannot trace to a named source with a working link. If a number can't be verified, it is cut.
- We prefer primary sources: peer-reviewed research, official documentation, first-party benchmarks. Preprints are labelled as preprints, and vendor-published data is attributed to the vendor.
- Where a study's population or method limits how far its findings travel, we say so in the post rather than in a footnote.
- Product behaviour claims (which iOS version added a feature, what a setting does) are checked against the maker's own documentation.
Independence and competitors
RambleFix is a product, and this blog exists partly to help people find it. We handle that in two ways: every post is useful on its own without RambleFix, and when we mention our own product we do it once, clearly, near the end. We do not run affiliate links, and nobody pays for placement.
When we compare RambleFix with other tools — AudioPen, Wispr Flow, Otter.ai, Apple's built-in dictation, and others — we compare on specifics and give the other tool its due. If a competitor does something better, the post says so.
Updates and corrections
Posts show a published date and, when the content has materially changed, an updated date. We update a post when the facts change — a new OS version, a revised study, a product that has been discontinued — not to refresh a date for its own sake.
If you spot an error, a broken link, or a claim you think is unsupported, tell us. Corrections are made in the post itself, and significant ones are noted at the point of the change.
Reader privacy
The blog follows the same privacy policy as the rest of RambleFix. We do not sell reader data, and we do not use it to train AI models.