Worn: Smart Glasses Hackathon will bring developers to New York City College of Technology in Downtown Brooklyn on November 20–21, 2026, for an overnight build using MicroLumin smart glasses. Waftech and localhost:nyc are presenting the event, with Cornell Tech AI Society as presenting partner. The opportunity is to put software in a person's field of view and discover how much attention it deserves.
The organizers plan SDK instruction, collaborative building and demonstrations on the actual devices. Hardware founders, mobile developers, embedded engineers and designers have a common problem to examine here: an interface can perform its function and still get in the wearer's way. Worn's proposed applications, from captions to hands-free work, give that problem concrete shape.
Admission is free, and registration requires host approval. The official event site lists City Tech at 300 Jay St, with doors opening Friday at 5:30 PM EST and the event wrapping Saturday at 6 PM EST. Attendees should confirm access instructions through registration and check current operating rules before arriving.
Worn's challenge themes include navigation, translation, accessibility, heads-up assistants and AI informed by the camera's view. Each invites a different kind of judgment about what a wearer needs to see. A caption that arrives too late and a direction that hangs around too long can both miss the moment, even when the underlying software runs exactly as designed.
That is the useful tension behind a wearable build weekend. A phone application can ask for a deliberate visit to a screen; a display near the eye shares space with the activity already underway. For builders, the question becomes how to support that activity while keeping the person's surroundings and intention central. Adding another feature can make the design problem harder.
MicroLumin describes its business around modular AI and AR glasses and provides a developer-ecosystem entry on its website. At Worn, the company is supplying hardware and SDK support, according to the organizers. Access to a device creates an opportunity to examine legibility, timing and interaction choices directly, rather than leaving those questions inside a presentation.
The proposed accessibility and professional-workflow themes also call for restraint in how prototypes are described. An overnight demonstration can expose a promising interaction or an awkward assumption. Any claim about dependable use in a workplace or an assistive setting would require evidence beyond this event, and developers should keep that distinction visible when explaining what they have built.
The presenter mix connects community organizing with hardware manufacturing. Waftech makes wafer-handling equipment, while localhost:nyc describes its mission around cultivating New York's builder and founder community. Their roles in Worn put a practical manufacturing connection beside the work of assembling people who want to build.
Cornell Tech AI Society, the presenting partner, identifies itself as a student-run community at Cornell University's New York City campus. Its activities include workshops, discussion and hackathons. That partnership should be understood precisely: the current event venue is City Tech in Brooklyn, even though some older third-party calendars still describe Cornell Tech as the location.
Somya Gupta, Stephen Jin, Olivia Iarmak and Vishal Kharker are among the hosts named on the organizer's listing. The value of a room like this depends on what participants do together: explain a use case, compare implementation choices, encounter an unfamiliar constraint and find someone who can help untangle it. A teammate who notices a bad assumption can be more useful than another broad conversation about the future of AI.
For founders and operators, the relevant networking opportunity is therefore closely tied to the build. Device setup, SDK questions and prototype feedback give people something specific to discuss. The event offers a setting for those exchanges; investors, recruiting outcomes, follow-on funding and commercial partnerships should never be treated as included benefits.
Friday's published schedule moves from a 6:35 PM SDK walkthrough to teammate matching at 7 PM and an 8 PM build start. Saturday includes a 10 AM workshop with Dr. Zhaoen Dai, whom the organizers identify as MicroLumin's founder and CEO. Submissions are due at 2 PM, followed by a demo expo and finalist presentations later that afternoon.
That sequence gives the weekend a useful pressure. Developers have to choose which interaction is worth completing before the demonstration arrives. A narrow application that makes one task easier can give observers a clearer basis for feedback than a crowded interface trying to demonstrate every possible use of smart glasses at once.
The on-device format also changes what a team should prepare to explain. Builders can show when information appears, what triggers it and how the wearer returns attention to the surrounding task. Those choices make the product argument inspectable, even when the prototype remains rough. The question of usefulness becomes harder to hide behind a polished slide.
Some official materials differ on team size and the arrangement for device access. The detailed event FAQ describes onsite testing and requires glasses to remain at the venue, while promotional copy uses broader distribution language. Participants should confirm team rules and hardware arrangements with the hosts, particularly when planning around an existing team or a specific testing requirement.
The event site's FAQ also says teams keep ownership of their projects while granting MicroLumin a non-exclusive, royalty-free license with uses that include commercial product development. Anyone planning to submit existing code should read the current terms and consider the permissions attached to that code. The full terms belong in that decision, alongside the technical preparation.
By Saturday's demonstrations, builders should have a more tangible way to discuss an unusually intimate software surface. A caption, prompt or direction will occupy space beside the world a person is already trying to navigate. The work continues in the small decisions about when that information appears, how quietly it helps and when it leaves the wearer alone.
The organizers welcome mobile developers, hardware founders, embedded and computer-vision engineers, and product designers. Prior AR experience is not required; SDK instruction and teammate matching are planned.
Registration requires host approval. Confirm venue access, current team-size rules and hardware arrangements with the organizers because some published details differ; the official schedule lists Friday doors at 5:30 PM EST.
A worn demonstration lets builders and observers examine when information appears, how readable it is and how it affects the surrounding task. Worn plans live device demos after its overnight build.
The official event FAQ describes onsite use and testing and requires the glasses to remain at the venue and be returned. Confirm access arrangements with the hosts rather than assuming a take-home device is included.
The event FAQ says teams retain ownership while granting MicroLumin a non-exclusive, royalty-free license that includes commercial product-development uses. Read the current submission terms and check permissions for any third-party code before submitting.