[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.] #  @barany6m Baran Baran posts on X about what to, loading the most. They currently have XXXXX followers and XX posts still getting attention that total XXXXX engagements in the last XX hours. ### Engagements: XXXXX [#](/creator/twitter::1259866197459435520/interactions)  - X Week XXXXXXX +291% - X Months XXXXXXX +1,898% - X Year XXXXXXX -XX% ### Mentions: X [#](/creator/twitter::1259866197459435520/posts_active)  - X Week X +100% - X Months X no change - X Year X -XX% ### Followers: XXXXX [#](/creator/twitter::1259866197459435520/followers)  - X Week XXXXX +7.20% - X Month XXXXX +12% - X Months XXXXX +10% - X Year XXXXX +13% ### CreatorRank: XXXXXXX [#](/creator/twitter::1259866197459435520/influencer_rank)  ### Social Influence [#](/creator/twitter::1259866197459435520/influence) --- **Social topic influence** [what to](/topic/what-to), [loading](/topic/loading) ### Top Social Posts [#](/creator/twitter::1259866197459435520/posts) --- Top posts by engagements in the last XX hours "For our new product we built a chat in React Native that feels like iMessage Here's how we did it: Fabric Swift View UICollectionView SwiftUI cells via UIHostingConfiguration React is responsible for the state - mutations fetching infinite loading - all via React Query. The native Fabric view is purely for rendering. React decides what to show native decides how to show it The bridge between three frameworks was tricky but worth it. UICollectionView animations come for free and scroll performance is native-smooth No blank spaces and no FPS drops - all powered by the New Architecture Who wants" [X Link](https://x.com/barany6m/status/1977070251016667484) [@barany6m](/creator/x/barany6m) 2025-10-11T17:54Z 4418 followers, 106.2K engagements "We built this onboarding flow in React Native that feels better than most native apps Heres how we did it: Patched react-native-screens for a custom transition Button and stepper are rendered on top of the stack Synced button state across screens via context The button and header are positioned absolutely above the stack. When a screen focuses it updates the shared button state (text disabled state) via context The hardest part is keeping the keyboard open during screen transitions. We solved it with hidden TextInputs that get focused programmatically before navigating The result: one button" [X Link](https://x.com/barany6m/status/1980027483740164374) [@barany6m](/creator/x/barany6m) 2025-10-19T21:45Z 4418 followers, 214.7K engagements
[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]
@barany6m BaranBaran posts on X about what to, loading the most. They currently have XXXXX followers and XX posts still getting attention that total XXXXX engagements in the last XX hours.
Social topic influence what to, loading
Top posts by engagements in the last XX hours
"For our new product we built a chat in React Native that feels like iMessage Here's how we did it: Fabric Swift View UICollectionView SwiftUI cells via UIHostingConfiguration React is responsible for the state - mutations fetching infinite loading - all via React Query. The native Fabric view is purely for rendering. React decides what to show native decides how to show it The bridge between three frameworks was tricky but worth it. UICollectionView animations come for free and scroll performance is native-smooth No blank spaces and no FPS drops - all powered by the New Architecture Who wants"
X Link @barany6m 2025-10-11T17:54Z 4418 followers, 106.2K engagements
"We built this onboarding flow in React Native that feels better than most native apps Heres how we did it: Patched react-native-screens for a custom transition Button and stepper are rendered on top of the stack Synced button state across screens via context The button and header are positioned absolutely above the stack. When a screen focuses it updates the shared button state (text disabled state) via context The hardest part is keeping the keyboard open during screen transitions. We solved it with hidden TextInputs that get focused programmatically before navigating The result: one button"
X Link @barany6m 2025-10-19T21:45Z 4418 followers, 214.7K engagements
/creator/twitter::barany6m