Confirmed users
975
edits
Performance/Fenix: Difference between revisions
Jump to navigation
Jump to search
→MAIN/VIEW start up: Change to Path
(→COLD/WARM/HOT start up: Add "state" description) |
(→MAIN/VIEW start up: Change to Path) |
||
| Line 123: | Line 123: | ||
* HOT = basically just foregrounding the app: the process and HomeActivity are already created | * HOT = basically just foregrounding the app: the process and HomeActivity are already created | ||
=== MAIN/VIEW | === Path: MAIN/VIEW === | ||
"Path" refers to the code path taken for this start up. We name these after the <code>action</code> inside the <code>Intent</code>s received by the app [https://developer.android.com/reference/android/content/Intent#ACTION_MAIN such as <code>ACTION_MAIN</code>] that tell the app what to do: | |||
* MAIN = a start up where the app icon was clicked. If there are no existing tabs, the homescreen will be shown. If there are existing tabs, the last selected one will be restored | * MAIN = a start up where the app icon was clicked. If there are no existing tabs, the homescreen will be shown. If there are existing tabs, the last selected one will be restored | ||
* VIEW = a start up where a link was clicked. In the default case, a new tab will be opened and the URL will be loaded | * VIEW = a start up where a link was clicked. In the default case, a new tab will be opened and the URL will be loaded | ||
Caveat: if an <code>Intent</code> is invalid, we may end up on a different screen (and thus taking a different code path) than the one specified by the <code>Intent</code>. For example, an invalid VIEW <code>Intent</code> may instead be treated as a MAIN <code>Intent</code>. | |||