<p>The table below lists the intents that your application can send, to invoke Google applications on Android devices in certain ways. For each action/uri pair, the table describes how the receiving Google application handles the intent. </p>
<p>Note that this list is not comprehensive.</p>
<table>
<tr>
<th scope="col">Target Application</th>
<th scope="col">Intent URI</th>
<th scope="col">Intent Action</th>
<th scope="col">Result</th>
</tr>
<tr>
<td rowspan="2">Browser</td>
<td>http://<em>web_address</em><br />
https://<em>web_address</em></td>
<td>VIEW</td>
<td>Open a browser window to the URL specified. </td>
</tr>
<tr>
<td>"" (empty string) <br />
http://<em>web_address</em><br />
https://<em>web_address</em></td>
<td>WEB_SEARCH</td>
<td>Opens the file at the location on the device in the browser. </td>
</tr>
<tr>
<td rowspan="2">Dialer</td>
<td height="103">tel: <em>phone_number</em></td>
<td>CALL</td>
<td><p>Calls the entered phone number. Valid telephone numbers as defined
in <a href="http://tools.ietf.org/html/rfc3966">the IETF RFC 3966</a> are
accepted. Valid examples include the following:</p>
<ul>
<li>tel:2125551212 </li>
<li>tel:
(212) 555 1212</li>
</ul>
<p>The dialer is good at normalizing some kinds of schemes: for example
telephone numbers, so the schema described isn't strictly required
in the {@link android.net.Uri#parse(java.lang.String)
Uri(URI string)} factory. However, if you have not tried a
schema or are unsure whether it can be handled, use the {@link
