Frontend & Mobile

iOS & Android developer tools

Mobile platform configuration lives in files that are easy to get wrong and hard to debug on-device: a provisioning profile with entitlements that don't match what the app requests, an AndroidManifest.xml with an intent filter that never matches, an assetlinks.json that Android silently rejects, or a bundle ID with an invalid character buried in a long reverse-DNS string. These tools read that configuration directly so a mismatch shows up before you build and install to a device.

The iOS-specific tools cover profile and push setup: the Provisioning Profile Viewer inspects entitlements and device lists, the AASA Validator tests App Site Association rules against real URLs, and the APNs token formatter converts push tokens between hex and decimal arrays. On Android, the manifest viewer extracts permissions and intent filters, and the App Links validator checks assetlinks.json against the package and certificate it must match. Across both, the Deep link builder composes scheme URIs, and the Mobile unit converter converts dp, sp, pt and px.

10 tools

iOS / Android Dev Tools tools FAQ

Why does Android reject my assetlinks.json for App Links?

assetlinks.json has to match the app's package name and the exact SHA-256 signing certificate fingerprint, and a mismatch on either one causes Android to silently ignore the file entirely rather than showing an error. The Android App Links validator checks assetlinks.json against both the package and the signing certificate.

How do I check what a provisioning profile actually allows?

A .mobileprovision file bundles entitlements, allowed devices and certificate information together in a binary plist format that isn't readable directly in a text editor. The Provisioning Profile Viewer inspects a provisioning profile's entitlements and device lists without needing Xcode installed.

What's the difference between dp, sp and pt in mobile layouts?

dp and sp are Android's density-independent units, with sp additionally scaling with the user's chosen text size, while pt is the roughly equivalent unit used on iOS, and none of them convert to raw pixels the same way across every device. The Mobile unit converter converts dp, sp, pt and px between the two platforms' display scales.