5 ms·

Great writeup(s), thanks for sharing! My immediate reaction was “that sounds too good to be true”, which is a nice compliment I think. I have some high level qu

by bbor 2y ago

Great writeup(s), thanks for sharing! My immediate reaction was “that sounds too good to be true”, which is a nice compliment I think. I have some high level questions if you find the interest: 1. Why have a React Native clone of your SPA instead of just doing a PWA? Does it provide some technical benefit (better offline local data persistence, maybe?) or is it just to get your site advertised on the App Store? Surely all the device APIs for movement, multitouch, etc. are supported on mobile browsers? This has been bothering me for a while, so perhaps too broad of a question. 2. What’s the rough timeline and funding look like for this? In my eyes this is a solution to, like, all complex web apps ever, so I was shocked to see just a few developers. I know you acknowledge some bugs in the Native implementation, but besides that, do you feel like this could be used for a data intensive Postgres-backed TS application today with minimal chances of bugs, or is it still a bit more experimental? I guess I’m looking for a bit of clarification on the intended meaning of “production ready”, since it seems so damn ambitious. Either way, Godspeed! Your website is gorgeous, and the whole project is insanely up my alley. Plus ‘npx one’ is just slick as hell

motoxpro 2y ago
even being a "tech" person i havent ever installed a PWA and no one in my "non tech" circle even knows that they exist. Lots of user education to do there for them to work in my opinion.
nwienert 2y ago
1. With Tamagui you can share almost 100% code, so it's not a re-write, and mostly the reasoning is that it feels a lot more native. Especially interactions, scrolling, and being able to use native UI and libraries anywhere you want. Performance is a bit better too in general. It's a bit more work for sure, but I think Tamagui + One really does make it a ton more doable than before. 2. Tamagui is bootstrapped and makes some money, we haven't raised and aren't sure yet if we will. But we may need to if we want to compete long-term against well funded competition. Honestly web works really well, we have a few sites in production already. Native works pretty decent but we just want to add a lot of tests and get a more apps into the app store before we call it stable. I'd estimate 6 months it'll be stable, but you can probably reliably deploy an app within 3.
- bbor 2y ago
  Fantastic. You’ve got a new user in me, will be porting my AI from next.js asap. Thanks for taking the time!

by bbor 2y ago

motoxpro 2y ago

even being a "tech" person i havent ever installed a PWA and no one in my "non tech" circle even knows that they exist. Lots of user education to do there for them to work in my opinion.

nwienert 2y ago

1. With Tamagui you can share almost 100% code, so it's not a re-write, and mostly the reasoning is that it feels a lot more native. Especially interactions, scrolling, and being able to use native UI and libraries anywhere you want. Performance is a bit better too in general. It's a bit more work for sure, but I think Tamagui + One really does make it a ton more doable than before. 2. Tamagui is bootstrapped and makes some money, we haven't raised and aren't sure yet if we will. But we may need to if we want to compete long-term against well funded competition. Honestly web works really well, we have a few sites in production already. Native works pretty decent but we just want to add a lot of tests and get a more apps into the app store before we call it stable. I'd estimate 6 months it'll be stable, but you can probably reliably deploy an app within 3.

bbor 2y ago
Fantastic. You’ve got a new user in me, will be porting my AI from next.js asap. Thanks for taking the time!