Evinced
From a QA test case to a merged pull request in about 15 minutes.
I build the checks that catch keyboard and missing-label problems, and I fixed Flutter accessibility in the engine so a cross-platform release could ship. Then I set up the AI workflow the team uses every day.
Problem
Evinced has to catch real accessibility issues on native iOS and on Flutter-on-iOS. That needed engine-level fixes, not another wrapper. The team also was not using AI tooling, so a screen still took days to go from a test case to a pull request.
What I did
I researched keyboard and visible-label validation, and I fixed Flutter accessibility in the engine so a cross-platform release could ship. Alongside that I ran an 8-week rollout: Cursor rules, AGENTS.md, skills, and a short path from spec to plan to review.
Before generation
Context and the specification
After generation
Tests and a separate review
Before merge
A person approves the change
- about15 minQA test case to a merged pull request, down from 2 to 4 days
- 100%of the iOS team using AI daily, up from none
- about75 hsaved each week
“Can be trusted to handle complex initiatives from research and planning through implementation and delivery.”