{"_id":"561c3b3400e13c0d00936286","__v":6,"githubsync":"","project":"561ae15363ef571900ca68d3","category":{"_id":"561ae15563ef571900ca68d7","version":"561ae15463ef571900ca68d6","pages":["561ae15563ef571900ca68d9","561af2911a10ea0d002387f7","561af4a878436c19009e87d8","561c3b3400e13c0d00936286","56327cdb38f8aa0d00d30f6e","566b532068eba90d009cac6c","5672df821e18b60d00b04a32"],"project":"561ae15363ef571900ca68d3","__v":7,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-10-11T22:23:17.043Z","from_sync":false,"order":0,"slug":"documentation","title":"Documentation"},"user":"561ae13963ef571900ca68d2","version":{"_id":"561ae15463ef571900ca68d6","project":"561ae15363ef571900ca68d3","__v":3,"createdAt":"2015-10-11T22:23:16.492Z","releaseDate":"2015-10-11T22:23:16.492Z","categories":["561ae15563ef571900ca68d7","56255c864dcb400d00ff4427","56326faf45f2cb0d006be3f1"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2015-10-12T22:59:00.207Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":6,"body":"The AppHub dashboard provides a visual interface for uploading, configuring, and deploying builds to your app. To get started, simply sign in with GitHub and create an app.\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/rTbwPj8dRcWhRNbFnQjP_dashboard_screenshot.png\",\n        \"dashboard_screenshot.png\",\n        \"1030\",\n        \"534\",\n        \"#345a6a\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nAppHub “apps” represent the apps that you distribute to your users. In general, developers create one AppHub “app” for their iOS app, however, if you have multiple version of your app (eg. a production version and a testing version), it may make sense to have separate AppHub apps for each.\n\n---\n\n##Getting Started\n\nWhen you create an app, the quickstart guide provides step-by-step instructions for integrating the AppHub SDK and connecting your first device.\n\nOnce you have connected a device, the indicator in step 5 of the quickstart guide will turn green and you can proceed to uploading builds.\n\n---\n\n##Uploading Builds\n\nBuilds represent versions of your app. When you upload a new build, the default configuration option is “none” which means your build won't be distributed to any users. In order to deploy your build to your users, click “configure” and select a deployment strategy. “All” deployments go to all of your users. If you have multiple builds with the “all” deployment strategy, users will get the newest build you have uploaded.\n\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/yYuQm8aRc2M3cgR1CSkG_build_modal.png\",\n        \"build_modal.png\",\n        \"574\",\n        \"397\",\n        \"#0a83a7\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\n“Debug” builds are distributed to devices that have debug mode enabled through the AppHub SDK. Typically, developers enable the debug option on devices used for testing (eg. their team's devices). [See the configuration docs for more information](http://docs.apphub.io/docs/getting-started#section-debug-builds).\n\n---\n\n## JavaScript and Native Versioning\n\nIt is important for AppHub developers to understand the relationship between iOS app versions and build versions. When you make changes to native code, and change the iOS version of your app, you risk making your app incompatible with javascript code made for earlier native versions. When you upload an IPA to AppHub, we determine the native version of your app associated with the javascript you intend to update. By default, AppHub will then only distribute your javascript update to devices running that native version of your app.\n\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/Ch4blRYYR1Se1xC1QRj2_multiple_versions.png\",\n        \"multiple_versions.png\",\n        \"932\",\n        \"388\",\n        \"#7e2a0a\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]\nIf, however, you wish specify additional native versions of your app to which a build can be distributed, you must enable “Advanced Deployment Settings” in your project's settings. You can access this by clicking the \"settings\" tab within your project. Once this setting is enabled, click “configure” on the build you wish to deploy, and you will have the option to specify additional native versions for that build.\n\n---\n\n##Adding Collaborators\n\nIf you are collaborating on an app with other developers, you can add collaborators to your app from either the home screen, or the app's settings page (by clicking on the gear in the upper right corner of the app preview). Collaborators can upload and deploy new builds, edit project data, and access usage information, but are not able to invite/remove other collaborators, edit billing information or delete projects.\n\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/XlIN8oRIRL2U0YjGcTKh_collaborators.png\",\n        \"collaborators.png\",\n        \"616\",\n        \"381\",\n        \"#1b6152\",\n        \"\"\n      ]\n    }\n  ]\n}\n[/block]","excerpt":"Manage and monitor your AppHub builds.","slug":"using-the-dashboard","type":"basic","title":"Using the Dashboard"}

Using the Dashboard

Manage and monitor your AppHub builds.

The AppHub dashboard provides a visual interface for uploading, configuring, and deploying builds to your app. To get started, simply sign in with GitHub and create an app. [block:image] { "images": [ { "image": [ "https://files.readme.io/rTbwPj8dRcWhRNbFnQjP_dashboard_screenshot.png", "dashboard_screenshot.png", "1030", "534", "#345a6a", "" ] } ] } [/block] AppHub “apps” represent the apps that you distribute to your users. In general, developers create one AppHub “app” for their iOS app, however, if you have multiple version of your app (eg. a production version and a testing version), it may make sense to have separate AppHub apps for each. --- ##Getting Started When you create an app, the quickstart guide provides step-by-step instructions for integrating the AppHub SDK and connecting your first device. Once you have connected a device, the indicator in step 5 of the quickstart guide will turn green and you can proceed to uploading builds. --- ##Uploading Builds Builds represent versions of your app. When you upload a new build, the default configuration option is “none” which means your build won't be distributed to any users. In order to deploy your build to your users, click “configure” and select a deployment strategy. “All” deployments go to all of your users. If you have multiple builds with the “all” deployment strategy, users will get the newest build you have uploaded. [block:image] { "images": [ { "image": [ "https://files.readme.io/yYuQm8aRc2M3cgR1CSkG_build_modal.png", "build_modal.png", "574", "397", "#0a83a7", "" ] } ] } [/block] “Debug” builds are distributed to devices that have debug mode enabled through the AppHub SDK. Typically, developers enable the debug option on devices used for testing (eg. their team's devices). [See the configuration docs for more information](http://docs.apphub.io/docs/getting-started#section-debug-builds). --- ## JavaScript and Native Versioning It is important for AppHub developers to understand the relationship between iOS app versions and build versions. When you make changes to native code, and change the iOS version of your app, you risk making your app incompatible with javascript code made for earlier native versions. When you upload an IPA to AppHub, we determine the native version of your app associated with the javascript you intend to update. By default, AppHub will then only distribute your javascript update to devices running that native version of your app. [block:image] { "images": [ { "image": [ "https://files.readme.io/Ch4blRYYR1Se1xC1QRj2_multiple_versions.png", "multiple_versions.png", "932", "388", "#7e2a0a", "" ] } ] } [/block] If, however, you wish specify additional native versions of your app to which a build can be distributed, you must enable “Advanced Deployment Settings” in your project's settings. You can access this by clicking the "settings" tab within your project. Once this setting is enabled, click “configure” on the build you wish to deploy, and you will have the option to specify additional native versions for that build. --- ##Adding Collaborators If you are collaborating on an app with other developers, you can add collaborators to your app from either the home screen, or the app's settings page (by clicking on the gear in the upper right corner of the app preview). Collaborators can upload and deploy new builds, edit project data, and access usage information, but are not able to invite/remove other collaborators, edit billing information or delete projects. [block:image] { "images": [ { "image": [ "https://files.readme.io/XlIN8oRIRL2U0YjGcTKh_collaborators.png", "collaborators.png", "616", "381", "#1b6152", "" ] } ] } [/block]