Choose an action — call, SMS, email, WhatsApp, map, directions, Play Store or another app — fill in the details, and the builder produces the correctly encoded link and a ready <a> tag. Inside an app that hands non-web links to Android, tapping it opens the matching app.
Link types at a glance
| Action | Format | Opens |
|---|---|---|
| Call | tel:+14155550123 | Dialer (number filled in) |
| SMS | sms:+1415…?body=Hi | Messages |
mailto:a@b.com?subject=…&body=… | Email app | |
https://wa.me/14155550123?text=… | ||
| Map | geo:0,0?q=Eiffel+Tower | Default map app |
| Directions | https://www.google.com/maps/dir/?api=1&destination=… | Google Maps |
| Play listing | market://details?id=com.example.app | Play Store |
| Other app | intent://…#Intent;scheme=…;package=…;end | That app, or a fallback URL |
Why these links need the app's help
A WebView only knows how to display web pages. Given tel: or intent: it shows an "unknown URL scheme" error unless the app intercepts the link and hands it to Android. Apps built with HTML2APK Pro do this for every non-web scheme, and also send wa.me, t.me, Google Maps and Play Store links to their apps instead of loading their websites. Always test the links on your actual build.
Encoding
Spaces, line breaks, & and non-English characters in messages must be percent-encoded, which the builder does. In HTML attributes, write & as & — the copied tag already does.
Frequently asked questions
Does a tel: link call automatically?
No. It opens the dialer with the number filled in; the user taps the call button. Calling directly would need a phone permission an HTML app should not ask for.
Why does my WhatsApp link open a web page?
WhatsApp is not installed, or the app loading the link displays https links itself. Builds that route wa.me links to Android open WhatsApp directly.