Product Design Company in San Francisco

Three delivery shapes drive the range: a scoped product design sprint for a Bay Area MVP, a full design system build with WCAG 2.2 AA conformant component library, Storybook handoff, and Apple HIG variants where native, or end-to-end product design for an enterprise B2B SaaS product at the Stripe and Linear minimalism standard, including dev-tools UX, API reference design, and CCPA-aware consent flows. Scope drivers include research, a design system foundation, and a clickable Figma prototype. San Francisco rates sit at the top of the global market because of the Stripe, Linear, Figma, and Apple talent premium plus YC alumni density. We quote fixed-fee with a clear scope, not open T and M.

B2B SaaS minimalism, as practiced by Stripe, Linear, Notion, and Figma, is not a visual style. It is a discipline. The discipline shows up in restrained type ramps (two or three sizes, not eight), deliberate use of monospace where information density and developer-facing context demand it, color used as signal rather than decoration (Linear's accent system is the canonical example), motion that confirms intent rather than performs personality, and high information density without visual noise (Stripe's dashboard fits more data per pixel than most consumer products and still reads cleanly). Implementation requires a strict design token system, an opinionated component library, and discipline in design reviews to reject decoration. Our engagements deliver design systems built to that discipline, and we publish the token architecture so engineering can extend it without re-introducing visual noise.

Yes. The Northern District of California federal court remains the most active venue in the United States for digital accessibility lawsuits under ADA Title III, with Robles v. Domino's (Ninth Circuit, 2019) establishing that Title III applies to websites and mobile apps of public accommodations. The operative settlement standard is WCAG 2.2 AA. Our engagements ship with a full WCAG 2.2 AA conformance pack including axe-core automated test suite, manual VoiceOver and TalkBack test reports, keyboard navigation audit, and a published accessibility statement. WCAG 2.2 added nine new criteria over 2.1 (focus appearance, dragging movements, target size, consistent help, redundant entry, accessible authentication) and we test against all of them. We coordinate with client legal counsel during design to address demand letter risk before launch, not after.

The California Consumer Privacy Act (CCPA), as amended by the California Privacy Rights Act (CPRA) effective January 2023, places consent, disclosure, and opt-out obligations on businesses processing California resident personal information above defined thresholds. The California Privacy Protection Agency (CPPA) finalised regulations specifically prohibiting dark patterns in consent flows, including pre-checked boxes, unequal button styling, and confusing language that obscures the user's choice. Our designs implement a Do Not Sell or Share My Personal Information link in the global footer (as required), a clear consent flow with equal visual weight on accept and reject, granular per-purpose consent, plain English purpose descriptions, and a documented data subject rights request flow accessible from account settings. We coordinate with client legal during the design phase, not after a CPPA enforcement action.

Yes, where it fits. The Stanford d.school methodology (Empathize, Define, Ideate, Prototype, Test) institutionalised design thinking and remains the canonical framework for early-stage problem framing and divergent ideation, particularly for ambiguous problem spaces and 0-to-1 product work. We use the full five-stage process for greenfield engagements with genuine user uncertainty, and a compressed Empathize-Prototype-Test loop for incremental work where the problem is well-understood. We do not apply design thinking ceremonially to projects that need execution rather than discovery, which is where most design thinking criticism lands. Our team includes designers with d.school workshop experience and clients can request a structured discovery sprint when the engagement scope warrants it. We are honest about which phase actually needs the formalism.

Yes. We build native iOS, macOS, watchOS, and visionOS experiences to the Apple Human Interface Guidelines, working alongside SwiftUI engineers from kickoff so the Figma file and SwiftUI previews evolve together rather than diverging. HIG conformance covers navigation hierarchy, system-provided controls preferred over custom, Dynamic Type and accessibility scaling, proper Dark Mode and high-contrast support, motion that respects reduce motion preferences, and platform-appropriate haptics. For Vision Pro work we follow the visionOS guidelines on spatial computing, including comfortable depth, eye-tracking-aware target sizing, and ergonomic field-of-view consideration. Our work has been used by Bay Area developers shipping to the App Store with App Store editorial-grade craft, not the lowest-common-denominator template look common in cross-platform tooling output.

Developer-as-user research has a different recruiting and methodology profile from consumer research. Developers do not respond well to generic UserTesting panels and they spot poorly framed survey questions instantly. We recruit through GitHub sponsors networks, Hacker News, IndieHackers, Bay Area developer Slack communities, conference attendee networks (StripeSessions, Linear's UNGROUP, GitHub Universe), and direct outreach via X. Sessions are usually moderated and screen-shared, with the participant working through real code in their own editor against our prototype API or CLI. We pay developer rates (USD 200 to USD 400 per hour for senior developers), which most consumer-grade research budgets underestimate. Outputs feed into API reference IA, CLI command structure, error message copy, and documentation patterns derived from the Stripe and Linear documentation benchmarks.

AB 2273, the California Age-Appropriate Design Code Act, requires businesses providing online services likely to be accessed by children under 18 to assess and mitigate risks to children and apply the highest privacy settings by default. Although the law has faced First Amendment challenges (NetChoice v. Bonta) and portions have been enjoined, the design principles align with the UK ICO Age Appropriate Design Code (used as the design template) and remain the operative best-practice standard for products with significant minor user bases. Our designs for in-scope products produce a Data Protection Impact Assessment input, age estimation or assurance UX aligned with ICO precedent, default-on safety settings for likely-minor users, and clear privacy disclosures pitched at the appropriate reading age. We coordinate with client legal counsel on which portions of AB 2273 are currently enforceable.