• New reply has been added.Load it
  • You need to be signed-in to post comments.

    • @mxb Web apps in a native wrapper has never resulted in quality applications before, and I doubt this will end up much different. I’m all for options, but history keeps repeating itself.

      • 0 votes
      • that's true but, on the other hand, we can (sadly) see a rise of electron-based desktop apps which are a huge performance killers but still people develop and use them on a daily basis

        • 1 vote
        • @gabek @mxb But now we have PWA that are very good for certain use cases. I wouldn't see PWA as a replacement for native applications, just a way to ship a better Web experience.

          • 0 votes
        • @mxb the title is a little misleading... my understanding is that the developer still need to provide an APK that depends on Chrome because what it does is just indicating to Chrome to "install" a PWA from a certain address

          • 1 vote
          • @mxb This sounds like an alternative to React Native, Cordova, etc. Now you can take your existing web app and compile a simple Android shell for it to add native features. Hopefully, we'll see this expand. I want these hybrid apps to run using my default browser not Chrome. And ingesting these apps automatically could be a cool next step.

            So a Prismo TWA when? :p :pwa:

            • 1 vote
            • i have absolutely no knowledge about PWA but will definitely research this :) i think that's pretty neat

              • 1 vote
              • @mxb A PWA would be great, but after thinking about it these hybrid TWAs wouldn't be feasible for federated projects. The software could implement PWA support but an admin for each instance would have to build and deploy the Android app shell since its per domain.

                • 0 votes
                • true that, but i can actually imagine instance admins doing that :) That would just be a part of process of hosting their prismo instance

                  • 1 vote