| ▲ | endemic 5 hours ago | |
> we can’t simply update the Firefox app I'm confused about this part. Is there some sort of code signing requirement that wouldn't be available to the "original" Firefox iOS app? | ||
| ▲ | george_perez 4 hours ago | parent | next [-] | |
They just mean they can't update their existing app with the non-WebKit engine. They have to make a separate SKU, with the non-WebKit engine, and publish that on the App Store. The sentence after that explains what they mean. They would have to migrate users from the Firefox WebKit SKU to the Firefox Gecko SKU in the EU and migrate all the data from one SKU to the other, essentially a full browser migration. | ||
| ▲ | nguyenkien 4 hours ago | parent | prev | next [-] | |
Apple require app with non-WebKit engine target Japan OR EU only. So they can't just update exists app. | ||
| ▲ | Hamuko 5 hours ago | parent | prev | next [-] | |
Isn't that because alternative browser engines are region-locked, so you'd need to have a WebKit version and a non-WebKit version for different regions? | ||
| ▲ | fl0id 4 hours ago | parent | prev [-] | |
every update goes through an app review. how do you think that's going to go if you don't adhere to this? | ||