3 ms·

I'm sure no one understands the technical challenges better than Adobe's engineers. The problem is that the company never admitted these challenges to their de

I'm sure no one understands the technical challenges better than Adobe's engineers. The problem is that the company never admitted these challenges to their developers and customers (until now). Instead, they continually explained the problem as merely a political fight with Apple. Your website is no good on mobile? Don't blame us, blame Apple's lust for control. At worst, they flat out lied to their developers and customers. At best, they are merely incompetent. Either way, if I were heavily invested in any Adobe technology I would seriously question how I could continue to trust that company.

idspispopd 15y ago
Amanita Design, creators of the indy award winning flash-based game "Machinarium", recently released this title to iPad. Machinarium is a basic point and click puzzle adventure. If written in native code this would have no issue running on even the first iPhone (of which there are plenty of similarly detailed games.) However due to using the Adobe iOS tools(air etc.) The performance is dismal on iPad 2. iPad 1 owners have mostly sought refunds, and left bad reviews - forcing the developer to make the game "iPad 2 only" despite being a battery killing lap heater. (This already puts it in the apple cross-hairs as it's available to download to iPad 1 users.) Discontinuing flash player is only half of Adobe's problem, the bad code is still being manufactured into processor-heavy apps which sap battery life and demand far-higher specs than what would normally be required if writing in native code, as noted in the example above. The crux of the problem is that it's not a small amount of additional processing overhead, these basic apps are churning through battery via excessive cpu time. These tools from Adobe are allow developers to port their flash games to the app store, and instead of increasing their revenue, it's creating problems and damaging their image/fan base.
- ntoshev 15y ago
  I'm not sure Machinarium problems stem from the Adobe toolchain. The developer says it's because they hit RAM limit with iPad 1 and load resources statically: "The memory limitations of iPad 1 (which are somewhere around 115 MB RAM per app) are just quite challenging. You have to have it running around 80-90 to keep it stable and the app has tons of timeline animations, the sources are 1 GB, all compiled into one single SWF file + some assets. The app was originally made for PC and upgraded for tablet devices. When you start creating tablet apps from scratch it's a whole different story. The game is now made with 'no compromises' compared to the desktop version and that keeps it unique." http://www.tuaw.com/2011/09/12/daily-ipad-app-machinarium/ http://www.tuaw.com/2011/09/12/daily-ipad-app-machinarium/

idspispopd 15y ago

Amanita Design, creators of the indy award winning flash-based game "Machinarium", recently released this title to iPad. Machinarium is a basic point and click puzzle adventure. If written in native code this would have no issue running on even the first iPhone (of which there are plenty of similarly detailed games.) However due to using the Adobe iOS tools(air etc.) The performance is dismal on iPad 2. iPad 1 owners have mostly sought refunds, and left bad reviews - forcing the developer to make the game "iPad 2 only" despite being a battery killing lap heater. (This already puts it in the apple cross-hairs as it's available to download to iPad 1 users.) Discontinuing flash player is only half of Adobe's problem, the bad code is still being manufactured into processor-heavy apps which sap battery life and demand far-higher specs than what would normally be required if writing in native code, as noted in the example above. The crux of the problem is that it's not a small amount of additional processing overhead, these basic apps are churning through battery via excessive cpu time. These tools from Adobe are allow developers to port their flash games to the app store, and instead of increasing their revenue, it's creating problems and damaging their image/fan base.

ntoshev 15y ago
I'm not sure Machinarium problems stem from the Adobe toolchain. The developer says it's because they hit RAM limit with iPad 1 and load resources statically: "The memory limitations of iPad 1 (which are somewhere around 115 MB RAM per app) are just quite challenging. You have to have it running around 80-90 to keep it stable and the app has tons of timeline animations, the sources are 1 GB, all compiled into one single SWF file + some assets. The app was originally made for PC and upgraded for tablet devices. When you start creating tablet apps from scratch it's a whole different story. The game is now made with 'no compromises' compared to the desktop version and that keeps it unique." http://www.tuaw.com/2011/09/12/daily-ipad-app-machinarium/ http://www.tuaw.com/2011/09/12/daily-ipad-app-machinarium/