Live data from Hacker News

Viewing profile — fernandorojo

fernandorojo

HN member
Joined
Sat, Mar 24, 2018, 7:49 PM UTC
HN karma
125
Public activity
39 items

About fernandorojo

YC Badge: 0x3Eb56c914D3C904Eb88ec41e437C51f07f2067a0

twitter.com/fernandotherojo

Recent public activity

  1. comment
    Comment #46113524

    > 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 Na…

  2. comment
    Comment #46113436

    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. comment
    Comment #46113429

    TIL a Cordova app won

  4. comment
    Comment #46113422

    Imagine being the first one!

  5. comment
    Comment #46113308

    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 compone…

  6. comment
    Comment #46113291

    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…

  7. comment
    Comment #46113267

    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 f…

  8. comment
    Comment #46112814

    Checking on this Firefox issue now, thanks for sharing.

  9. comment
    Comment #46112718

    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 p…

  10. comment
    Comment #46063723

    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. comment
    Comment #46063715

    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. comment
    Comment #46048699

    Author of the blog post here. Happy to answer any questions.

  13. comment
    Comment #43913910

    This is cool. I hadn’t come across an objective measurement of accents before.

  14. comment
    Comment #37288936

    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 …

  15. story
  16. comment
    Comment #34190870

    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…

  17. comment
    Comment #34189991

    What do you mean? Tamagui is only concerned with UI. Data and state management live in the react world using hooks.

  18. comment
    Comment #34189286

    That's a cool site. I like the use of iframes.

  19. comment
    Comment #34189213

    Of course, happy it's helpful.

  20. comment
    Comment #34188164

    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. comment
    Comment #34188090

    LambdaTest is helpful for these cases FWIW

  22. comment
    Comment #34188071

    Somewhat, but it's better. It's like forking React Native Web and solving all of its styling shortcomings.

  23. comment
    Comment #34188047

    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, inlin…

  24. comment
    Comment #33151862

    Cool idea. I’ll definitely check it out. We’ve been thinking of making something similar internally.

  25. comment
    Comment #30686305

    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 …