The new Push Refresh site is live. Refreshed brand, completely rebuilt site, and a sharper expression of what we do. Take a look 👇 pushrefresh.com/go/twitter/l…

Looking at that React Native SDK tweet with TanStack Query hooks and native iOS transport Got me thinking about mobile auth flows What's your current approach for handling biometric auth in React Native apps? TouchID, FaceID, fingerprint - are you rolling custom or using a specific library?

Framer tip: use CMS collections for everything. Not just blog posts. Testimonials. Team bios. Pricing tiers. Case studies. Anything that repeats = collection. #framer

Hot take: React 19's Server Components are making everyone forget how to write good client-side code Watched three devs this week struggle with basic state updates because they've been living in RSC land for months \n\nClient state still matters \n\nYou still need to understand useEffect \n\nYou still need to think about re-renders \n\nServer Components are amazing but they're not a replacement for fundamental React skills \n\nProve me wrong

Seeing all these Framer Expert launches and template drops What makes a good Framer template actually sell? 1. Mobile-first design (not desktop shrunk down) 2. Real content, not lorem ipsum everywhere 3. Working forms and interactions out the box 4. Clean component structure for easy customization 5. Actually solves a specific business need What else am I missing? Drop your takes below 👇

Seeing this React Native interview question thread "What would you ask that's not useEffect?" Here's mine: "Walk me through how you'd debug a performance issue in a FlatList with 10k items" \n\nTells me if they understand: \n\n• getItemLayout \n\n• removeClippedSubviews \n\n• keyExtractor optimization \n\n• When to reach for FlashList \n\nReal-world debugging > trivia questions

Seeing that Expo QR code issue from earlier This one trips up everyone at least once \n\nQuick fix that works 90% of the time: \n\n1. Clear your Expo Go cache completely Go to Expo Go settings → Clear Cache \n\n2. Make sure you're on the same network Both computer and phone need the same WiFi \n\n3. If still stuck, use tunnel mode instead Run `npx expo start --tunnel` \n\nTunnel is slower but works through firewalls and weird network configs \n\nWhat's your go-to when Expo Go gets stubborn?

Looking at all these Framer template drops lately The landing pages look great but here's what I'm curious about: What's your process for testing conversion rates on your Framer sites? Are you using built-in analytics or connecting external tools?

Hot take: All these "first Next.js app" posts are celebrating the wrong thing The 3-hour Google Meet about routing? The country explorer with dynamic routes? You're learning framework features, not React fundamentals Most devs jump straight to Next.js without understanding: - How React actually renders - When components re-render - Why keys matter - Basic state management patterns Then they hit a performance issue and blame the framework Learn React first. The router can wait.

Seeing these Framer plugins getting approved in 2-3 days now Remember when marketplace review took weeks? I just submitted a component last month and boom — live faster than I could finish the docs The review process is so much smoother Anyone else notice this speedup? What's your recent approval timeline been?

React Native navigation just got way smoother \n\n1. Standard-navigation API now works with both React Navigation 7/8 AND Expo Router — write once, support both \n\n2. HeroUI Native's new CLI gives you Expo Router Uniwind Tailwind in one command (npx create-heroui-native-app@latest) \n\n3. Expo UI Workshop dropping soon — native SwiftUI/Jetpack Compose bindings directly in React Native \n\n4. React Navigation's standard-navigation means custom navigator authors don't need separate wrappers anymore \n\n5. RNGH v3 mentioned in This Week In React — gesture handling keeps getting better

Seeing all this React Native bundle size talk lately That 0.32MB savings? Nice. But here's what moves the needle more: \n\nDrop unused deps first\n\nThen optimize your assets\n\nBundle analysis comes last \n\nMost apps are shipping 2-3MB of dead code before they even think about Metro configs \n\nStart with the obvious stuff #reactnative

Seeing that tweet about copying Framer templates with AI Here's a better approach that actually respects the design work: **Step 1:** Study the template's component structure Look at how sections flow, spacing patterns, typography hierarchy **Step 2:** Build your own version in Framer Use their CMS for dynamic content Add your own animations and interactions **Step 3:** Customize with your brand Colors, fonts, imagery that fits your business You end up with something original that performs better than a straight clone Plus you actually learn Framer's component system #framer

Hot take: Next.js App Router is making developers worse at React \n\nSeeing all these "first full stack Next.js app" posts but half these devs can't build a decent client-side component without reaching for a server action \n\nWe're teaching people magic instead of fundamentals \n\nChange my mind

Hot take: Everyone's rushing to Next.js 15/16 but most teams don't need SSR at all Seeing all these "just deployed my first full stack Next.js app" posts You built a CRUD app with auth That's client-side work with an API React Vite would ship faster Build simpler Debug easier SSR is for content sites and SEO-heavy apps Not every project needs the complexity

Just migrated a client app from Metro to Re.Pack for React Server Components The difference is wild Re.Pack's Rspack bundling handles RSC streaming way better than I expected Module Federation RSC means each widget can be its own server component unit Seeing @callstackio push this boundary with React Native makes me think we're finally getting true universal React Metro was fine for basic RN But RSC changes everything

Looking at all these Framer form plugins dropping lately FramerForms with calculators, Frameblox date pickers, Template Checker for validation Got me wondering — what's your approach to form state in React when you need something more complex than a contact form?

3 things I noticed from these Framer builds hitting my timeline: 1. That mortgage platform comparison — the "experiencing it in Framer hits differently" comment is spot on. The visual editor gives you spatial context that static mockups can't. 2. Day 3/30 intro animation shows how Framer's timeline makes complex sequences feel approachable. No keyframe hell. 3. These hero section posts prove the community gets it — Framer isn't just for prototyping anymore. It's where you ship the real thing. #framer

Seeing these Framer plugin builds in my feed got me thinking \n\nMobile devs are sleeping on the Expo plugin ecosystem \n\nHere's how to build a custom dev plugin in 5 minutes: \n\n1. `npx create-expo-plugin my-plugin` \n\n2. Add your hook in plugin/src: ```js export function withMyFeature(config) { // modify config here return config; } ``` \n\n3. Test locally: `npx expo install ./plugin` \n\nThat's it \n\nNo approval process. No marketplace fees. Just pure development velocity. \n\nThe Framer plugin scene is inspiring but Expo's been doing this workflow for years \n\n#reactnative #expo

File-based routing is overrated and most teams would ship faster with traditional routing \n\nYeah I said it \n\nSeeing all this Next.js and Expo Router praise today but here's the reality: \n\nMost apps don't need fancy folder structures \n\nMost teams waste hours debating file organization \n\nMost bugs come from forgetting which folder does what \n\nReact Router with clear route configs? You know exactly what's happening \n\nFile-based routing with nested layouts and group routes? Good luck onboarding new devs \n\nThe "intuitive" part only works if everyone thinks like you \n\nFight me in the replies

Seeing more Framer → Claude → code workflows in my feed Makes sense Design in Framer's visual editor Export to Claude for custom logic Keep iterating between both Way smoother than starting from scratch in an IDE The visual-first approach just clicks for a lot of projects