3 ms·
I wonder if Apple will apply this rule to everyone, which would be fair, or if they plan on letting big name developers like Facebook or Google continue to viol
by RKearney 10y ago
I wonder if Apple will apply this rule to everyone, which would be fair, or if they plan on letting big name developers like Facebook or Google continue to violate the rules without consequence.
- LeoPanthera 10y agoThey should pull the Facebook app for this. But I'll eat my hat if they do.
- empthought 10y agoTheir guidelines specifically say that, with prior authorization, the prohibitions do not apply.
- chii 10y agounfortunately, just like any other private platform, they don't need to be consistent or follow the rules all the time. I say, don't go native unless you must (for performance reasons etc). push the web forward instead!
- kyrra 10y agoAre there any sites that document Facebook or Google using hot code push on iOS?
- cbhl 10y agoI'm not sure if they still do this, but Facebook used to ship both code paths in the app binary for new launches, and give Apple instructions on how to test both code paths (e.g. sign in with this special user/pass combo). So they weren't changing app functionality after App Review approval; it's just that for users some of that functionality was gated on a boolean that was fetched over HTTPS.
- geofft 10y agoPutting code behind a feature flag seems entirely fair and a good idea for developers of any size. It's also a thing that can easily affect small developers; if your app requires logging into some existing paid account (enterprise software, a bank's app, etc.), the available features depend on what features the account has paid for. So as part of the review, you send Apple credentials for a test account that has all the features enabled. (Without a test account, they couldn't log in at all.)