>the primary UI and software stack were very locked off Nothing's really locked off. The filesystem is fully accessible, the file format is not obfuscated in a

>the primary UI and software stack were very locked off Nothing's really locked off. The filesystem is fully accessible, the file format is not obfuscated in any way and was easily reverse-engineered (there are several libraries for reading/writing the format now), and it's possible to interact with the main "xochitl" UI by intercepting/simulating events and drawing to the framebuffer after the main UI draws. It is true that they haven't opened the UI framework behind "xochitl", but I'd guess that it's probably pretty rudimentary and not particularly general given how simple "xochitl" is. Most third party apps for the device just use QT or draw directly to the framebuffer. (And why not use QT?) >It's clear the developer intends for the device to be heavily restricted by default They want the UI for average users to be fairly restricted, but IMHO they're intentionally leaving it open to people to hack on it. The CTO even has a crosswords app up on Github.