4 ms·
> You can get a developer account, build and sign your own executables, and run whatever you want on your iPhone. Sure, for an extra $100 every single year. Ap
by Wowfunhappy 7y ago
> You can get a developer account, build and sign your own executables, and run whatever you want on your iPhone.
Sure, for an extra $100 every single year. Apple charging money for a feature does not protect users.
- jchb 7y ago> Apple charging money for a feature does not protect users. The $99 is not likely to make them money. It is a token fee to protect the app store from the simplest spam and scam apps.
- npongratz 7y agoSure, it's a mere token for Apple, but it is a significant, recurring financial and logistical hurdle for me when I simply want the ability to use my pocket computing/surveillance device -- which I've already paid for -- in ways I deem fit.
- zaroth 7y agoThis is a pretty significant shifting of the goalposts. The argument was users should have the ability to run whatever code they want on their iPhones. That is actually possible today. It costs a $100/year, which considering the costs of the phones is pretty reasonable. Part of the reason it has to cost something non-trivial is because otherwise it would encourage massive piracy, which would devalue the entire App Store (in fact exactly what we see on Android). If the argument is users should be able to run whatever code they want, but they also must have free access to the development tools and resources like Xcode and Dev Center (which cost how many tens or hundreds of millions to develop?) then you’ve totally lost me. I understand and appreciate the principle that it should generally be possible to develop and run the programs of your choosing on smartphone-type hardware. In no way should a company be forced to spends millions of dollars to facilitate that at scale if that’s not their business model, particularly when it would primarily be used to directly attack their ecosystem.
- Wowfunhappy 7y ago> The argument was users should have the ability to run whatever code they want on their iPhones. That is actually possible today. Technically possible, fine. But there's a big gulf between "possible" and "not extremely painful". Let's say I create a personal fork of the open source Bitwarden password manager, to add some trivial quirk that makes the software better fit my life. How do you propose I actually use my custom version without paying Apple an extra $100 per year? Every 7 days, my version of the app will suddenly refuse to launch, until I get back to my computer and re-sign it. I would need to create a weekly calendar reminder, and never go on vacation without a computer nearby. Oh, and I'd better not have more than three of these forks, because that's another limitation for free accounts. The 7 day limit is not Apple refusing to provide "free access to the development tools", it's an artificial restriction explicitly created to make running un-blessed code impractical for more than rudimentary testing.
- zaroth 7y agoIt sounds like the problem you have isn't that it's not possible, but that it's not free (as in beer). The free account is good for playing around with the environment and learning how to write code for iOS. It is not well suited for running production software on your phone. If you want to run production software on your phone, blessed or unblessed, you probably want to pay Apple $100/yr for the longer duration and higher app limit. In my opinion, if you could do what you wanted for free, it would contribute massively to app piracy, and devalue the work of millions of developers on the App Store. $100/year is at about the right level to dissuade most people from circumventing the App Store (the average Apple user spends ~$75/year on the App Store). > ...it's an artificial restriction explicitly created to make running un-blessed code impractical for more than rudimentary testing. Crucially, paying Apple $100/year does not mean they ever see or have to bless code you deploy to your own devices. It just removes the limits in the development environment!
- Wowfunhappy 7y agoAllowing side-loading would probably contribute to app piracy somewhat, but I don't think it would have as large an effect as you describe. Android's customer base is less wealthy overall, and less likely to have payment information in the play store. I would look to Mac rather than Android for a more realistic picture of what the piracy landscape would look like. It's not bad. But, I also fundamentally believe we shouldn't be restricting user freedoms to protect copyright. $100 a year is completely and utterly cost-prohibitive for a lot of people, even within the context of someone who already owns an iPhone. A lot of children begin coding so they can create something for themselves, or change one thing in an application. With a 7-day limit, who would want to do that? While it's true that free accounts can technically experiment with coding, there's not much incentive when you can't really _use_ anything you've created. I worry about a generation of children who is given iPads rather than computers. Sure, most of them would never have touched code anyway, and that's fine. But iOS completely removes the incentive to learn and explore—to actually hack and tweak and create the tools we use everyday, instead of blindly consuming them.
- ceejayoz 7y agoThat hasn't been the case since 2016, when Apple changed it so the fee is just needed to publish to the App Store.
- Wowfunhappy 7y agoNo, it's also needed to install a self-made app on my phone for longer than 7 days at a time. That 7 day restriction is far too low to be reasonable for normal use.
- zaroth 7y agoIf you want to develop applications (or run arbitrary code) on their stack, which they spend billions of dollars developing and maintaining, yes, it will cost you $100/year. Or you can get a free dev account, but the feature set it more limited and signatures are only good for 7 days. Apple charges money for features so that they remain in business to keep making more features, and security updates too. So it is, in fact, exactly how they protect users.
- Wowfunhappy 7y ago> And signatures are only good for 7 days. And again, how does that restriction protect users? As I see it, it's entirely user-hostile: it ensures any self-created apps aren't really usable. If the limit was significantly longer, I would mostly shut up about all of this.
- nindalf 7y agoWho is this hypothetical person who can afford a Mac and the time to learn how to how to develop iOS applications and yet cannot afford $100 a year? Usually I'm all in favour of freedom, but I just can't see who's actually affected by this.
- AnthonyMouse 7y agoIt's the person who doesn't know how to do that yet. Most people don't get started in software development by writing their own operating system kernel. They're using an existing application with published source code and want to make a little change. It's an ugly hack written by a teenager, they just want to use it for themselves. They'll get better at it as they do it more. But now you say they have to buy a Mac and pay $100/year. Well, that's a no for that little initial change, so now they never get started to begin with.
- Wowfunhappy 7y agoOkay, here's a personal example: Apple does not allow dictionary apps on the App Store which actually use the word definitions built into iOS—they are required to provide their own definitions, which either take up precious storage space or are not available offline. So, I found some old WTFPL-licensed code on Github, spent an hour or so futzing around to make it compile and look pretty on iOS 12 (because I had no clue what I was doing), and came up with this: https://github.com/Wowfunhappy/Dictionary https://github.com/Wowfunhappy/Dictionary. It works super well, and I use it every day on my phone. The only reason I can use this app is because I'm Jailbroken.