Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Fallout From Apple's Exclusion of Flash-to-iPhone Export Continues
- Thread starter MacRumors
- Start date
- Sort by reaction score
Ignoring all the childish rants, pro this, pro that, etc, I have a simple question.
Will the ported Flash apps work properly with multitasking, new API's, and system resource management techniques present in iPhone OS4?
If the answer is no, then no one can fault apple here. There's no reason they should cripple multitasking and/or create issues just to abate adobe.
If the answer is yes, and the ported apps will work properly with all the new features, then apple has no excuse for this new action, and is simply being childish and monopolistic.
It all depends on the real reasons, not speculation.
Will the ported Flash apps work properly with multitasking, new API's, and system resource management techniques present in iPhone OS4?
If the answer is no, then no one can fault apple here. There's no reason they should cripple multitasking and/or create issues just to abate adobe.
If the answer is yes, and the ported apps will work properly with all the new features, then apple has no excuse for this new action, and is simply being childish and monopolistic.
It all depends on the real reasons, not speculation.
No, once again this is not about Flash on the web. (I agree with most people that Flash on the web mostly sucks and HTML 5 is the future.)
This is about developers using the Flash TOOL to write compiled native apps. There is no "open standard" for native apps.
let me explain this to you guys since you all don't know what html is which is clear since I see this thread hijack in all the threads talking about the new SDK rules.
HTML is hyper text markup language which is used for creating websites. In HTML you have something called tags like <html> or <head>. HTML5 contains two new tags <canvas> and <video> which is the cause for the whole flash will die debate.
You need to have knowledge of Javascript in order to use the <canvas> tag for games. It essentially places a canvas then Javascript is the paint. That's how the simple "html5" games are made.
Can you make native like apps using HTML5. It is possible but Apple doesn't make it so because you do not have access to all of the features in the SDK. You would need to use Objective-C in order to access things like the users audio.
/end
I really don't care Adobe needs to be dealt with and Apple is in a position to do so!
Apple will have zero problems if Adobe follows the path you have laid out. The days of Apple products being sold to support Adobe software are long gone. There are lots of reasons for people to own Macs these days.
Dave
I really don't care, if Apple is successful in their quest to bury Adobe and flash then the stress will be well worth it. That is a goal I'd personally like to see Apple meet. However due to the wide net they are casting I really think Apple has bigger issues than just Adobe. It likely has a lot to do with managing quality and the app store code base.
No they should manage their company in a respectable way and support their primary customers with quality products. Instead they have infected the Internet with flash and all the disgrace that comes with that.
Apple will have zero problems if Adobe follows the path you have laid out. The days of Apple products being sold to support Adobe software are long gone. There are lots of reasons for people to own Macs these days.
Dave
Oh, I know... Let's put the load on the shoulders of the users instead. Make everyone download an app for manually monitoring and managing tasks and processes on their iPhone. Then make the user get a degree in Geek Gadgetry so he can begin to use his phone effectively.
You're all off topic. All this talk about HTML5 is completely irrelevant. Read the article again. This is about application development... not content delivery. The reason is that the new multi-tasking iPhone OS 4 depends on apps being written in C. Which makes this Adobe guy really look like an a@@. I'd be surprised if he doesn't get fired.
I stand corrected. I assumed that was how apple was scanning. I've tinkered with iPhone development, but have not submitted anything.
Actually this is not true. IF they are building multitasking hooks into the OS that relies on characteristics of their toolchain, including particular objective C/Cocoa or API call constructs then it would make PERFECT sense to not allow apps that use other tools.
Also this is NOT a discussion about a language/compiler, it is an API discussion. An application developed by ANY flash based tool, even when built as a binary, is operating on a virtual operating system BASED ON FLASH RUNTIME, not the iPhone OS. On a device such as the iPhone/iPad there really is not enough extra resources to justify an inbetween layer, specially one that is bloatware.
Good point. You are right. I thought one of those generated C source code as output. It's a grey area since the Agreement says "originally written in c/c++/obj-c".
Maybe Unity and Torque will be "plus one's".
Sweet Jesus, I hope Unity and Torque make it out of this unscathed!
This is what unity says about their platform:
That sounds like the things Apple is trying to put a stop to. I'm hoping Unity can just update their unreleased 3.0 version to make it compliant enough to get approval on the app store.
Wordperfect wasn't Photoshop, After Effects, Illustrator, InDesign etc. etc. Adobe creative software are industry standard and far more important then Mac OS X for those who use them professionally. Apple has shown what they can do with pro software. First they showed promise then some innovation after which there were some great piece of software but then came Apple's consumer iThingy craze and pro needs and development went either down the toilet like it did with Shake (incredible piece of high end software that Apple bought from Nothing Real and then killed it after couple of years) or has slowed down to crawl like Final Cut Studio.
lol I'd like to see that developer agreement hold up in a court of law. Just because someone signs a contract or accepts a license agreement does not mean that that contract will stand up to legal scrutiny. There are a number of things that can make a contract invalid.
As for what Apple is doing, as long as the end code is clean and in a format that meets their requirements, it is none of their business what software the product was developed in. It would be like Walmart telling its suppliers that it won't accept products from a certain factory because the machines in that factory were made by Target. Apple is very clearly taking a stab at Adobe and other companies who are developing programs to help people make multi-platform mobile development tools. They don't want multi-platform apps because they aren't exclusive. It's anti-competitive business practice. Microsoft has gotten sued many times for far less than this.
"Apple needs full access to a properly-compiled app to do the pull off the tricks they are with this new OS"
says a forum user with no understanding of compiled code or the function of an OS.
says a forum user with no understanding of compiled code or the function of an OS.
This is a matter of principle. Short analogy: Most people would probably be happy if the state they live in gave them a free BMW. However, it would still be wrong, because it would drive other car manufacturers out of business.
Nobody forces Apple to endorse or support jailbreaking, Flash, etc. But Apple should not actively try to prevent jailbreaking with patching every new version of the iPhone OS or making a new dev agreement to harm companies like Adobe.
Unfortunately, Apple no longer is the hammer-throwing company like they imagined themselves in their 1984 commercial. Since the introduction of the iPod and especially the iPhone, they've turned into what they earlier fought against.
So you mean you want to write a computer program but can't be bothered to learn a computing language?! And what's this bit about 'Apple do something right for the user for once?' I personally think they did great with their app store, not to mention the brilliant hardware.
Geez, I know some students are muppets, but really.....
And the answer obviously is YES. The AppleInsider's theory holds no water whatsoever. If Apple was concerned about support for new API, it should have set this as a requirement: applications have to support specific APIs, it's that simple. What does it have to do with which language was used as the original source? Nothing.
As a developer I have learned a lot of languages. I just do not want Apple (or anybody else to this matter) dictating me how to develop my applications.
This discussion has devolved into an argument over flash when this isn't even about flash.
This is not about Apple blocking flash!!! This is about Apple blocking Adobe's flash exporter.
A developer can write an app in flash and then the exporter will export that into native iPhone format. The resulting app will contain NO FLASH. This is what Apple is prohibiting.
Just thought I'd point that out for those who still don't get it...
I literally know nothing about software development or any coding languages and even I can understand this.
This is not about Apple blocking flash!!! This is about Apple blocking Adobe's flash exporter.
A developer can write an app in flash and then the exporter will export that into native iPhone format. The resulting app will contain NO FLASH. This is what Apple is prohibiting.
Just thought I'd point that out for those who still don't get it...
I literally know nothing about software development or any coding languages and even I can understand this.
You want to check out flash's memory performance?
Go to Facebook and start playing Farmville or CafeWorld and monitor your computer's memory performance. These games leak like sieves and can bring your machine to a near standstill.
Imagine that happening to your mobile phone...
Go to Facebook and start playing Farmville or CafeWorld and monitor your computer's memory performance. These games leak like sieves and can bring your machine to a near standstill.
Imagine that happening to your mobile phone...
I am in the same situation as him. I want to learn objective-c but I have no time because I am a student but I do know AS.By doing this they will lose a lot of potential and current devs
Actually this is exactly the reason Flash NEEDS to go. No single company should be in a position to dictate the experience of the web.
You may recall Adobe's statements on the JooJoo debacle: According to the powers that be at Adobe, JooJoo should have had a 'direct relationship' if they wanted decent performance.
What is completely ridiculous is that there is absolutely no change of intent of the updated SDK wording.
I challenge anyone to check the wording of the old SDK and the new SDK and explain where how they are different in practice?
Translation layers/Virtual machines/third party frameworks were always forbidden and pretty much every developer knows this.
Things like Java/JVM are never going to happen. Where is all the screaming about Java?? Well it doesn't have a bunch company PR wonks with their panties in a bunch ranting on the net.
There was never any chance that AIR (Flash + runtime layer) was going to get approved by Apple, anymore than Java + JVM are.
The "outrage" blog could have been penned and waiting for some trigger to publish...
Apple is well within it's rights to demand native apps for it's platform, and such a decision will lead to better apps from dedicated developers, rather than yet another cross target output check-box from Flash "developers".
It will make iPhone apps look even better as the Android store will fill up with more Flash AIR crapware.
I challenge anyone to check the wording of the old SDK and the new SDK and explain where how they are different in practice?
Translation layers/Virtual machines/third party frameworks were always forbidden and pretty much every developer knows this.
Things like Java/JVM are never going to happen. Where is all the screaming about Java?? Well it doesn't have a bunch company PR wonks with their panties in a bunch ranting on the net.
There was never any chance that AIR (Flash + runtime layer) was going to get approved by Apple, anymore than Java + JVM are.
The "outrage" blog could have been penned and waiting for some trigger to publish...
Apple is well within it's rights to demand native apps for it's platform, and such a decision will lead to better apps from dedicated developers, rather than yet another cross target output check-box from Flash "developers".
It will make iPhone apps look even better as the Android store will fill up with more Flash AIR crapware.