816
edits
No edit summary |
No edit summary |
||
| Line 92: | Line 92: | ||
| <!-- Email --> | | <!-- Email --> | ||
| <!-- Gallery --> | | <!-- Gallery --> | ||
| | | Add to Home <!-- Homescreen --> | ||
| <!-- Music --> | | <!-- Music --> | ||
| <!-- PDFjs --> | | <!-- PDFjs --> | ||
| Line 323: | Line 323: | ||
</div> | </div> | ||
# The browser currently handles any activity where activity.source.data.type is 'url' by opening a new tab, but I don't think this activity is initiated by the homescreen itself but at a lower level. | # The browser currently handles any activity where activity.source.data.type is 'url' by opening a new tab, but I don't think this activity is initiated by the homescreen itself but at a lower level. | ||
| Line 332: | Line 331: | ||
* 1. Select from list of compatible applications that the link can be shared to: | * 1. Select from list of compatible applications that the link can be shared to: | ||
** Email, Compose message | ** Email, Compose message | ||
*** subject line: "[name] | *** subject line: "[name] shared a link with you" | ||
*** body text: [link] | *** body text: [link name][link url] | ||
** Messaging/SMS | ** Messaging/SMS | ||
*** | *** Open to New Message screen | ||
*** Open keyboard | |||
*** Add link url to a new blank message | |||
*** Place cursor one space after url | |||
* 2. User sends message or completes sharing operation | * 2. User sends message or completes sharing operation | ||
* 3. Share operation is completed in background and user is returned to browser | * 3. Share operation is completed in background and user is returned to browser | ||
==== In browser content mailto: link ==== | ==== In browser content mailto: link ==== | ||
* 1. User | * 1. User taps email link | ||
* 2. Email, Compose message | * 2. Email, Compose message | ||
** to: [mailto: email address] | ** to: [mailto: email address] | ||
| Line 348: | Line 350: | ||
==== In browser content link pattern ==== | ==== In browser content link pattern ==== | ||
* 1. Pattern match website addresses (ie: www.domain.com) | * 1. Pattern match website addresses (ie: www.domain.com) | ||
* 2. User | * 2. User taps link | ||
** | * 3. Link opens | ||
==== In browser content .PDF link ==== | |||
* 1. User taps link with .PDF file type (ie: www.domain.com/menu.pdf) | |||
* 2. Open headless PDF.js app | |||
* 3. PDF.js loads the content, user interacts with it. | |||
* 4. User at any time can tap "Close" input in PDF.js UI. | |||
* 5. User exits to previous screen | |||
==== In browser content phone number pattern ==== | ==== In browser content phone number pattern ==== | ||
* 1. Pattern matches phone numbers (eg XXX-XXX-XXXX formatted) | * 1. Pattern matches phone numbers (eg XXX-XXX-XXXX formatted) | ||
* 2. User | * 2. User taps phone number | ||
* 3. Dialer application is opened with phone # added to number field. | * 3. Dialer application is opened with phone # added to number field. | ||
| Line 364: | Line 374: | ||
==== Captured image view ==== | ==== Captured image view ==== | ||
* 1. User | * 1. User taps on image thumbnail to reveal full sized image from gallery. | ||
=== Calendar === | === Calendar === | ||
| Line 379: | Line 389: | ||
=== Contacts === | === Contacts === | ||
==== Contact website entry ==== | ==== Contact website entry ==== | ||
* 1. User | * 1. User taps on website address | ||
* 2. Web browser opens and navigates to address | * 2. Web browser opens and navigates to address | ||
==== Contact phone number entry ==== | ==== Contact phone number entry ==== | ||
* 1. User | * 1. User taps phone number | ||
* 2. Dialer opens and immediately dials phone number | * 2. Dialer opens and immediately dials phone number | ||
==== Contact email address entry ==== | ==== Contact email address entry ==== | ||
* 1. User | * 1. User taps email address | ||
* 2. Email | * 2. Email app opens to Compose Message view | ||
** To | ** "To" field is populated with email address | ||
** Keyboard opens | |||
** Subject field is selected | |||
* 3. User sends email | * 3. User sends email | ||
* 4. Email | * 4. Email "Send" operation is completed in background, and user is returned to Contact entry. | ||
==== Send SMS/MMS/Message contact ==== | ==== Send SMS/MMS/Message contact ==== | ||
* 1. User | * 1. User taps on Send message | ||
* 2. New SMS/MMS/Message | * 2. New SMS/MMS/Message | ||
** To: contact phone # | ** To: contact phone # | ||
| Line 409: | Line 421: | ||
=== Dialer === | === Dialer === | ||
==== Add phone number to contact ==== | ==== Add phone number to contact ==== | ||
* 1. User | * 1. User taps Add Contact button | ||
* 2. | * 2. Contacts app opens, to Add Contact view | ||
* 3. User enters contact details | * 3. User enters contact details | ||
* 4. User saves contact | * 4. User cancels or saves contact, activity closes, user is returned to Dialer. | ||
=== Email === | === Email === | ||
| Line 421: | Line 433: | ||
==== Read Email Contact ==== | ==== Read Email Contact ==== | ||
* 1. Match any emails in Contacts application | * 1. Match any emails in Contacts application | ||
* 2. | * 2. User taps on contact | ||
* 3. Open entry in Contacts. | * 3. Open entry in Contacts. | ||
edits