Policy will have to change for that to happen with Apple stuff
Will be looking for what you were talking about.
Squeak iPhone app. development was re-enabled on the iPhone after Apple goofed by making their developer license too restrictive in an effort to kill off Flash on the iPhone. The caveat was that any app. had to ban the downloading of executable code. The implication, at least for me, was that any Squeak app. had to disallow opening a system browser or workspace window, because the user might execute some code to download other code. The objective is predictable system maintenance, no unauthorized code on devices. It's like a locked down PC, except Apple is the IT department...
The way that the XO Laptop dealt with this was it had a "reset" button. It was more like a "panic" button. The entire system was open source, so students were encouraged to change it. However, if they unintentionally screwed up something, making the system unworkable, they could hit that button and it would essentially do a "factory reset" that would restore the software (I believe this included the source code) to its original state. A blunt instrument, but it at least makes it less dangerous to modify your own system, because you have an "escape hatch" from your own screw-ups.
