• @graphito@sopuli.xyzM
    link
    fedilink
    English
    36 days ago

    Nope, installation files aren’t going away. Joplin is a desktop app first. This prototype is simply an exploration of what is possible from browser

    • @CaptObvious
      link
      English
      46 days ago

      Thanks. While I understand the convenience, SaaS is hard to trust.

      • @graphito@sopuli.xyzM
        link
        fedilink
        English
        3
        edit-2
        5 days ago

        To shoehorn into this comment about SaaS I wanna say that this version cannot be used as a SaaS solution. Server instance in this prototype acts only as executable distribution system – like google play but without any ui. It simply sends the executable file to your browser – the same way other offline webapps work.

        Besides distribution everything else runs locally: this web version uses your local storage, computing resources and can sync to third party sync target

          • @graphito@sopuli.xyzM
            link
            fedilink
            English
            26 days ago

            For now it’s just a demo for new users to try Joplin features. I don’t know if it can be used as a release (production version) at all. If anyone got ideas of good uses for this initiative, pls share

            • @laurent@sopuli.xyzM
              link
              fedilink
              English
              22 days ago

              Yes this is not production ready, and to be clear that’s essentially the mobile app deployed as a web app. So the mobile/desktop apps are definitely not going away, but it means that any new mobile version we create, we can deploy it for the web too (provided this PoC works out well and it looks like it does). This is convenient for people who cannot install apps, for example on lock down devices, or simply for those who don’t want to install any app. Then it runs with only the permissions of the browser.