{"_id":"5923c772a91ac40f0041e26a","user":"55d535835082980d0009c965","__v":1,"category":{"_id":"55e75b7ae06f4b190080dbff","__v":10,"project":"55d535ca988e130d000b3f5c","version":"55d535cb988e130d000b3f5f","pages":["5637e17197666c0d008656a5","569591a4fcb1032d0089e037","569622eafe18811700c9c19b","5696c9588560a60d00e2c1e0","569709ca0b09a41900b2442b","5697129ac8ded91700307b77","5697190a59a6692d003fad6a","5697192969393517000c8280","569f11908f6d4b0d00f13bb2","56a0030b5b981c2b00383df0"],"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-09-02T20:26:34.258Z","from_sync":false,"order":4,"slug":"frame-platform","title":"Frame Platform"},"parentDoc":null,"project":"55d535ca988e130d000b3f5c","version":{"_id":"55d535cb988e130d000b3f5f","__v":13,"project":"55d535ca988e130d000b3f5c","hasDoc":true,"hasReference":false,"createdAt":"2015-08-20T02:04:59.052Z","releaseDate":"2015-08-20T02:04:59.052Z","categories":["55d535cc988e130d000b3f60","55d6b238d2a8eb1900109eef","55d6b4f3250d7d0d004274cd","55d7967960fc730d00fc2852","55da9804e835f20d009fc5d0","55e75b1de06f4b190080dbfd","55e75b39e06f4b190080dbfe","55e75b7ae06f4b190080dbff","564f5a4e33082f0d001bb709","570fb64aa38d470e0060cbff","586d0dd89a854123001acd65","586d0e3b9a854123001acd66","5a613b28da07540012e8ca4a"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":["59e13912a7c18b001afa4005"],"next":{"pages":[],"description":""},"createdAt":"2017-05-23T05:24:02.813Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"settings":"","results":{"codes":[]},"auth":"required","params":[],"url":""},"isReference":false,"order":3,"body":"With Frame Platform, you have a number of controls that let you tune exactly how users will experience your application running in a browser. You can set these features using the \"Properties\" of each app and the \"Session Settings.\"\n[block:api-header]\n{\n  \"title\": \"Application Properties\"\n}\n[/block]\nClick on the arrow next to the app icon in the Dashboard and select \"Properties\":\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/ab8d3dd-Screen_Shot_2017-04-18_at_6.42.16_PM.png\",\n        \"Screen Shot 2017-04-18 at 6.42.16 PM.png\",\n        185,\n        270,\n        \"#edf0ef\"\n      ]\n    }\n  ]\n}\n[/block]\nHere you can change the title and icon for the application, plus choose a start mode:\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/04cec9b-Screen_Shot_2017-05-22_at_10.26.34_PM.png\",\n        \"Screen Shot 2017-05-22 at 10.26.34 PM.png\",\n        1448,\n        958,\n        \"#e4edec\"\n      ]\n    }\n  ]\n}\n[/block]\n* **Start mode:** lets you configure hot start, warm start, or cold start options for an app. This is great for single app use cases, where you want to minimize the time from clicking on an app to running it by pre-launching it in the background before the user connects (hot start).\n\n     - Hot start - the app is started when the host instance boots, and then minimizes. It then waits for a user to request a session. After a session, the app is closed and launched again to be ready for the next user.\n\n     - Warm start - the app is started and then killed when machine boots. This is done to \"warm it  up\". Once you start it once, Windows will cache executables and other binary files in memory, so the next start will be faster.\n\n     - Cold start - the app is started only when someone requests a session with it.\n\n* **Advanced Options:** if you have this option enabled for your account, you can set these on a per-app basis by scrolling down on the App Properties page. This lets you set advanced application parameters and append an app launch path with custom launch arguments/parameters.\n\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/a03b350-Screen_Shot_2017-05-22_at_10.34.06_PM.png\",\n        \"Screen Shot 2017-05-22 at 10.34.06 PM.png\",\n        1444,\n        1082,\n        \"#e4edec\"\n      ],\n      \"border\": true\n    }\n  ]\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"Session Settings\",\n  \"body\": \"You can customize many aspects of the way your users' sessions will behave by editing \\\"Session Settings.\\\" These settings let you configure how the session will behave when users launch any application from the Launchpad. For example, you can choose to show or hide the distance and latency measurements shown in the bottom of the session status bar. If you would like to read more, please reference the documentation in Frame for Business [here](https://docs.fra.me/docs/configure-session-settings).\"\n}\n[/block]","excerpt":"Control your end users' experience with custom session settings","slug":"set-custom-app-properties-new","type":"basic","title":"Set custom app properties"}

Set custom app properties

Control your end users' experience with custom session settings

With Frame Platform, you have a number of controls that let you tune exactly how users will experience your application running in a browser. You can set these features using the "Properties" of each app and the "Session Settings." [block:api-header] { "title": "Application Properties" } [/block] Click on the arrow next to the app icon in the Dashboard and select "Properties": [block:image] { "images": [ { "image": [ "https://files.readme.io/ab8d3dd-Screen_Shot_2017-04-18_at_6.42.16_PM.png", "Screen Shot 2017-04-18 at 6.42.16 PM.png", 185, 270, "#edf0ef" ] } ] } [/block] Here you can change the title and icon for the application, plus choose a start mode: [block:image] { "images": [ { "image": [ "https://files.readme.io/04cec9b-Screen_Shot_2017-05-22_at_10.26.34_PM.png", "Screen Shot 2017-05-22 at 10.26.34 PM.png", 1448, 958, "#e4edec" ] } ] } [/block] * **Start mode:** lets you configure hot start, warm start, or cold start options for an app. This is great for single app use cases, where you want to minimize the time from clicking on an app to running it by pre-launching it in the background before the user connects (hot start). - Hot start - the app is started when the host instance boots, and then minimizes. It then waits for a user to request a session. After a session, the app is closed and launched again to be ready for the next user. - Warm start - the app is started and then killed when machine boots. This is done to "warm it up". Once you start it once, Windows will cache executables and other binary files in memory, so the next start will be faster. - Cold start - the app is started only when someone requests a session with it. * **Advanced Options:** if you have this option enabled for your account, you can set these on a per-app basis by scrolling down on the App Properties page. This lets you set advanced application parameters and append an app launch path with custom launch arguments/parameters. [block:image] { "images": [ { "image": [ "https://files.readme.io/a03b350-Screen_Shot_2017-05-22_at_10.34.06_PM.png", "Screen Shot 2017-05-22 at 10.34.06 PM.png", 1444, 1082, "#e4edec" ], "border": true } ] } [/block] [block:callout] { "type": "info", "title": "Session Settings", "body": "You can customize many aspects of the way your users' sessions will behave by editing \"Session Settings.\" These settings let you configure how the session will behave when users launch any application from the Launchpad. For example, you can choose to show or hide the distance and latency measurements shown in the bottom of the session status bar. If you would like to read more, please reference the documentation in Frame for Business [here](https://docs.fra.me/docs/configure-session-settings)." } [/block]