About

Tools built while shipping real apps.

Mr.AndroidShin Dev Tools is a small collection of single-purpose utilities for Android and Jetpack Compose developers. It is run by one person — a solo Android developer who designs, builds and publishes apps to Google Play, mostly in Kotlin and Jetpack Compose.

Why the site exists

Every tool here started as a chore I kept hitting in my own work: pasting a hex value into a Color(0xFF…) literal, checking whether a color passed contrast, or working out which Kotlin version a given Compose compiler expects. Instead of searching for the same answer each time, I turned each one into a focused page that loads fast, runs entirely in the browser, and never asks anyone to sign in.

What you can expect

Tools that do one job well, with no accounts, no uploads, and no data collection beyond what is described in the privacy policy. Everything runs client-side, so your inputs stay on your device. New tools and short, practical guides are added as I build them.

Who it's for

Android developers who want a quick answer without wading through documentation — whether you are prototyping a design system, migrating a Gradle setup, or estimating ad revenue for a side project. If a tool would save you time, that is a good candidate to add.

How the tools are built

Every utility here is a single, self-contained page. There's no framework to load, no tracking beyond the privacy policy, and no server doing the work — the logic runs in your browser with plain JavaScript. That keeps them fast, keeps your input on your device, and means a tool still works even on a flaky connection. Each one is tested against known-correct values before it ships; where a calculation follows a public standard — WCAG contrast ratios, Base64/UTF-8 encoding, exposure stops — the result is checked against that standard rather than eyeballed.

Guides and debugging notes

Alongside the tools, the site collects short, practical write-ups: how a particular Play Console step works, what a specific Gradle or Firebase error actually means, and how I fixed it in my own projects. These aren't rewrites of the official docs — they're the notes I wish I'd had when I hit the problem, written from real debugging sessions on real apps. If one of them saves you the hour it cost me, it's done its job.

Accuracy and updates

Android tooling moves quickly, so version numbers and menu names in the guides are written as illustrative examples, not fixed truth — the concepts are what matter. If you spot something out of date or wrong, the contact page is the fastest way to flag it, and confirmed corrections get made promptly.

Get in touch

Suggestions, corrections and requests are welcome. See the contact page for how to reach me.