Goals
Available: Scenic takes full advantage of OTP supervision trees to create applications that are fault-tolerant, self-healing, and highly available under adverse conditions.
Small and Fast: The only core dependencies are Erlang/OTP and OpenGL.
Self Contained: “Never trust a device if you don’t know where it keeps its brain.” The logic to run a device should be on the device and it should remain operational even if the service it talks to becomes unavailable.
Maintainable: Each device knows how to run itself. This lets teams focus on new products and only updating the old ones as the business needs.
Remotable: Scenic devices know how to run themselves, but can still be accessed remotely. Remote traffic attempts to be as small as possible so it can be used over the Internet, cellular modems, Bluetooth, etc. This is actively under development and coming soon.
Reusable: Collections of UI can be packaged up for reuse with, and across applications. I expect to see Hex packages of controls, graphs, and more available for Scenic applications.
Flexible: Scenic uses matrices similar to game development to position everything. This makes reuse, scale, positioning and more very flexible and simple.
Secure: Scenic is designed with an eye towards security. For now, the main effort is to keep it simple. No browser, Javascript, and other complexity presenting vulnerabilities. There will be much more to say about security later.