Figma's Progressive Web App Bet That Paid Off Six Years Later

Figma in 2016 was a small startup competing against Sketch — the dominant design tool on macOS — with a fundamentally different bet about where design work would happen. Sketch was a native macOS application; Adobe XD was a native macOS and Windows application; the entire category lived on the desktop, with files passed around as static exports. Figma's bet was that design work would migrate to the browser, the way that document work had migrated from Office to Google Docs and the way that engineering work had migrated from local IDEs to web-based collaboration tools. The bet was contrarian. Designers in 2016 cared deeply about performance and offline reliability, and the browser was considered unsuitable for creative tools. Figma had to prove not just that the browser could be fast enough, but that the browser advantages (real-time collaboration, single source of truth, instant sharing) outweighed the disadvantages.

The technical bet on the browser came with a strategic bet on web standards. The Figma team led by Evan Wallace built the rendering engine in WebGL for performance, but they also invested heavily in the surrounding standards layer that most competitors ignored. The web app manifest (manifest.json) was shipped early, with proper icon sizes, theme color, and launch behavior. The service worker enabled offline mode — files could be opened and edited without an internet connection, with operations queued and synced when the connection returned. The site shipped with full ARIA landmarks (header, nav, main, footer with proper roles), clean heading hierarchy on every marketing page, complete Twitter card and OpenGraph metadata so URL shares rendered correctly in Slack and Twitter, and title-length discipline in the 30-60 character sweet spot for Google SERP rendering. None of these decisions individually drove the early growth, but the cumulative posture of "we treat web standards as load-bearing" set Figma apart from competitors who treated the browser as a constraint to work around rather than a platform to invest in.

The PWA-specific bet was the most forward-looking. In 2017, the Progressive Web App concept was a Google-led initiative with strong Chrome support, weak iOS Safari support, and uneven Android Chrome support. Most companies treated PWAs as a Google-platform feature, useful for Android but irrelevant for the iOS-heavy creative-professional market that Figma was targeting. Figma's calculation was different. Even if iOS didn't support PWAs in 2017, web standards rarely die — they get adopted slowly across browsers, often years late. Building a PWA in 2017 was investing in a platform that wasn't yet universal but probably would be. The cost of shipping PWA features was low (the team was already building a web app, the manifest and service worker were modest additions); the option value of being ready when iOS Safari added PWA support was high.

The bet took six years to pay off. iOS 16, released in 2022, added partial PWA support; iPadOS 17, released in 2023, made PWAs genuinely installable on iPad, which was Figma's most important secondary device for designers who wanted to sketch on the go. When the iPad PWA support shipped, Figma was instantly installable on every iPad in the world, with no app review process, no version-specific bugs, and no separate codebase to maintain. Competitors who had built native iPad apps (Procreate, Affinity) had years of head start in performance optimization, but Figma had something they didn't — the same product, the same data, the same collaboration features running across desktop, web, iPad, and any other device that could run a modern browser. The cross-platform consistency that the PWA strategy enabled became a significant competitive advantage.

The deeper strategic value of the standards-first approach showed up in unexpected places. SEO performance was strong because the marketing site followed best practices (sitemap, structured data, canonical URLs, meta descriptions, proper heading hierarchy). Browser-installation discovery was easy because the manifest was set correctly. Accessibility audits passed without remediation work because ARIA landmarks and form labels were in place from launch. Performance scores on Lighthouse and Core Web Vitals were strong because the team had invested in the foundational standards rather than chasing scores after the fact. The standards work compounded into a set of quiet advantages that competitors with similar feature sets couldn't easily match.

The market response over six years validated the bet. Figma grew from a small private beta in 2016 to roughly 4 million users by 2023 and became the dominant design tool in the industry. The combined effect of real-time collaboration (the headline feature) and standards-first browser execution (the unsung infrastructure) created a product that designers preferred to native alternatives despite the conventional wisdom that browsers couldn't handle creative tools. The 2022 Adobe acquisition agreement valued Figma at $20B — a price that reflected the strategic position Figma had built, not just the immediate revenue. The deal was eventually blocked by EU and UK regulators in late 2023, and Adobe paid a $1B breakup fee, leaving Figma as an independent company with confirmed strategic value.

The 2024-2026 period saw Figma extend the standards-first approach across new surfaces. Figma Slides (2024) and FigJam (2022) shipped with the same PWA installability, the same offline support, the same accessibility standards as the core Figma editor. Each new product launched as a web-and-PWA experience rather than as a native app on any platform. The operational simplicity of one codebase, one team, one release cycle compounded into faster shipping than competitors who maintained multiple native codebases. By 2026, the standards-first browser-native approach was the canonical pattern for new creative tools — competitors who shipped native-first now look outdated by comparison.

The pattern generalized beyond creative tools. Notion, Linear, Pitch, and most modern productivity tools followed the same playbook: ship to the browser first, invest in the surrounding standards (manifest, service worker, ARIA, structured data, meta tags), and let the cross-platform consistency become the moat. The shift in default product architecture — from "native first, web optional" to "web first, native optional" — was driven in significant part by Figma's success.

For product managers, Figma's case offers several lessons. First, betting on web standards before they are universally enforced is one of the most undervalued strategic moves in product. The cost is low, the option value is high, and the payoff arrives when the standards become defaults rather than features. Second, the small standards details (manifest, service worker, Twitter card, ARIA landmarks, heading hierarchy, title length) compound into a quiet competitive posture that most teams underinvest in because the individual line items don't drive conversion metrics. Third, one cross-platform codebase beats multiple native codebases for most products, because the operational compounding (one team, one release cycle, one bug surface) over five to ten years is enormous. Fourth, contrarian product bets that take five-plus years to validate are exactly the ones that produce durable advantages, because competitors give up before the payoff arrives. Fifth, the right time to ship standards work is before it's strategically required — once the standard is universal, the moat shrinks; the company that shipped years early owns the position.