@paulcbetts i have been tested a beta version of slack lately which was already faster. is that any different?

@ourielohayon The Beta app you've been testing is in preparation for this release - folks on the beta will be updated automatically to 2.3.0

@paulcbetts @ourielohayon I had the same question as Ouriel. Should we remain on the beta for future updates, or revert back to the normal app?

@cutlerdave @ourielohayon Nope! Everyone on the beta is seamlessly migrated to the latest version, no need for a separate download (we actually shipped the final bits to beta users on last Friday)

@cutlerdave @paulcbetts @ourielohayon Hi! You can stay on the beta. You'll automatically receive new builds of the Slack app before they become public.

@rrhoover Hey Ryan, Is switching teams painful because of performance? Or because you have to log in to more than one of them?

@paulcbetts @rrhoover at least for me its logging in seperately (at least the ones without SAML/GApps). I have a school team, club teams and as a freelancer a lot of client teams. For me simply logging in once would be much easier.

@rrhoover Pain? Login once and then just CMD+1, CMD+2 etc?

@paulcbetts @rrhoover In my opinion, it is very hard because you need to log in all the time with the same username (email) for each team and I don't understand why I need to log in again on the desktop when I'm already log in on my mobile.

@paulcbetts separate logins for different teams is so wonky and clunky (technically speaking). would be cleaner to have one account that is given access to the different teams.

@tehsuck We Think That's Cool Too :)

@bitandbang We write about this a bit on our blog over at slack.engineering - basically at the time the original Slack app for Mac was written, Electron didn't exist! Slack was actually the first production app outside of Atom to use Electron (in fact, the very first internal releases of Slack for Windows were called "atom.exe" because you couldn't rename the executable without breaking it). Node modules make it fairly easy to load per-platform code, so we're able to integrate with the platform, imho this is the thing that makes Electron different from other platforms like Phonegap - if you hit the edges of what Phonegap provides, you're stuck - with Electron, you've always got an escape hatch if you're willing to write enough C++ :)

@esqarrouth It's now neither old nor laggy!

@paulcbetts So should I uninstall the old one and install this one?

@laurex Hi Laure - if you're into keyboard shortcuts, you can use CMD+1, CMD+2, CMD+3, etc to nav between teams.

@laurex In the new app, the team switcher is scrollable, give it a try!

@nami How does that work for teams 10-19? :)

@paulcbetts @laurex This was the first thing I noticed on the beta. Had just run out of room for teams when the beta hit. Scrolling is awesome!

@joshdance Hm, we'll try to make this better!

@daniel_a_a Accessibility is enabled only if Voiceover is enabled, because enabling it hurts performance. We'll look into changing this in the future, but we'd probably rather create a real API for this instead of having people have to hack their way in

@nadomars We definitely hear the feedback we're getting around logging into >1 team with the same identity. This gets a little more tricky when you think about the edge cases though - for example, which of the N team admins gets to set things like password policy or requiring 2FA for your single identity? Anyways, we definitely sympathize with The Problem and we'll do our best to come up with a good solution

@paulcbetts @nadomars You guys should go the route of a slack specific username login. Each team could still have company specific email logins, but it can be tied to the slack username. I may be off because I'm lying in bed and I don't dev anything..

@yo I'm not sure about this, but I think that a lot of people use slackin for this

@natesmoyer Cool idea! I think YouTube Live Video _should_ work, but it's definitely an interesting concept