fernandorojo

6 ms·

1.
by fernandorojo 10mo ago
> If you were to do it all over again, would you think about building on native technologies instead? Although it took a lot of effort, it was a new set of UI patterns for React Native, and it hadn't really been done well yet. Where
2.
by fernandorojo 10mo ago
Yeah that's what we use (and we showed it in the patch in the blog post). There was a bug on a particular iOS 26.2 beta, but it looks like it's already fixed
3.
by fernandorojo 10mo ago
TIL a Cordova app won
4.
by fernandorojo 10mo ago
Imagine being the first one!
5.
by fernandorojo 10mo ago
I ultimately prefer React Native's composition model over SwiftUI. Something that attracts me to RN is that it's easy to drop down to native. We use SwiftUI for a number of components under the hood. But for a full app, React Nati
6.
by fernandorojo 10mo ago
Our biggest usage of AI was actually a code review bot which lives on GitHub PRs. It reviews our code on every commit. It was originally an internal tool, but it's now Vercel Agent. We also used v0 for prototyping ideas and designs for
7.
by fernandorojo 10mo ago
For the live activities, we used expo-apple-targets. That helps bootstrap it, link assets, etc. The UI itself is SwiftUI. The hard part here was actually the server-driven events for the activities during the stream. Live activities can be
8.
by fernandorojo 10mo ago
Checking on this Firefox issue now, thanks for sharing.
9.
by fernandorojo 10mo ago
Overall, our focus right now is iOS, but we want to do Android at some point. Even though we used React Native, we also wrote a good amount of native Swift code under the hood to power native modules.
10.
by fernandorojo 10mo ago
Interesting, that actually should work. Are you on iOS 26.2 by chance? I'm currently investigating a regression on interactive keyboard dismissal specific to iOS 26.2.
11.
by fernandorojo 10mo ago
Thanks for sharing, sorry about that. We had an issue on the backend with Apple sign in that we just fixed today. Mind signing out and back in to see if it's fixed?
12.
by fernandorojo 10mo ago
Author of the blog post here. Happy to answer any questions.
13.
by fernandorojo 1y ago
This is cool. I hadn’t come across an objective measurement of accents before.
14.
by fernandorojo 3y ago
I’m fan of Daishi’s other work (like Zustand and react-hooks-global-state) so I’m intrigued to see this drop. As a longtime Next.js fan it’s cool to see simplified versions of new tech emerge.
15.
Solito 4 – React Native in the Next.js app directory(solito.dev)
3 points by fernandorojo 3y ago|0 comments
16.
by fernandorojo 4y ago
Ah, makes sense. Tamagui basically solves the part of styling + rendering UI. It works on both web and native. As for logic/data fetching...this has gotten far, far better in React over the past few years. For data fetching, assuming y
17.
by fernandorojo 4y ago
What do you mean? Tamagui is only concerned with UI. Data and state management live in the react world using hooks.
18.
by fernandorojo 4y ago
That's a cool site. I like the use of iframes.
19.
by fernandorojo 4y ago
Of course, happy it's helpful.
20.
by fernandorojo 4y ago
I wouldn't let its native support pigeonhole it as a React Native-only library. In my experience, it rivals other web-only libraries, especially with the compiler.
21.
by fernandorojo 4y ago
LambdaTest is helpful for these cases FWIW
22.
by fernandorojo 4y ago
Somewhat, but it's better. It's like forking React Native Web and solving all of its styling shortcomings.
23.
by fernandorojo 4y ago
I used Tamagui to build a number of screens for a new product we're working on, and I saw 90+ lighthouse scores on every page. The fact that I can get that, with SSR support, inline styles, psuedo selectors, typed themes, and that it
24.
by fernandorojo 4y ago
Cool idea. I’ll definitely check it out. We’ve been thinking of making something similar internally.
25.
by fernandorojo 5y ago
React Native + Next.js refers to using the same code in both a native app and website (built with Next.js). The hardest part of sharing code between apps and websites, however, is the navigation code. Websites have flat navigation. You have
26.
by fernandorojo 5y ago
I don't view a single codebase as the goal necessarily. While I see the benefit to doing a WebView everywhere, I prefer the React Native approach: write once, run anywhere by using the underlying native components of each system. Becau
27.
by fernandorojo 5y ago
Those kinds of implementation details won't be hard to add to Solito. The API I'm using is that of Next.js. If they adapt to suspenseful approaches to routing, Solito will too. There are also experiments in the works to make React
28.
by fernandorojo 5y ago
Glad it's helpful!
29.
by fernandorojo 5y ago
Solito gives a “solo dev” the power to build for multiple platforms. I built our entire product from scratch for iOS, Android and Web. Rather than rushing to hire a team to do each thing, I felt that if I built the right abstraction layers,
30.
by fernandorojo 5y ago
Someone has brought up adding a Remix integration to Solito, too. It's certainly possible from my end, the question is if Remix would make it possible. Many remix APIs like Form seem to be very browser-specific, so it wouldn't sha

More ›