Websites Built to Perform. Products Built to Scale.
We specialize in Framer builds, custom React websites, complex platform migrations, and custom applications
The new Push Refresh site is live.
Refreshed brand, completely rebuilt site, and a sharper expression of what we do.
Take a look π
https://t.co/2o4GxxuiAG
Switched from REST to Server Actions on a project last week.
No API route files. No fetch calls. No loading state boilerplate.
Felt weird at first. Then it felt obvious.
#nextjs#react
What state management library are you reaching for in 2026?
We've been using Zustand for most things.
No boilerplate. No providers. Just works.
But curious what others are picking.
#react
Honest question for mobile devs:
Are you writing tests for your React Native apps?
If yes β what kind? Unit? E2E? Snapshot?
If no β why not?
No judgment. Just curious.
#reactnative
3 React Native libraries worth trying:
1. Reanimated β 60fps animations on the UI thread
2. MMKV β fast key-value storage (10x faster than AsyncStorage)
3. Flash List β lists that don't drop frames
#reactnative
Seeing all these Framer Expert posts launching services
Most are selling the same thing: "I'll build your site"
\n\nBetter approach:
Build a specific component system first
\n\nExample: E-commerce product cards with hover states, CMS integration, and mobile variants
\n\nThen sell the system + implementation
\n\nClients get proven components. You get predictable scope.
#framer
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