3 ms·
So I built a very basic prototype app to explore an idea I had using Flutter (imagine something like a time boxing system where you track how frequently you get
by mikenew 5y ago
So I built a very basic prototype app to explore an idea I had using Flutter (imagine something like a time boxing system where you track how frequently you get distracted). Spent a couple days roughing it out, and then I was able to load it onto my own Android device to start testing. Literally just plugged in my device to my PC, confirm the prompt on the phone, and then `flutter run -d <device_id>`. I also wanted to send it to my brother (who has an iPhone) so he could start playing with it too.
So I had to pay Apple $100 to open a developer account. Then sign a bunch of contracts. Then register an app ID and generate certificates. Then bundle the app and submit it to appstoreconnect. Then wait for a bunch of automated checks to pass and tell me that the app ID is missing entitlements. Then figure out what that even means, attempt to fix the entitlements, and run through the submission again. Then set up testing groups and invite my brother to test the app. Then I have to "submit" the app for approval for testing. And a couple days later finally get approval from Apple so that I can start testing it. And that's the short version; there were a bunch of nonsensical Xcode quirks to deal with.
For context, I've been an iOS developer for a decade, and it still took me the better part of a weekend to get through it all, even though I know exactly what to expect. And this is so one fucking person can try an app for me.
I hate Apple. I don't know how else to put it. I don't think they're evil, I just think they don't give a shit about their developers. Did you know their bug tracker is private? I'll find some weird behavior with, let's say UITableView or something, and spend all day trying to figure out what subtle thing I'm doing wrong using their comically poor documentation. And then somewhere buried in Stack Overflow I'll find someone saying "oh yeah that's a bug in the framework, I submitted a radar 2 years ago". So there's some bug that they know about, and I'm not even allowed to see that. It feels hostile on their part, and it makes me feel hostile on my part. I think Paul Graham was right.
- collaborative 5y agoJust wait until you have to manually type "what's new" in each release in each different language your app supports that perhaps adds an invisible fix the user couldn't care less to know about. Oh, and appstoreconnect is designed to prevent you from automating this. This huge time waster is what really makes my blood boil when I think of Apple
- reayn 5y agoNot to be the devil's advocate here but... that seems fine to me? Lots of more technical people complain about terrible changelog entries (I've seen quite a few posts on HN about it too iirc), so I guess no matter what Apple does in this case they'll be a target; just that kind of situation. Maybe it could be a per-project toggle whether having a "what's new" section is necessary (though on second thought toggling that off might become the new norm leading back to the good old useless changelogs).
- collaborative 5y ago90% of updates change things that users would be offended to be told about. They would say "why do I need to know this?" Example: changing width of buttons x y and z under sub menus a b and c to support x y and z device edge cases. In these updates, devs just paste the same "what's new" they wrote for the previous release (which has the info that actually matters, like something new users want to hear about). Releases don't go from 1.1 to 1.2 in mobile, they go from 1.1.43.1 to 1.1.43.2. Having to manually type the same thing in 32 different languages for such small changes is what makes you really dislike the process. You can just select your release notes from the last release on the Play Store