Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Okay let's compare. We have implementations for native (SwiftUI & Compose), react native and flutter in no particular order. Can you tell them apart? Flutter actually did better than I expected visually, experience was as expected though (not great)

65,888 Aufrufe • vor 1 Jahr •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Started using React Native two days ago and immediately fell down a tab-bar rabbit hole. I’d seen Instagram and Revolut collapse their tab bars on scroll while keeping every icon visible. I wanted that without giving up real iOS Liquid Glass. Turns out iOS 26’s public API can’t express that state. UITabBarMinimizeBehavior is an enum of when, not what. With onScrollDown, UIKit minimizes the bar to the active tab alone. There’s no parameter controlling what survives. So most implementations rebuild the visible bar as a custom component. Some use genuine glass materials, but the real UITabBar is gone and with it, the native selection capsule: that little blob that moves like a drop of water between tabs. You can reproduce it with separate springs on the leading and trailing edges. I didn’t want a reproduction. I wanted UIKit’s. Then I remembered a Flutter app i built some months back which uses cupertino_native. Flutter runs the app while a platform-view bridge renders a real UIKit UITabBar. Finding expo-glass-tabs clarified the compact geometry I wanted. The two ideas clicked: why not bridge a real UITabBar into React Native? Here’s the trick: a standalone UITabBar has no UITabBarController managing it, so Apple’s minimization rule never applies. That means I can control its frame and items myself. Expo Router still owns navigation and screen lifecycle. React Native detects scroll direction. Swift removes and restores the real item labels, recentres the icons and animates the native bar’s size. All five icons remain visible. The result keeps Apple’s Liquid Glass, water-drop capsule, hit testing and accessibility, while adding a compact state its public API doesn’t provide. One gotcha tho: detaching the bar means reimplementing everything the controller previously gave you for free. Active-tab reselect scrolling was one example

kelvin.dart

67,945 Aufrufe • vor 1 Monat

Natively integrated—and #PoweredbyPyth🔮 Native is a liquidity solution that combines bridges, assets, and pricing into one offering on prominent L1/L2s, including . Learn more about our integration below: ℹ️ About Native Sourcing and supplying liquidity is expected to become prohibitively expensive and challenging as more networks emerge. Liquidity fragmentation persists because pricing remains inventory-based. Native was designed in response to this complexity and offers an elegant solution for routing any asset on one chain into a new target asset on any target chain. Native achieves this through a cross-chain liquidity mesh of cross-chain liquidity networks, bridges, DEXs, and PMMs. More specifically, Native can aggregate the best prices from its network of AMMs, aggregators, and partnered PMMs, so that users will always have competitive prices. 🔮 Native is #PoweredByPyth Native taps into Pyth’s real-time feeds to fetch prices on-chain and off-chain. for example, Native leverages Pyth Price Feeds to power ZetaSwap and support its token pricing operations. How Native Leverages Pyth Price Feeds Native runs its own in-house price-oracle service which will fetch pricing from a variety of sources, including Pyth, to update token prices in Native's backend server. These prices are then fetched and displayed to users live via the NativeX widget. Native also seeks to provide its proprietary trading data and become a part of the Pyth data provider community - more details to come.

Pyth Network 🔮

48,234 Aufrufe • vor 2 Jahren