Work

I split data boundaries across an independently versioned templates package, the live editor state, and async state for queries and mutations, so canvas and settings share one page tree.

Shipping each section type as an isolated editor feature would have looked faster early, while leaving conflicting sources of truth once templates, media, and maps shared a page.

Authors ship customized multilingual sites under live editing without fragile save paths. New sections extend the shared catalog and editing model so the builder stays coherent at platform scale.

I migrated domain by domain onto RTK Query with always-shippable stacked PRs, then removed legacy actions, constants, and middleware once each behavior path was preserved.

A rewrite behind a feature flag would have paused delivery and drifted from a fast-moving main that was already adopting the new feature-folder architecture across the whole codebase.

Three store layers and heavy boilerplate are gone. Caching, request dedup, and loading now share one pattern, cutting redundant network work while delivery stayed continuous.

I centered the work on semantic contracts, composable primitives, and distribution boundaries so shared UI could evolve without silently breaking tenant overrides or product consumers.

A one-size-fits-all abstraction would have looked consistent early, then left brittle tenant overrides and slower product work as teams hit real variation across the platform.

The design system now carries WCAG 2.2-aligned accessibility and shared contracts, while product teams can still support distinct brand identities without tenant-specific forks.

I extended the existing platform surface, integrated push delivery, and used xcconfig-based configuration so distribution stayed controlled from one source of truth across builds.

Duplicating web workflows as separate native logic would have increased drift and turned every product change into a cross-platform synchronization problem over the long run.

Shared workflows now reach thousands of mobile users through the same product model, and controlled releases keep build-to-submission time to under 48 hours for every release.