V18 Alpha 5: New Native Desktop App

Status
Not open for further replies.
@vvis718 Internal tests were done on Windows Server 2016. Latest version of Windows Server is the 2019.

You can install the 3CX Desktop App for Windows on a terminal server and users will provision with their accounts when they connect via remote desktop. After that they can interact with the application as usual.
That didn't work for us, because it is installed in Appdata. Every user had to use the MSI to install.

It would be very useful if we could open the desktop app via the dialer. This was possible with the Chrome plugin (buttons at the bottom).
 
  • Like
Reactions: accentlogic
Hi, 2 Questions:
1. Will there be a way to provision the Client in ANY WAY on a Windows AD Domain? It would be very important! Or - if this isn’t a way: PLEASE add a command, I can run in netlogon for provisioning on Login!!!
2. Will there be a way to display Contacts from a ODBC Database Source?
Thanks!
 
That didn't work for us, because it is installed in Appdata. Every user had to use the MSI to install.

It would be very useful if we could open the desktop app via the dialer. This was possible with the Chrome plugin (buttons at the bottom).

I suspect you may be able to work around this using a GPO. as I am assuming the installer will need to run as the user account.
 
Hi Everyone.

I just installed the new version 18. I would like to know if this is the version of the RC - 18.0.1871. Also, I noticed that the contacts page does not display the name of most of the contacts in full. What I mean is a contact's last name is abbreviated to just the first letter when viewed in the desktop app. For example, David Peterson is displayed as

David P - {his company name}
080NNNNNNN

It would be much better if it displayed all the contacts information in full.
 

Attachments

  • Contact View 3CX V18.png
    Contact View 3CX V18.png
    4.7 KB · Views: 5
With v16.5 it seemed that the WEBCLIENT would be the present and future of 3CX and many clients stopped using the WINDOWS application. The CHROME extension, click2call in the browser available for CRM integrations like ZENDESK, ...

Now it seems that the future is once again the desktop application and not the webclient ...

For our customers, webclient is undoubtedly preferable, not only because of the integration with CRM and click2call but also because it eliminates the need to install applications in the OS for each Windows user.
 
With v16.5 it seemed that the WEBCLIENT would be the present and future of 3CX and many clients stopped using the WINDOWS application. The CHROME extension, click2call in the browser available for CRM integrations like ZENDESK, ...

Now it seems that the future is once again the desktop application and not the webclient ...

For our customers, webclient is undoubtedly preferable, not only because of the integration with CRM and click2call but also because it eliminates the need to install applications in the OS for each Windows user.
The new DesktopApp is based on the Webclient but encapsulated in a Electron app, which gives it many more possibilities for integrations.
 
  • Like
Reactions: FridayIT
With v16.5 it seemed that the WEBCLIENT would be the present and future of 3CX and many clients stopped using the WINDOWS application. The CHROME extension, click2call in the browser available for CRM integrations like ZENDESK, ...

Now it seems that the future is once again the desktop application and not the webclient ...

For our customers, webclient is undoubtedly preferable, not only because of the integration with CRM and click2call but also because it eliminates the need to install applications in the OS for each Windows user.
Totally agree, it will be a massive job to get the Windows desktop app installed across the whole user base. Intrestingly on Mac the webclient still works in V18. It would be good to have this options for Windows aswell, so users have the choice.
 
Totally agree, it will be a massive job to get the Windows desktop app installed across the whole user base. Intrestingly on Mac the webclient still works in V18. It would be good to have this options for Windows aswell, so users have the choice.
The Webclient DOES work in V18. The apps are complimentary.

The desktop app just replaces the old Windows Client which, by the way, still work on V18.
 
We have also invested a lot of effort in convincing customers to use webclient. And now, from my point of view we go back in that sense
 
  • Like
Reactions: Rhys Haskell
The Webclient DOES work in V18. The apps are complimentary.

The desktop app just replaces the old Windows Client which, by the way, still work on V18.
It does however you need to have the webclient open to recieve any calls.
 
We have also invested a lot of effort in convincing customers to use webclient. And now, from my point of view we go back in that sense
No ones forces you. The app IS the Webclient, in a separate app.

I strongly suggest you test it out before saying it's bad again.
 
  • Like
Reactions: NickD_3CX
It does however you need to have the webclient open to recieve any calls.
The DesktopApp fixes that.

Try it out instead of complaining without knowing.
 
The new DesktopApp is based on the Webclient but encapsulated in a Electron app, which gives it many more possibilities for integrations.
Ok, but we lose other importants. We believe that new versions should give us new things, without losing important functions
 
Ok, but we lose other importants. We believe that new versions should give us new things, without losing important functions
What the hell do you think you lose? IT'S THE SAME THING.
 
The DesktopApp fixes that.

Try it out instead of complaining without knowing.
We have tested the desktop app, and think it works quite well. However, when managing over 3000 users over mutiple countrys it will be a massive task to install the software and support the users through the transition.
 
We have tested the desktop app, and think it works quite well. However, when managing over 3000 users over mutiple countrys it will be a massive task to install the software and support the users through the transition.
It's an MSI file. You can use GPOs or an RMM to deploy it.

Otherwise, it's not worst than when the browser extension had to be installed as well.
 
  • Like
Reactions: FridayIT
Hi

I just wanted to give a constructive note.

Click2call from a web page is somthing so used by our customers, and not all webpages implement those protocols for click2call. So it is something that was and will not be ... Neither is the functionality of being able to receive calls without having the webclient open thanks to the CHROME / EDGE extension ... For our clients these are 2 important things ...

Anyway, it is philosophy question. When you manage a PBX with 100-200-300 users and have a large staff turnover, you will have to spend a lot of time installing the desktop applications. The IT technicians of our customers were very happy when the webclient appeared because it saved them a lot of work. Now, from my point of view, we take a step back in that sense.

We prefer better webclient (not worst) and the possibility of Desktop App. But not webclient without some functions of v16.5.
 
Status
Not open for further replies.

Forum statistics

Threads
111,981
Messages
590,112
Members
164,908
Latest member
FarizQasimov