Spotify to axe 1,500 workers to save costs

Re:Spotify to axe 1,500 workers to save costs by spacebanana7 on Monday December 04, 2023 @05:24AM (#38515656)

Spotify has a lot of front ends to manage, I think more than 20 would be required.

Mobile (iOS, Android), web, vehicle native integrations (Tesla, Volvo, VW, BMW, Audi, Ford), gaming (Xbox, Switch, PS4, PS5), desktop (Mac, Windows, Linux, Chromebook) and voice assistants (Alexa, Google).

Maintaining that variety of front ends must be very labour intensive.

[ Parent | on HN ]

Re:Spotify to axe 1,500 workers to save costs by creshal on Monday December 04, 2023 @07:28AM (#38516444)

Spotify uses Chromium embedded for their desktop clients and webviews for their mobile clients, so that's largely one codebase for 6+ clients.

A lot of the external frontends are also not made by spotify themselves, but implemented by the manufacturer through Spotify's SDK.

You still want a bunch of dedicated staff to support all that, but it's not as dramatic as it could be.

[ Parent | on HN ]

Re:Spotify to axe 1,500 workers to save costs by ViewTrick1002 on Monday December 04, 2023 @06:57AM (#38516209)

Let us not forget:

TVs, Wifi connected speakers, home theater systems, Chromecast etc.

[ Parent | on HN ]

Re:Spotify to axe 1,500 workers to save costs by pdimitar on Monday December 04, 2023 @05:29AM (#38515685)

Hm, solid point, thank you.

[ Parent | on HN ]