6 ms·
From https://rollout.io/how-it-works/ https://rollout.io/how-it-works/ : Does Rollout comply to Apple’s Guidelines? Yes. As per Apple’s official guideline
by simplehuman 10y ago
From https://rollout.io/how-it-works/ https://rollout.io/how-it-works/ :
Does Rollout comply to Apple’s Guidelines?
Yes. As per Apple’s official guidelines, Rollout.io does NOT alter binaries. ... With over 50 million devices already running our SDK, it is safe to say that Rollout complies with with Apple’s development and App Store guidelines.
Ouch. Just like the company's future is in danger.
- eridius 10y agoThe first time I saw Rollout I was shocked it wasn't already banned by the App Store. No matter what they say, I can't imagine how they could do what they claim to do without flagrantly violating the guidelines.
- empthought 10y agoIt only started to matter when dumbasses started thinking that using Javascript everywhere was A-OK.
- sctb 10y agoPlease comment civilly and substantively on HN or not at all. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- geofft 10y agoI'm guessing there are two things Apple is worried about. The first is using hot code push to change the purpose of the app after release, e.g., switching a business app into a video game. The second is using hot code push to violate app store review guidelines, like the use of private APIs. You can do hot "code" push techniques that allow the first but not the second, by letting apps update HTML and JS that calls back into pre-existing native code. That's what Cordova / PhoneGap does. I'd guess that Apple will just ban the app and the developer if they catch it. It appears that Rollout started using some API that would enable it to do the second, and Apple is preemptively making sure that it doesn't happen. The wording of the rejection is based on passing computed parameters to introspection routines.
- amluto 10y ago> The second is using hot code push to violate app store review guidelines, like the use of private APIs. I've never understood this part. Why doesn't iOS simply prevent apps from calling private APIs?
- sjwright 10y agoPresumably because many private APIs are used behind the scenes by public APIs and the security model must allow applications to run them.
- Elizzy 10y agoBecause some of these APIs are useful in an enterprise app setting that aren't distributed via the App Store. Like Disney applications on their turnstile devices at Disney World.
- marcoperaza 10y agoYou aren't supposed to call private APIs in your code, but your app is definitely making private API calls all the time since the libraries provided by the platform are running in-process.
- euyyn 10y agoPreventing it in a technical way is far from easy: If your app calls public API X, which as part of its implementation calls private API Y, your compiler only needs a declaration of Y to output the function call / ObjC message send. Nothing in the language prevents it, and the code is executed natively unlike Java.
- tluyben2 10y agoThey control the software and the hardware though: seems possible to allow a specific region of memory (aka their public API) to call a specific region of memory (private API) and segfault for all the rest that does that?
- 10y ago
- cynix 10y ago> Rollout lets you push code-level changes to native iOS apps, without waiting on the App Store. What did they expect when their entire business model is based on something that's literally the opposite of what the review guideline allows?
- recursive 10y agoUber is still doing kind of ok.
- megablast 10y agoUber isn't going up against one company though. It is going up against 1000s of governments.
- tuananh 10y agoWhat does Uber do?
- recursive 10y agoThey run an illegal taxi service. There's an app for it too.
- EduardoBautista 10y agoIt's legal in many cities.
- madeofpalk 10y agoWhich is disingenuous to say because the guidelines forbid using these methods to make "significant changes to the app" - it doesn't mention modifying the binary.
- Nition 10y agoHeh, "We're in so many apps... it MUST be allowed!"
- cooper12 10y agoTo be honest, I think the fact that they're used by so many big players is the reason that Apple is requiring removal in future updates rather than outright removing for ToS violations.
- craigvn 10y agoI would be cashing out now...!
- Aissen 10y agoIt won't be the first $10m+ company killed by Apple's App Store policy. I hope it will be among the last though.
- intoverflow2 10y agoVery little sympathy for anyone who didn't see this coming, I'm more just shocked they even got it past Apple in the first place. Even if I had the idea and the technical skills to pull such a product off I wouldn't even bother trying for fear it wouldn't even get past the first hurdle.