Speak Naturally
Users should not need to memorize rigid commands or adapt to machine-like syntax.
ROLE
Co-Founder & Design Lead
TIMELINE
January 2025 - Present
TEAM
1 PM,
1 Engineer,
1 Designer (me!)
SKILLS
Product Design, Development, User Research, Collaboration
ROLE
Co-Founder & Design Lead
TIMELINE
January 2025 - Present
TEAM
1 PM,
1 Engineer,
1 Designer (me!)
SKILLS
Product Design, Development, User Research, Collaboration
ROLE
Co-Founder & Design Lead
TIMELINE
January 2025 - Present
TEAM
1 PM,
1 Engineer,
1 Designer (me!)
SKILLS
Product Design, Development, User Research, Collaboration
OVERVIEW
We are designing and building an AI-driven workspace that lets users dictate math naturally and explore relationships visually. The project blends research, design, and voice interfaces to make math more accessible and focused on understanding, not mechanics.
We are designing and building an AI-driven workspace that lets users dictate math naturally and explore relationships visually. The project blends research, design, and voice interfaces to make math more accessible and focused on understanding, not mechanics.
We are designing and building an AI-driven workspace that lets users dictate math naturally and explore relationships visually. The project blends research, design, and voice interfaces to make math more accessible and focused on understanding, not mechanics.
OPPORTUNITY
Typing math is frustrating and presents real challenges for students with fine motor disabilities. But it's not only users with accessibility needs, writing precise mathematics is difficult for everyone.
Typing math is frustrating and presents real challenges for students with fine motor disabilities. But it's not only users with accessibility needs, writing precise mathematics is difficult for everyone.
Typing math is frustrating and presents real challenges for students with fine motor disabilities. But it's not only users with accessibility needs, writing precise mathematics is difficult for everyone.

WHY THIS MATTERS
This project began with a personal and immediate problem. Our co-founder was highly capable in mathematics, but a wrist injury made it painful and difficult to physically write equations. Despite having the knowledge and ability to succeed, the act of writing became a barrier.
This project began with a personal and immediate problem. Our co-founder was highly capable in mathematics, but a wrist injury made it painful and difficult to physically write equations. Despite having the knowledge and ability to succeed, the act of writing became a barrier.
This project began with a personal and immediate problem. Our co-founder was highly capable in mathematics, but a wrist injury made it painful and difficult to physically write equations. Despite having the knowledge and ability to succeed, the act of writing became a barrier.

SOLUTION
We designed a hands-free math tool that allows users to create and edit mathematical expressions using voice. Instead of relying on keyboards, equation editors, or handwriting, users can speak naturally while the system converts their input into properly formatted math in real time.
We designed a hands-free math tool that allows users to create and edit mathematical expressions using voice. Instead of relying on keyboards, equation editors, or handwriting, users can speak naturally while the system converts their input into properly formatted math in real time.
We designed a hands-free math tool that allows users to create and edit mathematical expressions using voice. Instead of relying on keyboards, equation editors, or handwriting, users can speak naturally while the system converts their input into properly formatted math in real time.
Although still in an early stage, the project has already generated strong momentum across research, funding, and institutional interest.
Although still in an early stage, the project has already generated strong momentum across research, funding, and institutional interest.
Although still in an early stage, the project has already generated strong momentum across research, funding, and institutional interest.

STARTING FROM ZERO
When we began, we didn't have an established interaction model for voice-driven mathematical input. Before designing interfaces, we first needed to understand how users naturally speak math, where existing tools created friction, and what a hands-free workflow should actually feel like.
When we began, we didn't have an established interaction model for voice-driven mathematical input. Before designing interfaces, we first needed to understand how users naturally speak math, where existing tools created friction, and what a hands-free workflow should actually feel like.
When we began, we didn't have an established interaction model for voice-driven mathematical input. Before designing interfaces, we first needed to understand how users naturally speak math, where existing tools created friction, and what a hands-free workflow should actually feel like.
RESEARCH
As our understanding of the problem space evolved, we wanted a structured way to synthesize our findings and evaluate existing approaches. We formalized this work through a research paper that explored opportunities for voice-driven mathematical input and reviewed the limitations of current solutions. The paper was later accepted and presented at ACM ASSETS 2025.
As our understanding of the problem space evolved, we wanted a structured way to synthesize our findings and evaluate existing approaches. We formalized this work through a research paper that explored opportunities for voice-driven mathematical input and reviewed the limitations of current solutions. The paper was later accepted and presented at ACM ASSETS 2025.
As our understanding of the problem space evolved, we wanted a structured way to synthesize our findings and evaluate existing approaches. We formalized this work through a research paper that explored opportunities for voice-driven mathematical input and reviewed the limitations of current solutions. The paper was later accepted and presented at ACM ASSETS 2025.

PRODUCT PRINCIPLES
We explored many possibilities, but over time certain principles consistently emerged and guided our decisions.
We explored many possibilities, but over time certain principles consistently emerged and guided our decisions.
We explored many possibilities, but over time certain principles consistently emerged and guided our decisions.
Users should not need to memorize rigid commands or adapt to machine-like syntax.
Math input should support thinking speed instead of interrupting it.
Real-time rendering helps users build trust and confidence while speaking.
Editing equations should feel lightweight and recoverable rather than punishing.
The experience should remain usable for people with different physical abilities and interaction needs.
CURRENT STATE
Assistivity is now live and in the hands of real users, with onboarding and core workspace experiences shipped.
Assistivity is now live and in the hands of real users, with onboarding and core workspace experiences shipped.
Assistivity is now live and in the hands of real users, with onboarding and core workspace experiences shipped.
Motion isn't just for the hero moments. Across the app bar, sidebar, and everyday actions like saving and exporting, small animations help the product feel responsive, clear, and in flow with the user.
Motion isn't just for the hero moments. Across the app bar, sidebar, and everyday actions like saving and exporting, small animations help the product feel responsive, clear, and in flow with the user.
Motion isn't just for the hero moments. Across the app bar, sidebar, and everyday actions like saving and exporting, small animations help the product feel responsive, clear, and in flow with the user.
THE MATH NODE
The math node is the core interaction of Assistivity, where spoken input becomes structured math in real time. Below is a closer look at how it works and the details that shape the experience.
The math node is the core interaction of Assistivity, where spoken input becomes structured math in real time. Below is a closer look at how it works and the details that shape the experience.
The math node is the core interaction of Assistivity, where spoken input becomes structured math in real time. Below is a closer look at how it works and the details that shape the experience.

Each node is made up of two parts: a top bar for quick actions like copying, recoloring, and deleting, and the node body itself, where users press the microphone to start speaking their equation.

Each node is made up of two parts: a top bar for quick actions like copying, recoloring, and deleting, and the node body itself, where users press the microphone to start speaking their equation.

As you speak, your equation appears as plain text inside the node, giving you a chance to review what was heard before committing to it.

As you speak, your equation appears as plain text inside the node, giving you a chance to review what was heard before committing to it.

Once submitted, the plain text transforms into a properly formatted equation, structured, readable, and ready to build on.

Once submitted, the plain text transforms into a properly formatted equation, structured, readable, and ready to build on.
EQUATION CONTROLS
Every rendered equation can be flipped to its underlying LaTeX, giving users a way to inspect, copy, or verify the exact structure behind what they see.
Every rendered equation can be flipped to its underlying LaTeX, giving users a way to inspect, copy, or verify the exact structure behind what they see.
Every rendered equation can be flipped to its underlying LaTeX, giving users a way to inspect, copy, or verify the exact structure behind what they see.

Equations can be edited the same way they were created, by speaking. This keeps corrections lightweight and in flow, without forcing users into a keyboard or equation editor.
Equations can be edited the same way they were created, by speaking. This keeps corrections lightweight and in flow, without forcing users into a keyboard or equation editor.
Equations can be edited the same way they were created, by speaking. This keeps corrections lightweight and in flow, without forcing users into a keyboard or equation editor.

A quick control lets users add a new equation directly below the current one, treating it as the next step. It keeps the flow of thinking uninterrupted between related equations.
A quick control lets users add a new equation directly below the current one, treating it as the next step. It keeps the flow of thinking uninterrupted between related equations.
A quick control lets users add a new equation directly below the current one, treating it as the next step. It keeps the flow of thinking uninterrupted between related equations.

Spoken math isn't always precise. When an equation could be interpreted more than one way, the node highlights it and offers the possible options, letting users pick the one they meant.
Spoken math isn't always precise. When an equation could be interpreted more than one way, the node highlights it and offers the possible options, letting users pick the one they meant.
Spoken math isn't always precise. When an equation could be interpreted more than one way, the node highlights it and offers the possible options, letting users pick the one they meant.

When something can't be rendered, the node shifts into an error state that surfaces what went wrong, so users can recover quickly without guessing.
When something can't be rendered, the node shifts into an error state that surfaces what went wrong, so users can recover quickly without guessing.
When something can't be rendered, the node shifts into an error state that surfaces what went wrong, so users can recover quickly without guessing.

REFLECTION
This project shifted how I think about accessibility in design. Rather than treating it as a constraint layered onto a finished experience, I learned to treat it as a starting point, one that often leads to better, more intentional design for everyone.
This project pushed me to move beyond designing from intuition and into designing from research. Formalizing our thinking through a published paper reframed how I approach ambiguity, from something to solve quickly, to something worth studying carefully before shaping a product around it.
This project shifted how I think about accessibility in design. Rather than treating it as a constraint layered onto a finished experience, I learned to treat it as a starting point, one that often leads to better, more intentional design for everyone.
This project pushed me to move beyond designing from intuition and into designing from research. Formalizing our thinking through a published paper reframed how I approach ambiguity, from something to solve quickly, to something worth studying carefully before shaping a product around it.
Designing for voice-driven math meant working without an established playbook. It taught me to lean on principles instead of patterns, and to trust that a strong interaction model can emerge from ambiguity when the thinking behind it is clear.
Designing for voice-driven math meant working without an established playbook. It taught me to lean on principles instead of patterns, and to trust that a strong interaction model can emerge from ambiguity when the thinking behind it is clear.