One

we said we'd be a bit quiet this month, just little update: ⚀ we're 3mo into a large app with One + @zero__ms ⚀ hard to believe how far we've gotten this fast ⚀ starter kit based on it before summer ⚀ hard to explain how big a leap forward this will be

@rommyarb we're lining it up! almost

Hey, it's been 12 days, and nothing is happening. Are you there?

hello

the next gen one/zero/tamagui stack is really something else. our new chat app (started jan) has been flying. but it's also massive - more features than many mature companies, Linear-level polish. it's going into private beta this week. more on that soon. we also started on a new app for a client who raised $7M. we're **two** days in - and already have 20+ screens in place, auth flows, great animations/themes/details, lots of native UI, ios + web + android working in dev + prod, testing, ci/cd... basically an entire startup has come to life in a weekend. once we complete this project (goal is 1 month e2e into both app stores), we're going to immediately move towards releasing a bunch of things: - One 1.0 RC1, featuring "Metro mode" which makes adoption risk way lower. - Tamagui v2 should come out separately here soon - Free starter kit based on the stack - Takeout 2 - which so much better than v1 it's hard to compare, and will be actually powering multiple production apps. All Pro accounts will get it in beta form likely near end of October and then chat app will come EOY that's the update, and why i've been so quiet lately 🍻

@WhoKnow50498590 Web yes, native no. We went quiet a couple months ago to go heads down on a few things that are now fairly close to ready that will get us there.

@one__js One is prod ready, for RN?

Getting close to the perfect stack

@guillem_puche Checking..

@one__js I don't know how to run it with Android github.com/onejs/one/issu… P.S. Using Linux

new release out - we've fixed a ton of things with @vercel builds we're actually one of the only frameworks using the Build Output API as our target

@jviper410 @zero__ms For now we are only officially supporting mobile but we’d be happy to collaborate on any React Native platforms.

@one__js @zero__ms Over The Top, basically full suite of mobile apps and TV apps. AppleTv and Android TV support react native, then there are the other platforms some support react native others are web views.

we said we'd be a bit quiet this month, just little update: ⚀ we're 3mo into a large app with One + @zero__ms ⚀ hard to believe how far we've gotten this fast ⚀ starter kit based on it before summer ⚀ hard to explain how big a leap forward this will be

@jviper410 @zero__ms What’s OTT?

@one__js @zero__ms Will this work in a full OTT app deployment? Going to TV app providers?

We’re thrilled to welcome @natebirdman, founder of @tamagui_js and @one__js, to the Local-First Conf 2025 lineup! Nathan will make the case for simpler frameworks and better UX by showing how local-first flips the script on data management.

.@one__js Lets Frontend Devs Build Once, Deploy Web and Native Apps | By @LoraineLawson feat. @natebirdman thenewstack.io/one-lets-front…

@mrousavy @rauchg The webs biggest limitation is being single threaded and the DOM is slow as ass. People try a nice sheet demo and think the web can compete but they forget that their users will be dragging that sheet during React render = dead in water

It's not that simple - Keyboard handling on mobile is different; - A View is not always scrollable - on web it is. You have to add padding for the keyboard - Keyboard padding can be either added to the whole view, then everything moves up and scales, or to a child container via padding - If added via padding, content above the text input needs to account for that - either go out of view (translate) or scale down - Keyboard can be interactively dismissed and has a special animation curve - On native you have safe areas like notch or bottom bar, those will be added or removed from the keyboard safe area view SwiftUI makes this a lot easier than UIKit, but it's still more responsibility & control compared to the web - and I think that's good

I’m convinced the gap in experience between a native mobile app and a mobile web app boils down primarily to user input at this point. The performance gap is illusory for most use-cases & devices. Safari iOS handling of how a keyboard displays, the havoc it wreaks on the page, and limited APIs to control it are a fundamental issue. Once 120fps animations are enabled by default that’ll be the icing on the cake. But any diminishment in the ability for a human to reliably enter information into the page is a deal breaker.

There is no path to One that does not involve going through Zero.

@iamsahaj_xyz CF support has not landed yet, but we have good progress. If you use us ping in the Discord and we can prioritize it. We already have Vercel working so it’s not a big jump.

@iamsahaj_xyz Hello

if you have a Vite SPA and you want to build a backend now but don't want to use nextjs - what are your options? - needs SSR/SSG - should work with cf workers - minimal framework magic - good DX opinions on hono / tanstack-start? asking for a friend 👀

We finally tracked down a really tricky and annoying issue causing stale states, the patch ended up being in React Navigation itself Once again @zetavg with heroic investigation and write up, link 👇

Who wants to help contribute better error overlays with OwnerStack?

@zkjason_ @zero__ms No but we do have Vercel mostly working and from there Cloudflare and other serverless should be relatively easy. Nitro had a ton of things going on at once, lots of opinionated choices some we didn’t want so we decided not to use it.

@one__js @zero__ms Does One use runtime adapters like Nitro?