About FixThatApp

An independent troubleshooting and tools site — built by one person, for real problems.

FixThatApp was built out of a specific frustration. The year was 2024 and I was trying to fix a WhatsApp calling issue for my parents. Every result I found was either a blog post written by someone who clearly hadn't tried the steps themselves, a forum thread that ended without a resolution, or a "top 10 fixes" list where step one was "restart your phone" and step two was "update the app." None of it addressed why the problem was happening or how to tell which fix applied to my situation.

So I started writing guides the way I wanted to find them: diagnostic first, then targeted fixes in order of likelihood, with an explanation of what's actually causing each failure. No filler. No padding. No "this is a common issue" preamble that wastes three paragraphs before saying anything useful.

That became FixThatApp — which has since grown to cover 48 in-depth troubleshooting guides across apps, devices, and services, plus 60+ free browser-based tools and a technical blog.

How Every Guide Is Written

Every troubleshooting guide on FixThatApp follows the same process, in this order:

1. Reproduce the problem. I go through the actual failure scenario before writing a word. If I can't reproduce it, I find someone who has reported it recently with enough detail to understand the cause.
2. Identify the root cause, not just the symptom. "WhatsApp not calling" can be five different problems — a firewall issue, a battery optimization kill, a VoIP block on the carrier, a codec mismatch, or a regional restriction. Each one has a different fix.
3. Order fixes by probability, not ease. Most guides put "restart your phone" first because it's easy to write. I put it where it actually belongs in the diagnostic sequence — which is rarely first.
4. Check against current app behaviour. Apps change. A fix that worked in 2022 may not work in 2026 because the UI moved, the feature was renamed, or the underlying cause was patched. Every guide is reviewed against the current app version before publishing.
5. Add the "What NOT to Do" section. Almost every troubleshooting problem has a common mistake that makes it worse. These are documented specifically — not as generic warnings, but as real scenarios where the wrong step turns a recoverable problem into a harder one.

Who Writes and Maintains This Site

What the Site Covers

• Troubleshooting guides — step-by-step diagnostic guides for apps like WhatsApp, Discord, Instagram, Spotify, Gmail, Chrome, and more. Each guide identifies the likely cause first, then gives targeted fixes for each cause. Not a list of things to try.
• Free browser-based tools — calculators (GST, SIP, compound interest, loan EMI, tax, profit margin), developer tools (JWT decoder, hash generator, JSON formatter, regex tester), and text utilities (diff checker, duplicate remover, whitespace cleaner). Everything runs in your browser — nothing is sent to a server.
• Technical blog — in-depth explainers on the topics behind the tools and guides: how EMI formulas work, what makes a password actually secure, why CSS minification works, how DNS propagation happens. Written for people who want to understand, not just copy-paste.

Editorial Standards

• Every fix is explained, not just listed. A guide that says "clear your cache" without explaining what cache does and why clearing it helps is not useful. Every step on this site includes a brief explanation of the underlying cause.
• No paywalls, no accounts, no upsells. Every tool and guide is free. The site is supported by Google AdSense display advertising, which is disclosed in the Privacy Policy.
• Tools don't touch your data. All calculators and text tools run entirely in your browser. Input values are not sent anywhere. There are no server-side requests when you use any tool on this site.
• Dates reflect actual last-reviewed dates. The "Last updated" date on each page is the date I last reviewed and verified the content against current app behaviour — not the original publication date.
• No sponsored content. Articles and guides are not paid placements. There is no mechanism to buy a mention on this site.

Content Corrections

If a fix no longer works, a UI path has changed, or a calculator gives you a wrong result — please let me know with the page URL and a description of the issue. I aim to review and correct reported errors within 2–5 business days.

All Guides Tools Blog Privacy Policy Contact