If you literally want your application to start "when the OS boots up," then the answer is: you cannot.
Otherwise, if this is normal, if your application starts when the user logs in, add "background" manifest file.
It starts Chrome early and closes late, so applications and extensions can have a longer life.
If any installed hosted application, packaged application, or extension has "background" permission, Chrome starts (invisibly) as soon as the user logs into his computer - before the user starts Chrome. Setting the background also forces Chrome to continue to work (even after closing the last window) until the user explicitly quits Chrome.
The background permission is only available for hosted apps of legacy packaged apps and extensions, not the Chrome app .
If you want to use the "background" resolution in a Chrome application, then the only way to do this is to get it whitelisted. This can be done using the --whitelisted-extension-id flag:
chromium --whitelisted-extension-id=[YOUREXTENSIONID - 32 chars ap]
You can only have one added value using the command line, so it should only be used for testing. If you want to publish your app with background resolution, you're out of luck. Permission was intentionally disabled by the Chromium team, see https://code.google.com/p/chromium/issues/detail?id=163770 .
Rob w source share