News for hackers. Stuff that matters.
Re:Addressing Spotify’s Claims by revel on Friday March 15, 2019 @09:10AM (#19399328)
I love how brazen this letter is.

> Apple’s approach has always been to grow the pie.

Apple's approach has always been to grow it's own pie. They have never been even remotely interested in playing nicely with other companies. I don't fault them for it, but let's not kid ourselves here; the app store is largely an extremely profitable exercise in rent seeking.

It's not like this is new for Apple; they've had proprietary cables and adapters for as long as I can remember. Developing software for their hardware has always meant using Xcode, which, surprise, is not free. Literally every other platform has given away tooling and emulators, but that's never been true for Apple. Occasionally this kind of behavior works out well for customers -- they were unafraid to use their market power as a cudgel to kill off Flash (which I think we can all agree needed to happen) -- but all too frequently it's purely anti-competitive. Apple has created some incredible products and services over the years, but let's not kid ourselves about this; this is simply a way of extracting value from Spotify.

Re:Addressing Spotify’s Claims by simonh on Friday March 15, 2019 @09:33AM (#19399521)
There’s a thread of truth in what you’re saying, but it unravels on close inspection.

Proprietary cables are hardly new, and to be fair those cables and connectors are usually way better than the standard stuff. Firewire and thunderbolt were actually released as open standards and saw decent adoption. Lightning is far superior to Micro-USB. Just listen to the wailing and gnashing of teeth by Macbook owners having to give up proprietary MagSafe for USB-C charging on their laptops.

XCode is free and has been for ages. To this day you can develop whatever you like for the Mac and not pay Apple a penny. You don’t even have to use XCode to do it. It’s even free for iPhone development for your own device now, though you have to pay a fee to publish stuff. I’m not sure what you comment about emulators is about to be honest, The iOS emulator for the Mac is free.

Yes they want their cut from Spotify. I don’t understand the Apple exceptionalism about this though. Nobody rages on HN about Sony’s monopoly over games development for the PlayStation, or Microsoft for XBOX, or Nintendo for the Switch, but for some reason Apple which came to this business model two generations late is the root of all evil. It really is kind of weird how that works. Maybe if their iconic image was a cute little plumber instead of a half eaten fruit, everyone would say 'Aww how cute' and give them a pass.

Re:Addressing Spotify’s Claims by rhodysurf on Friday March 15, 2019 @10:25AM (#19399957)
XCode is free and has been for ages. To this day you can develop whatever you like for the Mac and not pay Apple a penny. You don’t even have to use XCode to do it. It’s even free for iPhone development for your own device now, though you have to pay a fee to publish stuff. I’m not sure what you comment about emulators is about to be honest, The iOS emulator for the Mac is free.

True it is all free except the whole having the purchase a 1000 dollar computer part.

Re:Addressing Spotify’s Claims by HenryBemis on Friday March 15, 2019 @10:44AM (#19400140)
And there is the Apple dev annual subscription.

By the way, I have (in the past) managed to run macOS on Vmware successfully, but one needs a pretty strong PC to make this work without having the fans lifting the PC off the groud.

Re:Addressing Spotify’s Claims by dev_north_east on Friday March 15, 2019 @11:26AM (#19400533)
> And there is the Apple dev annual subscription.

Only if you're publishing.

Re:Addressing Spotify’s Claims by Phillips126 on Friday March 15, 2019 @12:39PM (#19401345)
We had to pay $299 for the enterprise license to distribute iOS applications internally to just our staff[1]. This circumvented the App Store entirely and we used MDM tools (AirWatch) to distribute. Was this avoidable? I'm genuinely curious as I am not specifically an iOS/Mac dev.

[1] https://developer.apple.com/programs/enterprise/

Re:Addressing Spotify’s Claims by larkost on Friday March 15, 2019 @01:19PM (#19401886)
No. In order to publish (even just within your organization) you need to establish a trusted relationship, and Apple charges for that. There is plenty of room for argument about how much Apple should be charging for this, but the process does have some costs to Apple, so it is only right that they charge something.
Re:Addressing Spotify’s Claims by hellisothers on Friday March 15, 2019 @11:25AM (#19400519)
This is a disingenuous argument, you have to buy a PC to develop Windows. And you have to pay $100-300 for windows, AND you have to play $600-$2500 _per year_ for Visual Studio
Re:Addressing Spotify’s Claims by detaro on Friday March 15, 2019 @11:29AM (#19400563)
You can develop for Windows without Visual Studio, and Visual Studio has a free tier that includes some commercial usage. If you own pretty much any desktop computer or laptop, it can run Windows (including Macs). I think you can even get Windows licenses for testing purposes for free, if you prefer to work on macOS or Linux and just test on Windows (EDIT: on reviewing this part, the terms on those test images aren't as clear as one would like, even though they clearly are provided for developers, so count cost for 1 license if you want to be sure).
Re:Addressing Spotify’s Claims by dalore on Friday March 15, 2019 @12:34PM (#19401282)
No it's not. You can buy a PC from many different vendors, HP, Lenevo, Dell etc. They compete and the price goes down, and customers get a choice. You can also run linux for free and use VSCode for free which also runs on Linux.

With Apple I have to buy the PC from Apple at it's marked up price since no competition. So it is a fair point.

Re:Addressing Spotify’s Claims by simonh on Friday March 15, 2019 @12:49PM (#19401501)
What do you mean no competition?

Why on earth would you want to develop Mac software without buying a Mac? This argument really does make no sense at all. It’s like complaining that if you want to drive Porsche, you have to buy a Porsche from Porsche. Er, yeah. That’s how that works.

Please quibble about renting and dealerships or something. Please. I dare you. I double dare you! I swear I won’t stop laughing for a week.

Re:Addressing Spotify’s Claims by dalore on Tuesday March 19, 2019 @06:41AM (#19429604)
Dare accepted. You know that is a false analogy. If you want X you need to get X.

It would be more like a mechanic being required to buy his tools from Porsche to be able to work on a Porsche.

And it's good you bring this up, this too is a problem in the auto industry world. Car manufacturers are pulling these stunts and creating locks for their cars so only approved tools can be used with it.

To continue the analogy, it would be like buying an Epson printer and being force to use Epson ink. Or buying a house and being forced to buy your DIY suppliers from the real estate agent.

We can keep going with analogies all day.

Re:Addressing Spotify’s Claims by learc83 on Friday March 15, 2019 @11:40AM (#19400675)
Visual Studio Community (which is everything you'd need if you aren't a large team) is free. You can use it for up to 5 users for commercial work.
Re:Addressing Spotify’s Claims by bena on Friday March 15, 2019 @12:06PM (#19400922)
I use Community professionally.
Re:Addressing Spotify’s Claims by coryfklein on Friday March 15, 2019 @01:08PM (#19401744)
Your personal accusation of disingenuousness distracts from what would otherwise have been a good point. Let's see what a barebones setup costs for developing with a solid IDE on each platform:

macOS:

$800 Mac Mini (Apple's most affordable offering that runs macOS)

$90 Acer SB220Q Monitor

$FREE Xcode

Total: $890

Windows:

$200 Dell Inspiron 11 3000 (Most affordable Dell PC I could find being sold new)

$1200 One time payment for Visual Studio (but you don't get updates)

Total: $1400

So if have to both buy a computer and need a full featured IDE then Visual Studio's license wipes out any savings you get from avoiding the "Apple tax". It gets even worse if you want perpetual updates to Visual Studio which cost $800/year but come free with XCode.

This is counter to what I had expected beforehand myself, I expected the "Apple tax" to make the bar of entry much higher than PC development.

If, on the other hand, you can get by with a less advanced IDE or are developing in a non-proprietary language like Java, Python, or Scala the cost goes way down:

Cheapskate Option:

$200 Windows/Linux laptop

$FREE Eclipse/JetBrains CE IDE/Visual Studio Code

Total: $200

This is certainly more affordable than the $800 macOS alternative. Although one could debate whether the above mentioned IDEs are on equal footing with XCode/Visual Studio.

Re:Addressing Spotify’s Claims by AlotOfReading on Friday March 15, 2019 @03:32PM (#19403336)
Visual Studio Community is free. It doesn't have the fancy cloud/devops enterprise-y stuff, but it's not like Xcode does either.
Re:Addressing Spotify’s Claims by coryfklein on Friday March 15, 2019 @04:50PM (#19404165)
Ah! I didn't know Visual Studio Community was even a thing. Figures though, since I've never used either.
Re:Addressing Spotify’s Claims by arsenico on Friday March 15, 2019 @12:25PM (#19401160)
This is incorrect - you can go and buy a used Mac Mini for 250USD.
Re:Addressing Spotify’s Claims by vinceguidry on Friday March 15, 2019 @01:06PM (#19401703)
> Yes they want their cut from Spotify. I don’t understand the Apple exceptionalism about this though.

No Spotify's letter put it very clearly, they want to take their 30% cut from Spotify while putting their own music service on the market undercutting their prices. This is blatantly anticompetitive and is rightly being slammed by Congress.

Apple's response to this has been shrug. I don't think Apple shouldn't be allowed to offer their own music service but they shouldn't use anti-competitive practices in order to stifle competition.

Re:Addressing Spotify’s Claims by graeme on Friday March 15, 2019 @01:12PM (#19401801)
Did apple music price below spotify/ not familiar with the pricing history.
Re:Addressing Spotify’s Claims by vinceguidry on Friday March 15, 2019 @01:20PM (#19401898)
They used shady tactics to force them to bill through the Apple's marketplace so they could get the 30% cut, forcing Spotify to raise prices by 30% so they could maintain their revenue position. Then they released Apple Music at the $9.99 price point that Spotify was at previously.

The shady tactics resumed when Spotify stopped using the App Store to bill and reduced the price to compete with Apple Music. Apple isn't interested in competing with Spotify, only with freezing them out of the market.

Re:Addressing Spotify’s Claims by andromeduck on Friday March 15, 2019 @06:20PM (#19404857)
Shady tactics like lowering the cut to 15% after 1 year.
Re:Addressing Spotify’s Claims by Benjammer on Friday March 15, 2019 @03:24PM (#19403267)
Why does the value of Apple's App Store infrastructure and network effects always get zeroed out in the equation here? Spotify is welcome to build their own app distribution infrastructure on their own mobile hardware and charge whoever whatever they want for it and keep all the profits themselves.
Re:Addressing Spotify’s Claims by vinceguidry on Friday March 15, 2019 @04:11PM (#19403757)
Apple does not offer a legitimate way for developers to release apps for their hardware other than the App Store. I suppose you could go even further and say that Spotify should make and market their own phones, but luckily American commerce doesn't work that way.
Re:Addressing Spotify’s Claims by therockhead on Friday March 15, 2019 @10:03AM (#19399751)
Historically the console manufacturers sold their consoles at a loss and only made profit on games sales. This might have influenced our perspective on the sales model.
Re:Addressing Spotify’s Claims by simonh on Friday March 15, 2019 @01:32PM (#19402045)
Not always. Nintendo was making a profit in each Wii sold, as a unit, from day one.
Re:Addressing Spotify’s Claims by robert_foss on Friday March 15, 2019 @10:13AM (#19399840)
XCode may cost you 0$, but you have to buy a Mac to use it. And those things are >0$ in most cases.
Re:Addressing Spotify’s Claims by philistine on Friday March 15, 2019 @10:54AM (#19400228)
Instead of having Xcode be available on PCs, which we all know are free to own.

Yeah, right.

Re:Addressing Spotify’s Claims by EthanV2 on Friday March 15, 2019 @11:01AM (#19400289)
I guess the point is you might already own a PC, and you could use that for developing Android apps, for example. But if you also want to use Xcode and develop iOS apps as well then you have to buy a Mac.
Re:Addressing Spotify’s Claims by mcphage on Friday March 15, 2019 @02:39PM (#19402810)
> you might already own a PC [...] if you also want to use Xcode and develop iOS apps as well then you have to buy a Mac.

You might already own a Mac.

Re:Addressing Spotify’s Claims by mdorazio on Friday March 15, 2019 @03:18PM (#19403209)
And if you own a Mac it costs $0 to develop for any other platform. See the imbalance here?
Re:Addressing Spotify’s Claims by pjmlp on Friday March 15, 2019 @03:38PM (#19403411)
No, it costs 100 euros to get a proper Windows license.
Re:Addressing Spotify’s Claims by mdorazio on Saturday March 16, 2019 @08:56PM (#19411468)
No, you don't need a Windows license to develop for Windows. That's the whole point here. You can code and compile binaries for Windows, Linux, Android, etc. from many IDEs and virtually any platform under the sun. You can code and compile binaries for Apple products from exactly one IDE and exactly one platform: Apple's.
Re:Addressing Spotify’s Claims by pjmlp on Sunday March 17, 2019 @01:41PM (#19415199)
Of course you need Windows to develop Win32 and now UWP apps.

If you mean cross compiling from other OSes into Windows, good luck creating anything beyond CLI apps based on POSIX.

Ah but there is Wine! Not really, there are tons of Windows features that it doesn't support, and probably never will.

And if you mean Web apps, then I also develop Webapps for Mac without having one around.

Re:Addressing Spotify’s Claims by georgespencer on Friday March 15, 2019 @11:49AM (#19400761)
If that is the point it's not a very good one.
Re:Addressing Spotify’s Claims by jessemillar on Friday March 15, 2019 @10:26AM (#19399971)
While I understand your point, I would gently argue that to develop a truly great macOS or iOS app, you somewhat need to live in the Apple ecosystem to understand the design guidelines and quality that Apple customers have come to expect.
Re:Addressing Spotify’s Claims by asdff on Friday March 15, 2019 @10:49AM (#19400186)
I bet the most downloaded apps these days are ground up cross platform and identical on every platform, e.g. steam, spotify, and web browsers. Relying on proprietary apple features that you have to clumsily port over to another OS would waste a lot of your time as a dev. You'd probably do your best troubleshooting on a cheap, under powered hackintosh than a model year macbook pro, to be honest.
Re:Addressing Spotify’s Claims by jessemillar on Friday March 15, 2019 @10:51AM (#19400199)
Fair point. I tend to not like those cross-platform apps because of their generally-degraded performance so my previous comment showed a bit of my underlying bias.
Re:Addressing Spotify’s Claims by virtualritz on Friday March 15, 2019 @10:56AM (#19400243)
Yes. But parent didn't contest that. They rather made the point that you have to pay to "live" in that ecosystem. MacOS is officially only supported on Apple hardware ... So it's not free and the fact that XCode is is therefore a moot point to that line of reasoning.
Re:Addressing Spotify’s Claims by Aaargh20318 on Friday March 15, 2019 @10:23AM (#19399941)
You need a Mac anyway, and the costs of a Mac is peanuts compared to the costs of a developer.
Re:Addressing Spotify’s Claims by VectorLock on Friday March 15, 2019 @01:14PM (#19401830)
>Just listen to the wailing and gnashing of teeth by Macbook owners having to give up proprietary MagSafe for USB-C charging on their laptops.

For me personally and I think for a lot of people that is less about a love for MagSafe than it is an aversion to USB-C.

Re:Addressing Spotify’s Claims by vesrah on Friday March 15, 2019 @01:17PM (#19401858)
The difference in the way the USB-C cable and Magsafe handle an off angle tug seals the debate for me.
Re:Addressing Spotify’s Claims by VectorLock on Friday March 15, 2019 @09:16PM (#19405780)
For every time MagSafe saved me from an errant tug there were 100,000 times it inconvenienced me by disconnecting with the slightest movement.
Re:Addressing Spotify’s Claims by umanwizard on Friday March 15, 2019 @01:01PM (#19401650)
Apple publishes an iOS simulator, not an emulator, which is a totally different thing.
Re:Addressing Spotify’s Claims by larkost on Friday March 15, 2019 @01:25PM (#19401957)
Yes, it is different. But how is that important in this conversation. Here the important bit is: have a tool that enables you to test your iOS code on your development machine. Emulation vs. simulation is not generally important in that.

Side note undercutting my point: there are places, like OpenGL where the underlying hardware is significantly better/different and the iOS simulation is not representative of the real environment. Mostly these only matter to high-end games, and there you better be checking regularly on a list of hardware.

Re:Addressing Spotify’s Claims by umanwizard on Friday March 15, 2019 @02:20PM (#19402612)
You’re absolutely right that it’s not important to the conversation; I’m just being pedantic and going on a tangent :) But I have seen enough real bugs due to people not understanding the limitations of iOS simulator realism that I would really like it if more people understood the issue.

It also matters in more than high-performance GPU rendering. It’s easy to miss bog-standard CPU performance or memory leak bugs when you’re running software designed for a 1GB Ram, dual core CPU machine on a 32GB, 8 core machine

Re:Addressing Spotify’s Claims by jonahb on Friday March 15, 2019 @01:50PM (#19402258)
Nobody rages on HN about Sony’s monopoly over games development for the PlayStation

Might be because the App Store is the sole channel. Also, apps are easier to substitute than games, making anti-competitive behavior possible.

Re:Addressing Spotify’s Claims by scarface74 on Friday March 15, 2019 @08:49PM (#19405674)
And even if you buy a physical game for the Playststion, the game still has to be approved by Sony.
Re:Addressing Spotify’s Claims by madeofpalk on Friday March 15, 2019 @09:21AM (#19399403)
> they've had proprietary cables and adapters for as long as I can remember.

Apart from Lightning, which was created when no better alternative existed, I cannot remember a proprietary Apple connector in at least the past 10 years.

Re:Addressing Spotify’s Claims by FireBeyond on Friday March 15, 2019 @12:40PM (#19401368)
The 30 pin connector has certainly been available on devices in the past 10 years.

The Magsafe connector has, too.

As has MagSafe 2...

Re:Addressing Spotify’s Claims by asdff on Friday March 15, 2019 @10:13AM (#19399842)
Any apple laptop video out for the past 15 years?
Re:Addressing Spotify’s Claims by throw0101a on Friday March 15, 2019 @10:30AM (#19400006)
The original MacBook Air had micro-DVI, and then later Mini DisplayPort. Later generations had Thunderbolt. None of these were Apple-only.

The original MacBook Pros had MagSafe, which was proprietary, but DVI for displays (open); later on they had Mini-DP or Thunderbolt The MacBook follows a similar pattern.

So once MagSafe was eliminated, Apple switched to non-Apple-only plugs, though since they were early adopters, it perhaps seemed like it was proprietary. However, Apple did not own (mini) DVI, (mini) DisplayPort, Thunderbolt, or USB-C.

The only Apple-only pugs are/were the old 30-pin iDevice connector and Lightning.

Re:Addressing Spotify’s Claims by sigzero on Friday March 15, 2019 @10:49AM (#19400181)
Rest in peace MagSafe. Wish they would resurrect that one!
Re:Addressing Spotify’s Claims by asdff on Friday March 15, 2019 @11:01AM (#19400292)
Practically speaking, they were mostly an apple only liability. Go to any podium with an apple laptop made before retina when they finally caught up with the worldand stuck an HDMI port in the macbook pro, and you will find the DVI/VGA/HDMI cable that everyone uses, and no way to plug in your macbook if you forgot your 3" dongle. During presentations in undergrad, everyone with a macbook had to email themselves or use a flash drive to bum someone's better endowed laptop to hook up to the projector, because no one ever accounted that they would need a $30 dongle to use the video out on their $1500 laptop. IT started buying these miniDVI or whatever dongles for the podiums, but they wouldn't stay put for very long in the lecture halls.
Re:Addressing Spotify’s Claims by franga2000 on Friday March 15, 2019 @09:27AM (#19399466)
That wide flat thing that looked kinda similar to Samsung's tablet connector? I'm not sure if it was in the last 10y tho...
Re:Addressing Spotify’s Claims by finaliteration on Friday March 15, 2019 @10:01AM (#19399743)
You’re thinking of the Dock Connector, which was last used on the iPhone 4s back in 2011.
Re:Addressing Spotify’s Claims by madeofpalk on Friday March 15, 2019 @11:29AM (#19400557)
And first used in 2003.
Re:Addressing Spotify’s Claims by parthdesai on Friday March 15, 2019 @12:17PM (#19401049)
>Apart from Lightning, which was created when no better alternative existed

Gotcha, then why does new iPhone not have USB-C while new MacBooks only have USB-C?

Re:Addressing Spotify’s Claims by lemoncucumber on Friday March 15, 2019 @02:40PM (#19402821)
According to wikipedia, the USB-C spec was finalized in 2014, while lighting was introduced in 2012. So GP's point was correct that USB-C was not an option when lightning was created.

As far as whether Apple should now migrate from lightning to USB-C, that's a separate question with tradeoffs on both sides.

Re:Addressing Spotify’s Claims by parthdesai on Friday March 15, 2019 @03:01PM (#19403028)
I clearly mention new iPhones, don't i?
Re:Addressing Spotify’s Claims by lemoncucumber on Saturday March 16, 2019 @04:32PM (#19410088)
Yes, and I clearly mention that changing connectors again has different trade offs than if they’d been able to go straight to USB-C in the first place, don’t I?
Re:Addressing Spotify’s Claims by sbuk on Friday March 15, 2019 @01:57PM (#19402349)
Apart from Lightning...
Re:Addressing Spotify’s Claims by parthdesai on Friday March 15, 2019 @02:18PM (#19402588)
>Apart from Lightning, which was created when no better alternative existed...

There is a better universal alternative out there today and yet they continue to use Lightning port in iPhones.

Re:Addressing Spotify’s Claims by sbuk on Friday March 15, 2019 @04:07PM (#19403721)
Do you not remember the caterwauling the last time they dared change the port on the iPhone/iPad?
Re:Addressing Spotify’s Claims by jklinger410 on Friday March 15, 2019 @09:31AM (#19399501)
>Apart from Lightning, which was created when no better alternative existed

They could have easily went with USB-C.

Re:Addressing Spotify’s Claims by madeofpalk on Friday March 15, 2019 @09:35AM (#19399537)
USB-C spec was finalised two years after Lighting shipped.
Re:Addressing Spotify’s Claims by jklinger410 on Friday March 15, 2019 @10:56AM (#19400245)
And lightning works with USB-C. The narrative here is supposed to be that we're all certain Apple was working really hard to try and make a universal adapter to their device and just couldn't because it wasn't far enough along?
Re:Addressing Spotify’s Claims by dasloop on Friday March 15, 2019 @09:32AM (#19399512)
MS tools are not free for commercial as any certification required to sign (was discussed in HN as few weeks ago) apps and installers. 99$/year for that is a better porposal than the one in MS.
Re:Addressing Spotify’s Claims by cnorthwood on Friday March 15, 2019 @09:17AM (#19399368)
Xcode is now free: https://itunes.apple.com/gb/app/xcode/id497799835?mt=12 (although you still have to have a mac)
Re:Addressing Spotify’s Claims by mattl on Friday March 15, 2019 @09:18AM (#19399385)
Still proprietary though, right? With underlying free libraries and compilers?
Re:Addressing Spotify’s Claims by cnorthwood on Friday March 15, 2019 @09:23AM (#19399427)
Yes, it's gratis, not libre. I understood the parent comment to be referring to the price.
Re:Addressing Spotify’s Claims by mattl on Friday March 15, 2019 @09:29AM (#19399482)
I understood it the other way. Proprietary cables to free tools. ️
Re:Addressing Spotify’s Claims by simonh on Friday March 15, 2019 @09:50AM (#19399657)
The components that are specific to the Mac, such as the GUI builder, are closed source. All the underlying tooling and technologies such as the LLVM compiler stack, Clang, etc are published by Apple as open source and widely used on other platforms.
Re:Addressing Spotify’s Claims by tempodox on Friday March 15, 2019 @09:26AM (#19399451)
If you want to publish your stuff in the AppStore, or just install it on your own iDevice, you have to pay a yearly subscription fee.
Re:Addressing Spotify’s Claims by voqv on Friday March 15, 2019 @09:31AM (#19399505)
> install it on your own iDevice, you have to pay a yearly subscription fee.

Not true anymore [1]

[1] https://stackoverflow.com/questions/43932076/how-to-build-ap...

Re:Addressing Spotify’s Claims by emsy on Friday March 15, 2019 @10:05AM (#19399773)
Not only do you still have to hassle with Apple's clunky provisioning profiles, it only lasts for a week and you're almost guaranteed to get an error message because you reached the device limit with as much as one device.
Re:Addressing Spotify’s Claims by Aaargh20318 on Friday March 15, 2019 @10:27AM (#19399981)
> Not only do you still have to hassle with Apple's clunky provisioning profiles

No you don't. XCode takes care of all of that automatically, I haven't had to hassle with provisioning profiles in years.

Re:Addressing Spotify’s Claims by consp on Friday March 15, 2019 @10:51AM (#19400197)
You provide anecdotal evidence (like me) as it requires me to set it manually to work and it has been so for about a year.
Re:Addressing Spotify’s Claims by Aaargh20318 on Friday March 15, 2019 @11:07AM (#19400338)
What do you need to 'set manually' ? You check 'automatically manage signing' and select your team from the list (if you're in multiple teams) and it should Just Work™.
Re:Addressing Spotify’s Claims by oauea on Friday March 15, 2019 @09:48AM (#19399642)
It's ridiculous apple still forces anyone who wants to publish to its platform to have a mac. Had to jump through ridiculous hoops to get automated builds for an iOS app working since our build farm is all Linux (of course).
Re:Addressing Spotify’s Claims by asow92 on Friday March 15, 2019 @10:44AM (#19400133)
Apple has some really nice developer tools and they provide my business a lot of value. I'd gladly pay more for them if I had to.
Re:Addressing Spotify’s Claims by ppeetteerr on Friday March 15, 2019 @12:33PM (#19401261)
> Literally every other platform has given away tooling and emulators

That's so wrong. Try building a game for any console and see how far that assumption will take you.

Re:Addressing Spotify’s Claims by FireBeyond on Friday March 15, 2019 @12:39PM (#19401338)
Since when is a gaming console a personal computer (in any meaningful sense)?
Re:Addressing Spotify’s Claims by ppeetteerr on Friday March 15, 2019 @01:10PM (#19401773)
The argument is around platforms, not PCs. If you're referring to the only other meaningful consumer OS, then you don't appreciate the vastness of the platform market.