#SLACK CLIENT ALTERNATIVE FULL#
#SLACK CLIENT ALTERNATIVE SOFTWARE#

Especially for companies with the scale and budgets of Github or Slack. But using an embedded web view of any kind feels incredibly, incredibly cheap.

#SLACK CLIENT ALTERNATIVE FULL#

I firmly believe going full native is the most user-friendly option, but I appreciate the increased cost and complexity of development, testing, support. Even if a Hello World app was 200mb shipped and took 500mb of ram to run, it's still on the developers to get it to a state where it's an order of magnitude worse once it gets to do something useful. Might have been a better choice to build directly on raw Webkit. But the developers instead chose to plug in all the extras from Chrome (?). for all intents and purposes, as alternative clients that also happen to be.

Nach oben sind der Nutzeranzahl nur durch den jeweiligen Server Grenzen gesetzt. Nutzer loben besonders die problemlose Skalierbarkeit.

Auch wenn Sie Ihre Prozesse bereits auf einer Public Cloud hosten, fügen Sie Mattermost einfach in die Umgebung ein. So at the time Electron was founded, it might have made more sense to ship Webkit on Windows. Your Slack client strives to be a consistent, compact, zero latency. Die Slack-Alternative lässt sich einfach in Ihre bestehende Vor-Ort-Infrastruktur einbauen. How does using 2 or 3 different rendering engines solve the problem for the developer? They have to now put in the extra effort and QA for each engine/platform. So which one is the 'native' web view on Linux / BSD? Use whatever version of Webkit is supplied by the distro? This is a security nightmare, as these are outdated and full of bugs more often than not. And even then, assuming the new features are only designed for ~50% of users, because users don't typically use every feature of a product, you'll only actually see 1 in 20 changes that the Slack team build. As an end user we probably only get ~10% of the changes – 90% may be experiments that never see the light of day but still have to be built in order to find the 10% that are worth it. not being Electron apps in certain areas, and sacrificing adaptability for that.Īlso, Slack doesn't change _that_ much right?! Well yes and no. Yes there are faster Electron apps, but typically they manage that by. That feature is probably vastly more impactful than improving system integration.įor there to be features like that, or an ecosystem of third party integrations, speed of development is likely a huge factor, and for that, being able to share the codebase across web and desktop apps is likely a no-brainer.Īs much as I'd love to see a more performant Slack, it's likely that it would have large negative impacts on the speed of iteration elsewhere, and so I can understand why they don't do it.

#SLACK CLIENT ALTERNATIVE SOFTWARE#

Let me say up front that I really dislike the Slack app, but I do think this comment is unfair on Slack.įor them, the biggest lever to improved user experience is almost certainly _product features_ not performance or native integration.Īs much as I'd like drag and drop support or less RAM usage, Slack are mostly trying to convert people who have never used instant messaging in the workplace to using it daily (which I think is overall a win), and mostly trying to make users who are not as comfortable with software as we are use a new piece of software.Īs an example, when I share a Google Docs link in Slack, I get a prompt from Google Docs _in Slack_ with a one click button to 'fix' sharing so that those in the channel will be able to see it.

Slack client alternative