Core chat experience
Rebuilt the core chat experience and shipped the replacement to production.
THE STORY
Building the product.
The problem
An AI app builder depends on much more than the generated output. Its chat, editing tools, loading experience, and mobile surface all need to work together as a reliable product.
The approach
Own product surfaces end to end, improve the foundations, and build tools that let more of the team make changes. My work spans production interfaces, React Native mobile, performance, and the design system.
The useful parts.
My contributions across the product.
Emergent on mobile
Built the mobile app as its sole developer, bringing the web platform to React Native and Expo.
Direct visual editing
Built a Visual Edit Mode for making UI changes without spending AI credits, alongside work on the product’s light theme.
Tools that help the team ship
Built a landing-page editor, an AI pull-request review tool, and a design system that helps designers ship UI fixes.
What I shipped
A closer look at the product areas I have built and shipped at Emergent.
AREA 01 OF 04
The everyday product surface
Rebuilt the core chat, worked on load performance, and shipped a light theme. These changes improve the experience users return to throughout a build.
THE OUTCOMEA stronger foundation for the main product workflow.
Behind the build.
Decisions, boundaries, and the current state of the work.
This is a selection of my engineering work at Emergent, not an independently owned product. The mobile app was my sole-developer responsibility; the broader platform is the work of the Emergent team.
Take a closer look.
Open the product or explore its source material.