Render anything inline. Save sessions and history. Powered by open web standards.

I’m trying it, and it does looks nice.

  • dan@upvote.au
    link
    fedilink
    arrow-up
    0
    ·
    11 months ago

    I don’t understand why desktop JS apps don’t use React Native at least. It’s still JavaScript but doesn’t use a browser, and renders to native UI widgets. Far lighter than Electron.

    • ☆ Yσɠƚԋσʂ ☆@lemmy.ml
      link
      fedilink
      arrow-up
      0
      arrow-down
      1
      ·
      11 months ago

      The disadvantage with React Native is that you still have to maintain a UI for each platform because it maps to native widgets while a web UI works the same on every platform.

      • dan@upvote.au
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        11 months ago

        Business/application logic can be 80-90% of an app’s code, and all of it can be reused across platforms. The actual UI rendering is just a small part of it.

        In the UI code, some of it does have to differ across platforms but it’s mostly the lower level components like buttons, text fields, etc. Some product UI code built on top of those abstractions can be reused across platforms.

        • ☆ Yσɠƚԋσʂ ☆@lemmy.ml
          link
          fedilink
          arrow-up
          0
          arrow-down
          1
          ·
          11 months ago

          Sure, but it’s still more work than a web UI, and using a web UI is a lot more flexible. For example, say you want to render a chart or some other visualization. It’s trivial to do with a web UI, but can be a tricky problem with native widgets, especially if you want to keep the UX consistent across platforms. I agree that using React Native can work fine in a lot of cases, but I can also understand the appeal of using the web UI stack. Another aspect is likely familiarity, people use the tools they know, and if somebody is already comfortable with a particular ecosystem they’re likely to leverage it.