Android tools — start here, then pick a path
This hub is for people who already have a build, a manifest, or a device on the desk. Choose the job, not a grid. Most of these tools run in your browser; they do not replace Android Studio, apktool, or Play Console.
Decision guide
- I have an .apk and I should not install it yet → APK Analyzer, then the analysis guide.
- I have permission lines and a Play review next week → Permissions Decoder.
- I am editing text AndroidManifest.xml → Manifest Validator.
- The device is on USB and I need a command → ADB command generator.
- Marketing sent a link that should open the app → Intent URL + Deep link tester.
- I need launcher densities from one image → App icon generator.
- I need a signing checklist, not a keystore in the browser → APK signer guide.
Path A — Before sideload or Play upload
1. Hash and list the APK. 2. Read versions as clues only. 3. Paste permissions as text. 4. Validate the text manifest you are about to merge. Full write-up: How to analyze an APK without installing it. Related: versionCode, versionName, and applicationId, publishing checklist.
The APK Analyzer uses JSZip + Web Crypto. It does not decode binary AXML. If “Possible package” is blank, switch to aapt or apktool. The string extractor is for leftover debug copy, not a localization suite.
Path B — Links, intents, and a device
Intent URLs and verified App Links fail in boring ways: wrong scheme, missing host, activity not exported, debug vs release applicationId.
Generate the URL, then sanity-check it in the deep link tester before you file a ticket on the device. ADB helps with
am start once USB debugging is on — the generator does not talk to your phone from this site.
Path C — Store assets and adjacent web
Icons: the icon generator canvas-resizes one PNG. It does not write Adaptive Icon XML — read the safe-zone note before you ship. Dessert name → API integer: the local version table (not a device probe, not Play’s catalog).
Frequently asked questions
Does DroidXP upload my APK?
Local Android tools parse in your browser. Follow your own policy for confidential builds on shared machines.
Can these tools replace Android Studio?
No. They are desk checks. Builds, debugging, and profilers stay in the IDE.