Skip to content

$ cat ~/case-studies/adobe.md

Creative workflow prototyping at scale

An iPad creative tool used by internal Adobe product teams to prototype new brush and surface behaviors before committing to the roadmap.

client: Adobeindustry: Enterprise softwareduration: 6 weeksteam: 3 senior engineers
Adobe case study hero

Adobe's internal creative-tools group needed a way to prototype brush-engine changes against real-world workflows without shipping through their regular release train. The brief: a sandbox iPad app that product designers could actually use, not a lab toy.

We shipped in 6 weeks on a fixed-price scope. SwiftUI for the interface, Metal for the brush engine, AWS Lambda + S3 for the backing sync. The app installs from an internal MDM channel and lets designers load surfaces, test brush behaviors, and export comparison recordings for review.

Key decisions: we kept the brush pipeline native-Metal rather than bridging through a cross-platform layer (latency was the whole point), and we let the sync layer lag behind the canvas rather than blocking — the wrong bet would have made the pen feel laggy.

$ git diff --scope
tradeoffs.log
  • + kept: Sub-16ms pen-to-pixel latency
    - cut:  Cross-platform code sharing
    // why: SwiftUI + Metal stayed; a React Native bridge would have doubled the frame budget.
  • + kept: Offline-first sketch persistence
    - cut:  Real-time multi-user canvas
    // why: Designers work solo; multiplayer was theater cost with no user demand.
  • + kept: Hardware-accelerated export
    - cut:  In-app video editing
    // why: Export was the share-ready moment. Editing was Premiere's job, not ours.

$ ready to start

Book a Lehi strategy session.

30 minutes. You leave with a scoped MVP plan, a fixed-price quote, and an AWS architecture sketch.