Pocketship

With Pocketship I keep getting the same support question: how do I share a design system across React Native and a marketing website so they don't drift apart after the first redesign? I've seen three camps: Design tokens only - share colors/spacing/type as JSON, rebuild components per platform Shared component package - one RN/web component lib, lots of platform ifs Just copy-paste and accept the drift The dream is: designer changes a token in Figma, it flows to native + web with zero manual work. For teams who've lived with this for more than a year - what actually survived contact with reality? Style Dictionary? Tamagui? Something custom?

Building the auth module for Pocketship and stuck on a product line: do I bake in a full opinionated auth (sessions, refresh, biometrics, social) or ship thin adapters and let people bring Clerk/Supabase/Firebase? Bake-it-in = magical first 10 minutes, painful when someone needs something custom. Adapters = flexible but the "weekend MVP" promise dies in config. Starter kits live or die on the first hour. But they get abandoned on the first wall. Where would you draw the line?

Our RN e2e suite is ~12% flaky and it's training the team to ignore red builds, which defeats the entire point. Suspected causes Animations not settled before assertions Network races (real backend in CI) Timers and debounced inputs I'm tempted to quarantine flaky tests automatically and retry once, but that feels like sweeping it under the rug. How do you keep e2e honest without it becoming a coin flip?