Re:Why We Are No Longer Developing for the iPad
by eridius on Thursday April 16, 2015 @05:45PM
(#9390924)
So am I. I'm also interested to know why the engine can't be fixed, rather than being forced to replace it with an all-new engine.
[ Parent
| on HN ]
Re:Why We Are No Longer Developing for the iPad
by Someone on Thursday April 16, 2015 @05:53PM
(#9390954)
It might be technically possible or even trivial to fix the engine, but impossible for other reasons.
They are talking of licensing a new engine. If they licensed the current one, too, it might just be a matter of a vendor that went out of business or killed the product.
Re:Why We Are No Longer Developing for the iPad
by teacup50 on Thursday April 16, 2015 @09:05PM
(#9391729)
Not the engine author, but from our app experience:
Tracking Apple's breakage (in minor releases, even) and fixing our code -- code that was written to the defined API -- is a cost that is rising precipitously as Apple's quality and stability keeps going down.
If you have revenue from other platforms, it can make sense to just say "f it" and drop the platform. The AppStore is a shitty retail pipeline; 30% is a crazy commission for digital software distribution, the single-retailer-monopoly + appstore design is driving prices to unsustainable levels, etc.