I disagree that the documentation is incorrect. Chrome OS kiosk mode is intended for apps that rely on the security of the device to ensure that the content is secure, etc. https://bugs.chromium.org/p/chromium/issues/detail?id=656620 is a valid issue and needs to be fixed.

Re comment #1: What makes you believe that Kiosk Mode is supposed to provide these guarantees (other than the referenced documentation)?

We are (and always have been) wary about client-enforced security designs since relying on the integrity of a client device is generally fragile. FWIW, the Kiosk Apps infrastructure has allowed developer mode from the start, and developers do actually rely on developer mode to debug their kiosk applications.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

atwilson@, rkc@ mentioned you now own kiosk apps - can you help find an owner for this?

There's nothing to do here AFAICT. Yes, we could warn developers that "hey, if you leave your device in dev mode, people can do stuff with it" but it's not clear this is a problem in practice. We aren't going to update every help center article on every topic to say "btw, if your device is in dev mode then all bets are off".