816
edits
(Populate with outline) |
m (→Background) |
||
| Line 20: | Line 20: | ||
=== Are exclusively user-initiated. === | |||
=== Comprised of four components === | |||
Action + Type + [data] + Disposition | Action + Type + [data] + Disposition | ||
| Line 43: | Line 43: | ||
=== Can be one-way, or round trip === | |||
==== One way ==== | |||
* 1. Browser: "Share" | * 1. Browser: "Share" | ||
* 2. Select handler app from list of apps that support that Activity (Share), type (URL), and [Data] (string) | * 2. Select handler app from list of apps that support that Activity (Share), type (URL), and [Data] (string) | ||
| Line 53: | Line 54: | ||
In a one-way trip, the message composition window would then close, and take user to main window of Email app. The user would not be returned to the originating app (Browser). | In a one-way trip, the message composition window would then close, and take user to main window of Email app. The user would not be returned to the originating app (Browser). | ||
==== Round trip ==== | |||
* 1. Email: "Attach" | * 1. Email: "Attach" | ||
* 2. Select attachment type from list (eg: Image, Document, Video, etc) | * 2. Select attachment type from list (eg: Image, Document, Video, etc) | ||
| Line 67: | Line 69: | ||
The system maintains a record ''(via a central registry in Activities API?)'' of which apps support which Actions & Types, and uses this record to present to populate the list of available handler apps when the user selects an Action. | The system maintains a record ''(via a central registry in Activities API?)'' of which apps support which Actions & Types, and uses this record to present to populate the list of available handler apps when the user selects an Action. | ||
== Requirements == | == Requirements == | ||
edits