Hello, I would like to start by saying: I'm very excited to see this project getting off the ground, and with an excellent start in both hardware and software. While I lack the experience needed for tasks such as improving the layout of hardware or refining user experience, I hope I can at least contribute to the software end of things with my experience as a compsci student (currently involved in machine learning research).
I may be mistaken, but one problem I've noticed with the current design is its dependence on a small number of hardware buttons to interface with software running on the OpenEyeTap. This seems unfortunately limiting, as it not only restricts the ease and functionality of many applications, but it also makes it near impossible to create a way to switch applications, restricting the device to a single purpose at once.
These concerns were addressed in the UX thread with the proposal of an IMU-based reticle and a bluetooth microphone, and while I think those proposals are excellent and would make for a solid final means of interfacing with the device, they also don't work with the current default hardware configuration, are dependent on environmental variables that could hinder use (particularly sound and the potential for user instructions to be drowned out), and could introduce overhead that could spread thin the already limited processing power of the Raspberry Pi Zero- though I'm admittedly unsure of how bad this impact might be.
Instead, for the current default hardware, has there been any consideration of the option of a being able to interface with the EyeTap from another device such as a smart phone? The Pi Zero W is notable for its bluetooth support, and so it would be relatively easy to have a sort of mobile interface to send instructions to start or stop certain applications, or to ease in tasks such connecting the device to WiFi networks. This bluetooth connectivity could also enable applications running on the EyeTap to utilize it for their own interfacing purposes, such as having software alternatives to hardware buttons. Of course, other methods of connection are also possible, but I strive to ensure my solution is wireless and doesn't prevent the ability to connect online which some existing software depends on.
These are just some thoughts I had on how to expand the usability of the current design. While it's far from my specialty, I would be personally interested in taking a shot at making an interface like this happen once I've gotten my hands on the hardware. For now, I'd love to hear other people's thoughts on the idea.