About DroidXP

DroidXP is a local-first desk for Android build checks. Drop an APK, paste a manifest, or decode a permission list in the browser, then read a guide when the check is not enough and you still need apktool, aapt, or Play Console.

Created by: Guru N

Copyright 2026

About

I built DroidXP because checking an Android build should be a simple step. Drop an APK, paste a manifest, or decode a permission list in the browser. The file stays in the tab. If you like the site or have a suggestion, write to thedroidxapps@gmail.com. Feedback is welcome.

What this site is for

The useful moment is the gap between “the build finished” and “I am ready to install it or upload it.” Android Studio, the SDK tools, and Play Console are the right place for the full job. They are a poor place for a thirty-second question: what is inside this APK, which permission names are in this list, does this text manifest even parse.

DroidXP answers that smaller question in the tab. The indexed site is those checks, plus the guides and the blog that say when the browser result is only a clue. There is no account and no fee. The privacy policy, terms, and disclaimer describe the limits in plain language.

A check, in order

This is the order the pages are written for. Skip a step when you do not have that file.

  1. APK Analyzer lists ZIP entries, counts .dex files, detects lib/*.so, and hashes the whole file. Printable text can suggest a package name and version. It does not decode binary manifest XML, list permissions, or verify a signature. The longer write-up is How to analyze an APK.
  2. APK String Extractor exports raw strings.xml when that file is stored as text. Otherwise it scans resources.arsc as bytes. It is not a localization suite.
  3. Permissions Decoder labels pasted uses-permission names from a list in the page. Unknown names, including QUERY_ALL_PACKAGES, stay unknown. A label is not Play policy and not a runtime grant. See permissions that cause Play review.
  4. Manifest Validator parses text XML only. It checks the root, package, application, uses-sdk, and a launcher activity. It does not check android:exported, debuggable, or allowBackup. Binary AXML from inside an APK will not parse here.
  5. Version Checker is a local table from API 16 through API 36. It does not read a phone and it is not Play’s device catalog.
  6. ADB Command Generator and the APK signer guide print shell text. They do not run adb, read a keystore, or sign a file. ADB and intents without Studio explains where you run the line.
  7. Intent URL Generator and the Deep Link Tester build and parse URL text. They do not contact the host or fetch assetlinks.json.
  8. App Icon Generator resizes one PNG in the tab. It does not write mipmap folders or adaptive-icon XML. The safe-zone note is on the blog.

Where the file goes

A dropped APK or a pasted manifest is read in the browser. It is not uploaded to droidxp.com. The page still loads fonts, and the APK tools also load a library from jsDelivr. Those requests do not include your file.

There is no account. The theme choice is stored in the browser. The privacy guide and the privacy policy list what the pages load. Advertising is not enabled, and the pages do not load an advertising tag.

What a result is not

A blank “possible package” line does not prove the package is missing. A permission label does not mean Play will approve the app. An OK deep-link parse does not mean the App Link is verified. A PNG from the icon tool is not an adaptive icon. The signer page prints commands and does not sign. When the browser check and the SDK disagree, trust aapt, apktool, or Play Console. Browser tools vs apktool and aapt is the comparison. Two longer notes: the merged manifest is not the XML you pasted, and a file hash is not a signing certificate.

Who publishes this site

The site is published as DroidXP by Guru N. The tools and the guides are the work you can check.

The only contact address is thedroidxapps@gmail.com. The contact page can open that address in your mail app. Include the page URL and what you expected the tool to show.

The same name is on these profiles: