3 ms·

Fun fact nobody remembers: back in the day Adobe built a feature where you could build flash source to an iphone app - you hit "publish" and an .ipa came out. I

Fun fact nobody remembers: back in the day Adobe built a feature where you could build flash source to an iphone app - you hit "publish" and an .ipa came out. It worked fine, people made apps, they got accepted to the app store, users used them, etc. Then a day or so before that feature left beta, apple added a vague new clause to their app store agreement, which made no sense on paper but whose obvious purpose was to disallow flash apps. They then unpublished all the existing flash apps for violating that clause. Adobe quietly cancelled the app publish feature, and a few months later apple quietly removed the clause.

ihuman 2y ago
What was the clause?
- deleted 2y ago
  [deleted]
- fenomas 2y ago
  It was something like that the app must have been "originally written" in certain approved programming languages. It basically targeted cross-compilation, but it was written so vaguely that on paper it appeared to even disallow native iOS apps if they started out as a port from some other language. There was briefly a kerfuffle about it, as people using other cross-compilation tools (xamarin? etc) worried their apps would get removed as well. But IIRC apple never actually enforced the clause, other than to remove existing flash-based apps and reject new ones.
  - Marazan 2y ago
    But it did cause vendors of cross-compilers to lay of dozens of staff as the clause killed their business (Source: I work with someone who was laid off because of the clause)
joshtynjala 2y ago
I don’t recall Apple unpublishing my AIR apps. One of mine was among the first secretly submitted before Adobe revealed the feature publicly. However, I definitely remember after Apple added the new clause, when I needed to submit updates, those were stuck in approval limbo for many, many months. Then, suddenly, they all got approved in a flurry and there was never an issue again. Adobe AIR is actually still available today (now maintained by Harman through an agreement with Adobe), and it can still compile native iOS apps that can be submitted to the App Store. This feature was never removed, and is still maintained to be compatible with new iPhones.

ihuman 2y ago

What was the clause?

deleted 2y ago
[deleted]
fenomas 2y ago
It was something like that the app must have been "originally written" in certain approved programming languages. It basically targeted cross-compilation, but it was written so vaguely that on paper it appeared to even disallow native iOS apps if they started out as a port from some other language. There was briefly a kerfuffle about it, as people using other cross-compilation tools (xamarin? etc) worried their apps would get removed as well. But IIRC apple never actually enforced the clause, other than to remove existing flash-based apps and reject new ones.
- Marazan 2y ago
  But it did cause vendors of cross-compilers to lay of dozens of staff as the clause killed their business (Source: I work with someone who was laid off because of the clause)

joshtynjala 2y ago

I don’t recall Apple unpublishing my AIR apps. One of mine was among the first secretly submitted before Adobe revealed the feature publicly. However, I definitely remember after Apple added the new clause, when I needed to submit updates, those were stuck in approval limbo for many, many months. Then, suddenly, they all got approved in a flurry and there was never an issue again. Adobe AIR is actually still available today (now maintained by Harman through an agreement with Adobe), and it can still compile native iOS apps that can be submitted to the App Store. This feature was never removed, and is still maintained to be compatible with new iPhones.