iOS and Android apps, from onboarding to the first payment, each following its own platform conventions.
✓User flows and wireframes
✓iOS UI that follows Apple's Human Interface Guidelines
✓Android UI that follows Material 3: system back, bottom sheets, Material pickers
✓Offline, error and permission states
✓Interactive, animated prototypes
The phone prototypes on this site are shown in iPhone frames. On Android projects, the same flows are adapted to Material patterns, not copied. Try the Corridor app
02Web apps and dashboards
Web apps and dashboards
Busy SaaS screens that stay easy to read: tables, charts, roles, permissions and settings.
I turn approved designs into responsive front-end code with the animations built in. The proof is on this site: every prototype here is hand-coded in HTML, CSS and JavaScript, not exported from a design tool.
✓Responsive code that matches the approved design
✓Micro-interactions built in, with reduced-motion fallbacks
✓Semantic, keyboard-friendly markup
✓Handoff to your developers, or I build alongside them
When your developers send a prototype, APK or TestFlight build, I check that it looks and behaves as designed, log every issue I find and retest the fixes. You get a release readiness report; your team makes the release call.
✓Prototype, APK and TestFlight builds
✓iOS, Android and browser coverage
✓Build vs design comparison, screen by screen
✓Bug reports with steps, expected vs actual and severity
From this site's source, not a design tool export.
Three short excerpts from the code that runs these pages and prototypes. Full source is available on request.
Count-up stats
Numbers count up once when they scroll into view, then land on the real text so nothing is lost for screen readers or copy and paste.
index.html · motion layer
var countUp = function (el) {
var tn = el.firstChild;
var m = tn.nodeValue.trim().match(/^([^\d]*)(\d+(?:\.\d+)?)([^\d]*)$/);
if (!m) return;
var num = parseFloat(m[2]), dec = (m[2].split('.')[1] || '').length;
var orig = tn.nodeValue, t0 = performance.now();
el.style.fontVariantNumeric = 'tabular-nums'; // digits keep their width
var step = function (now) {
var t = Math.min((now - t0) / 1100, 1);
var e = 1 - Math.pow(1 - t, 3); // ease-out cubic
tn.nodeValue = m[1] + (num * e).toFixed(dec) + m[3];
if (t < 1) requestAnimationFrame(step);
else tn.nodeValue = orig; // end on the real text
};
requestAnimationFrame(step);
};
Hold to approve
A press-and-hold for risky actions in Relay. Letting go cancels, and a two-tap option is there for people who cannot hold.
/work/relay/mobile-app/ · approval sheet
holdStart: function () {
clearInterval(self._rmh);
self._rmh = setInterval(function () {
var h = self.state.rlm_hold + 6; // about 0.85s to fill
if (h >= 100) {
self.setState({ rlm_hold: 100 });
finish(true); // approve the action
return;
}
self.setState({ rlm_hold: h });
}, 50);
},
holdEnd: function () {
if (self.state.rlm_hold < 100) { // let go early: cancel
clearInterval(self._rmh);
self.setState({ rlm_hold: 0 });
}
},
// Can't hold? A two-tap confirm does the same job.
Focus you can see
One rule gives every link, button and field a clear keyboard focus state on light and dark backgrounds.
Every page · accessibility layer
/* Visible focus on every page: a dark ring
plus a lime halo, readable on light and dark */
a:focus-visible,
button:focus-visible,
summary:focus-visible,
input:focus-visible,
select:focus-visible,
textarea:focus-visible,
[tabindex]:focus-visible {
outline: 2px solid #141414 !important;
outline-offset: 2px !important;
box-shadow: 0 0 0 5px #D7FF3B !important;
}
Build testing and QA
What you get from a test round.
Design QA compares the built screens with the approved design. Build testing runs the app itself on iOS, Android and the web. A round covers both, and every issue comes back in the same format.
Sample bug report · Corridor conceptFixed, retest on next build
COR-014
Send button hidden behind the keyboard on small screens
Severity
S2 Major: blocks some users from finishing a transfer
Device
Android 14, small screen (360 px wide), build 0.9.3 from internal testing
Steps
Open Send and choose a recipient.
Tap the amount field.
Type 250.
Expected
The Send button stays visible above the keyboard, as in the design frame.
Actual
The keyboard covers the button. The user has to close the keyboard to continue.
Evidence
Screen recording, plus a screenshot next to the design frame
Severity scale
Every issue gets a severity, so your team fixes the right things first.
S1
Blocker
Crash, data loss or a flow that cannot be finished. Fix before release.
S2
Major
Feature works wrongly or blocks some users. Fix before release unless agreed.
S3
Minor
Visual or copy mismatch, with a workaround. Fix in the next sprint.
S4
Polish
Spacing, motion or alignment details. Batch when there is time.
Device and browser coverage
iOS
✓Current and previous major iOS version
✓A small and a large iPhone
✓TestFlight builds
✓VoiceOver, largest Dynamic Type size, light and dark mode
Android
✓Current and an older supported Android version
✓A small screen and a mid-range phone
✓APK, Google Play internal testing or Firebase App Distribution
✓TalkBack, font scaling and the system back gesture
Web
✓Chrome, Safari, Firefox and Edge, latest versions
✓360, 768, 1280 and 1440 px widths
✓Keyboard-only pass with visible focus
✓Contrast and tap-target checks
The retest loop
01
Test the build
Design check and functional pass on the matrix above.
02
Report
Each issue filed in your Jira, Linear or GitHub Issues, with a screen recording.
03
Your team fixes
I answer questions and pair on tricky states.
04
Retest
Fixes verified on the next build, plus a short regression pass on the flows that changed.
05
Release readiness report
What passed, what is still open, and the known risks.
What this is not: it does not replace automated tests, load testing or security testing, and the release decision stays with your team.
How a project runs
Five steps. One owner from start to finish.
01
Discover
Brief, users and benchmarks, so we know what to keep and what to beat.
02
Design
Flows first, then high-fidelity UI for every surface.
03
Prototype
Animated, clickable prototypes you can test with real users.
04
Build
Front-end code with the motion in place, or files ready for your developers.
05
Test and launch
Each build checked on iOS, Android and browsers, issues retested, then a release readiness report.