Enterprise for iPad
Enterprise for iPad is Zonda's mobile companion app, giving homebuilders and land developers instant access to market data, site reports, and project tracking from the field.
Client
Type
Year
Role
Deliverables
80 Components
22+ User Flows
100+ App Screens
Brand Identity
160 Report Pages
BACKGROUND
Enterprise for iPad hadn't been meaningfully redesigned since 2013 — over 10 years of visual and interaction debt in a market that had moved on.
Two other pressures made the case for a rebrand impossible to ignore: Enterprise for iPad and Enterprise were sold as a bundle, but their interfaces didn't match (different navigation, different map markers, different everything), creating an inconsistent experience for customers who had to context-switch between them.
And without a shared design system, every new feature was slower and harder to build than it needed to be.
GOAL(S)
Design Goals
Align design patterns with Enterprise to close the visual gap between the two products
Refresh the app to feel modern and aesthetically current
Fix existing minor UI issues along the way
Adapt the design to take advantage of current iPad hardware/OS capabilities
Business Goals
Reinforce iPad as the go-to mobile solution for fast data access
Create scalability and feature parity with Enterprise
Strengthen brand consistency across the product line
Make future design and development cheaper via a reusable design system
STRATEGY
A connected but distinct design system
Built Enterprise's basic styles as the shared foundation, then created an iPad-specific system on top — so the two stayed visually and structurally connected while respecting the different platforms.
Platform-appropriate interaction design
Informed by Apple's HIG: larger tap targets and bigger text for touch-first, arm's-length use; layouts that used the larger display to surface more content without extra scrolling; support for multiple device orientations (4+ vertical layouts) instead of just one.
Forward-looking technical support
Including dynamic type, adaptive layouts, and a version built to work properly on iPad-on-Mac OS (adding hover states and desktop-style interactions where needed).
Accessibility passes
With roughly 3 iterations focused specifically on contrast and font readability.
A tight collaboration loop with engineering
Every design decision was checked against the dev team, which kept friction low and reuse high (avoiding 2–3 redundant variations of the same component).
Edge-case coverage
Built Enterprise's basic styles as the shared foundation, then created an iPad-specific system on top — so the two stayed visually and structurally connected while respecting the different platforms.
OUTCOMES
The hardest call on this project was sequencing. Enterprise and iPad needed to feel like one product, but iPad's design system had to work as a touch-first, standalone system. Building the shared foundation first, then branching iPad-specific patterns on top of it, meant slower early progress in exchange for far less rework later — a trade I'd make again.
Checking every decision against the dev team as I went, rather than batching feedback at the end, is the habit I'd carry into the next project unchanged. It's the reason the rebrand shipped 4 weeks early instead of getting stuck in a late-stage rebuild.
If I did it again, I'd push harder on the accessibility pass earlier in the process instead of iterating on it three separate times — the contrast and readability issues were catchable in the first design system pass, not after components were already in use.
That's the story behind this project.
Curious what else I've worked on?