Really excited to see what’s next for Exact! This already makes me want to keep building with it.
If you missed the announcement post, here it is: https://t.co/Vvppf7pUkm
I want to share a preview of something I've been working on called Exact. It's a new Agent Native app framework written in Rust. It's extremely fast and tries to let you build exactly the experience you want with no compromises.
I wanted to try Exact from @ccheever@expo last night. I asked my agent to port a few screens from my Moovii app, and I’m really happy with the results already.
2 prompts later: iPhone, iPhone Duo, iPad, Mac, and web. All from one codebase 🤯
The coolest part is the native UI. Tabs, navigation, menus, and controls that belong on each Apple device, plus real DOM on the web.
Seeing the same screens adapt properly across all of them is pretty wild.
iOS developers: Please for the love of god stop making your own custom tab views, not least they because they all freaking suck on iPhone Duo. Shopify, Facebook, Google, Airbnb, YouTube, and more are all trying, and none of them are succeeding 🤷♂️
Safe area insets aren’t always enough on iPhone Duo.
Meet react-native-reserved-regions, a sister library to react-native-safe-area-context.
Apple’s new reserved regions API, in React Native. Let your UI make room for folds, camera cutouts, and system controls.
Engineers today run several agents in parallel. On a React Native app, those agents fight over ports, simulators, and rebuilds.
Today we're open-sourcing Stim, our agent-first CLI that gives each agent its own isolated RN/@expo environment.
Agents are good at writing React Native code, but suck at building and running the app.
The tooling is built for humans, not agents working in parallel.
Been working on a not-so-secret project to make that easier and faster.