It proposes the development of a multimodal, intelligent user interface in the form of an open eyewear platform whose hardware comprises a graphics display, camera, eye tracker, mic, earphones, microvibrators, temperature and pulse sensors, proximity sensors, and IMU, powered by a self-contained computer with wireless networking. The team will address the design, implementation, and evaluation of the system hardware and software, user interface, and representative applications intended to address the needs of health professionals, disabled users, and general users.Strengths:The project will develop an intelligent eyewear system comprising open hardware and software. Making this an open design allows additions and extensions that would not be possible with vendor-proprietary systems, including a software execution environment that does not impose the restrictions of, for example, the Google Mirror API (https://developers.google.com/glass/). Future offerings from other vendors cannot be assessed at this point, but the proposed eGlasses indicate potential progress beyond what has been published. Thus, the eGlasses platform could be an important benefit to the mobile and wearable computing research community.The hardware incorporates additional sensors beyond those available in early commercial offerings such as the Google Glass “Explorer” edition and Vuzix M100: eye tracker and temperature/pulse/proximity sensors. These make it possible for project members and external researchers to investigate the design of novel interaction techniques that range significantly beyond what can be supported by currently announced commercial products.The proposed healthcare and assistive applications are realistic and of societal interest, and are potentially high payoff.That the current design is far less visually appealing than commercial ones is less of an issue for research (rather than productization) and allows the incorporation of larger batteries, enabling more ambitious use scenarios.The level of technical detail in the proposal for WP3-4 gives good confidence in the modular approach taken for I/O development, which should also reduce risk of overall failure should one component prove problematic to develop.The balance of partner load across the workplan is appropriate. The concurrency of the initial requirement gathering exercise (WP2) and the requirements capture for the demonstrators (WP6,WP7) should ensure cross-pollination of ideas to ensure no unexpected integration problems.