Tamagui works with the Next app directory now, the starter will be updated within a day or two. Though warning that there’s still a lot of sharp edges in general with it.
v1.14 lands our huge speed improvement on theme changes!
The homepage of the website (a pathological use case with many animated components) is 2x faster. On docs pages, 6x 🤯
Before/after:
Next minor Tamagui merges a hard-fought and huge perf upgrade when changing themes, test here:
site-git-theme-avoid-rerende…
Avoids re-rendering for nearly every component (in fact, only when animated & not using CSS driver will anything re-render).
github.com/tamagui/tamagui/p…
We’ve been a bit quiet lately but anyone watching the repo knows velocity has been higher than ever.
Also 🚨 please upgrade to the latest!
We fixed one of the biggest bugs. The explanation in the discord I think explains how tricky this stuff is
Feld is built on the shoulders of giants. It uses @expo and @Baconbrix's Expo Router, @natebirdman's @tamagui_js, and is built with a fully serverless backend on AWS (with a single table, @alexbdebrie 😉).
Important Reminder:
You can use Tamagui with no bundler config *at all*.
Just add the package, pass in our included base config, Provider, and you’re off.
Setting up the compiler can turn folks off, so we designed Tamagui to work 100% runtime only. It’s a really nice feature!
Our next speaker – @natebirdman will cover how @tamagui_js & other libraries are making "write once, run anywhere" possible without the typical sacrifice of feeling and performance, the relationship between DX and UX, and more!
Come see Nate at App.js!
appjs.co
@tamagui_js has this kind of DX that makes you proud of using a specific tech. Literally
Not only it is mind blowing, but it makes you belong to the « this is the right way to make apps » circle, and thanks for the hard work there! Keep it up