3 ms·
The pain of forking development into multiple separate teams with completely different technology stacks, bugs, and coordination overhead is just not worth it
by jillesvangurp 7y ago
The pain of forking development into multiple separate teams with completely different technology stacks, bugs, and coordination overhead is just not worth it for most startups. It slows you down when you need to be able to adapt quickly. A lot of unicorns in the past would have addressed this by simply focusing on one platform initially but for an application like this that is not feasible. Even Linux support is not optional for a company like Slack since a lot of the decision makers on stuff like this tend to be in the IT department which in many companies would include at least a few Linux users. By going all in on Electron, they ensured access to all relevant platforms from day one.
The reality is, that most of their user base is completely fine with performance as is, which I agree is not ideal. But it's good enough. My guess is that they will gradually fix issues by benefitting from Electron improvements, swapping out bits of js for more efficient WASM based stuff, etc.
Mostly native app strategies are an extremely bad idea for small start ups these days. You triple the cost (or worse) of your development and inevitably you are going to do better on some platforms than others. I know people obsess about native on platforms like IOS but I find it interesting that there are quite a few unicorns out there succeeding with glorified electron/react native code bases. Slack is basically shipping a web app packaged up as an electron app on Android, IOS, Mac, Windows, and Linux. You can run the thing in a browser pretty much without loss of functionality.
- saagarjha 7y agoSlack is in no way a "small startup".
- jillesvangurp 7y agoThey were when they started out and not getting distracted by a multi platform strategy is what allowed them to stop being one.
- saagarjha 7y agoThey’ve had more than a couple of years with plenty of resources to fix their apps.
- jillesvangurp 7y agoI just explained you how not doing that was crucial to their growth strategy. Not having to coordinate bugs, features, and releases across multiple teams with different tech stacks is really nice when you are trying to outpace your competitors. Most of these follow a similar strategy. Pure native chat apps are not that common anymore.
- kristopolous 7y agoif they can't build a couple binary apps with a $16,000,000,000 valuation then they're doing something seriously seriously wrong. I've worked for companies 1/2000th that with native binaries on all 5 big platforms (linux/win/osx/ios/android).