Which Client? PWA vs Desktop vs Native App

[N_G]

Many users followed our advice to deploy our PWA web app mode instead of our Desktop App during the attack. Following this, we learned more about deploying in this mode. I wanted to share some of the things we’ve seen and give some background and suggestions on which is the best to use according to the situation.

The PWA (Progressive W...​

Continue reading the Original Blog Post.​

 

[weimerd]

Thanks Nick for the comparison as well as the outlook to a new native windows app that is being distributed to Microsoft Store. Can't wait for the TAPI integration as this is the biggest issue for us actually. I know: TAPI is old. But many clients are using CRM software that relies on TAPI to communicate with any phone system. We are not selling/promoting the old Windows client with TAPI functionality actually as it is pretty outdated.

So heads up: I really appreciate the new development way. Cheers to the whole team!

 

[N_G]

Thanks for the headsup @weimerd... We plan to add TAPI to our Desktop app too so you have something faster.

 

[CallingFromMars]

@nick
Is it possible to have hotkeys for PWA, too? Like with the Desktop App or Browser extension in the past?

 

[Osney Osmar]

Finally the native windows app will be back and revamped this is wonderful.

 

[SteveITS]

"What the Desktop App requires

• Local admin rights to install the app"

So this is a change and it will not be installed in AppData anymore? Will it have a way to self-update for standard users, such as an update service?

 

[N_G]

Maybe i made a mistake there, nothing has changed with the DesktopApp installation. I will check and revert

 

[Ingo Wilczak]

There is on Feauture missing in the comparison between the PWA and Desktop/Legacy App.

The Desktop and Legacy App has the Hotkey Feature, which the PWA does not have.

 

[Ingo Wilczak]

Maybe i made a mistake there, nothing has changed with the DesktopApp installation. I will check and revert

From what i know, the Desktop-App does not require Adminrights for installation

 

[Ingo Wilczak]

Oh sorry, i didn't see the updated Blog-Post which adresses both points

 

[bbaker73]

@Nick Galea

What the Native App requires​

• Local admin rights to install the app.
• Provisioning via PNP on local LAN OR download of config file (U8).

Are you indicating in update 8 we'll be able to download the config file (no longer in the welcome email on 7a) so that we can still deploy native app in remote environments off lan without vpn?
Also can you clarify that exiting configured native apps will continue to function if provisioned, just during this transition through 7a to 8 we won't be able to provision any new native apps off lan until update 8?

Thank you!

 

[N_G]

@Ingo Wilczak @SteveITS I am sorry the blog post has a mistake - local admin is not required, I will update the blog
@bbaker73 Yes you can download the config file from the client this will most probably be in update 7a already, no need to wait for 8

 

[PrismaComputer]

Just because 3CX officially does recommend to further use PWA app:

• PWA does not support shortcuts.
• PWA doesn't support link handling. Links to the webdialer (https://xxx.xxx.xx/webclient/#/call?phone=1234567890) should be captured and processed by the app instead of opening a new tab.
  See: https://learn.microsoft.com/en-us/microsoft-edge/progressive-web-apps-chromium/how-to/handle-urls