Apple Relaxes iOS Development Tool Restrictions
An anonymous reader writes "Earlier this year Apple caused major upset among developers by updating the iPhone developer program license with clause 3.3.1. It basically stopped the use of cross-platform compilers, meaning Adobe Flash could not be used to develop an app for the App Store. The move also put into doubt which other development platforms could be used and generally caused a lot of confusion. Apple has just significantly relaxed that policy and allowed for the use of development tools, as long as 'the resulting apps do not download any code.'"
There are still interesting problems in not allowing to download or update any code. With the rise of jailbreaking iPhones and them running unsigned and modified applications (cracked and/or otherwise), there is no way for an anticheat system to update itself. All anticheat systems like Valve's VAC, PunkBuster and Blizzard's Warden rely on downloading updated code from the internet.
What this means for online iPhone games is that when someone releases a hack for the jailbroken iPhones, their users can completely ruin the games and legit players cannot do anything. And since Apple is a control freak, they check every update to your application slowly and ineffectely. All while the hacking is rampant and ruins everyones game.
There certainly are need for updating code and Apple needs to remove that clause too. We don't want walled gardens controlled by mega corporations, we want systems we can use the way we want.
This would have been the first app had it not been for the stupid restrictions.
It's refreshing to see Apple wrong so many times in a row. Watching them backpedal is amusing.
So...when will they be approving Google Voice?
Absolute power corrupts absolutely. indymedia
Does that count as downloading?
I am looking at this in the context of scriptability.
More importantly, developers will no longer have to second guess the reasons why apps may or may not be accepted. From the statement:
"In addition, for the first time we are publishing the App Store Review Guidelines to help developers understand how we review submitted apps. We hope it will make us more transparent and help our developers create even more successful apps for the App Store."
Browsers download and run code (javaScript).
What about them?
Its good to see big companies backpedal and fix their mistakes, even more if the company is Apple/Ms/Google
Don't get me wrong, I think it made sense for *them* to ban things like Adobe CS5, but I don't think it was good for everyone involved (especially users and developers), and its great to see them do that, for whatever reason it must be.
Let's clarify, since the description isn't that great. Apple will now allow Adobe's Flash to export in iPhone app format
Also, Apple released their App Store Review Guidelines (PDF). Worth a read.
This was all about Unity, which basically does exactly what Adobe's Flash packaging tool did for the most part. The Unity game tools have been used to develop some fairly popular iPhone games, and Apple knew it couldn't continue to authorise Unity based apps whilst denying apps created with Adobe's tools without falling foul of competition laws. Similarly, by kicking Unity off too they'd be throwing away from of the iPhone's most popular games.
So the question now is, does this mean if Adobe tries to release it's tools again that Apple is going to let it, or are they now going to try and find another excuse to deny Adobe access to the platform?
Apple stood to lose far more if it continued to stand by this policy, and if it stood by the policy whilst letting some apps through it also stood to face the DoJ, so it had to decide one way or the other.
This is the actual statement by Apple.
Also, I've read some rumors about the next iLife '11 having a new program for creating iOS apps in a similar way to the Android's AppInventor. This new statement seems a like a pointer in that direction, otherwise they would have a hard time arguing about antitrust issues on the App Store...
exp(i*pi)+1=0
I wonder if this means that I can develop using Eclipse CDT and an iPod Touch, rather than having to buy a Mac.
You can still download code if you use the tools provided by Apple.
The download limit is if you use outside tools.
Oracle wants Java on the iPhone. Oracle sues Google over Java patents. Apple now lets Java on the iPhone.
Google Voice is already an iOS web app. Remember, GV is not VOIP (and there are in fact plenty of VOIP apps for iOS).
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Does this mean that I can use C# to generate a Silverlight app that will run on Windows, Windows Mobile, Linux, Android and iPhone?
Can I write in Java an app that will run on every desktop and mobile?
--
make install -not war
there is no way for an anticheat system to update itself.
What's to prevent the game maker from simply issuing a software update, and having software issue challenges to each other related to versions before accepting games?
Online cheating is not as great a problem as with the PC's or consoles.
It only takes a few seconds to update a new version on the device.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Hopefully that means you can write apps in Qt and hopefully they will be cross-platform with Android so developers don't have an excuse to marginalize one platform.
Most of the time these worries are about anti virus instead. There the updates also contain exe updates.
But the same update mechanism used for an normal application can apply to a any application. Let it bet antivirus, anti-cheat or a simple game. If you want to update it you do it via a the app-store, and don't come up with a own update system. If that is not good enough, that should be updated, not implement it on yourself.
The fact that windows does not have a central update system and every app has to do their own update mechanism is a bad thing of windows. And it is a sad fact that user have come accustomed to that.
It's refreshing to see Apple wrong so many times in a row. Watching them backpedal is amusing.
What's refreshing to see is a company that actually admits it was wrong, how often does that happen?
They were wrong to lock down the development tools so much (I said so at the time and thought they would relax things eventually simply because they had to), they realized the mistake, and have stepped back after developer pressure. That's why I prefer to work with iOS development, because they do listen to developers and take into account feedback or concerns, and really change fundamental policy instead of continuing said policy just because it exists as so many other companies would do...
All companies (and people) make mistakes. It's how (or if!) mistakes are corrected that is the thing to measure by.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
What I would like to see apple do is to add performance to it's application review process. Say for instance you app does not boot to a stable runnable state in 10 seconds it gets disapproved. Same goes for memory usage and and processor load. That would solve the whole "user experience" goal that they claim to have. Of course it would keep most of the interpreted apps, flash, java etc off of the phone but I have no problem with that. On one hand I would like to have to option to use interpreted languages on the device on the other hand I know that for performance reasons it is not the way to go.
Got Code?
But most people wouldn't have blamed Flash - especially if there wasn't an easy example of a non-flash version to point to. They'd have blamed the iPhone. Most people, even most iPhone users, don't read /. or related sites - that's one of the reasons that the iPhone has been a smashing commercial success, you don't need to be a geek to use it (N70, I'm looking at you here). Keeping Flash off the platform was exactly the right business decision to make.
Even if Adobe would release a version that wasn't a battery killing unstable one - which would be a great start - the usability experience isn't close to being there for multitouch devices. And the iPhone is all about user experience.
You're special forces then? That's great! I just love your olympics!
This was all about Unity, which basically does exactly what Adobe's Flash packaging tool did for the most part.
Actually I thought Unity was more intermediate, producing an XCode project you would compile - the flash tool produced a binary directly.
Apple knew it couldn't continue to authorise Unity based apps whilst denying apps created with Adobe's tools without falling foul of competition laws
Actually it could do that forever because there are no such laws. Anti-Trust doesn't enter into the picture in any way.
The real reason the relaxed the restrictions is, I think twofold:
1) Developer outcry - Apple does respect and listen to developers, and they were having too many people come up with too many perfectly valid edge cases (like using Mono or Scheme for development). Apple had actually pulled back on this restriction a few months earlier letting people submit things developed using alternative languages on a case by case basis, that was probably a lot of work to review.
2) Control of app quality. This I think is key - what Apple is really worried about with Flash developed apps coming out is that a ton a crappy stuff would flood the store and the review process. So what has changed? The fact that they have a stated review policy now, which says in part "we will not allow a ton of crappy small applications that do nothing". The whole limitation made no sense before because Apple benefits from having quality applications on the platform, so now its more clear that wider spectrum of development tools will not be allowed to destroy the level of quality the application pool enjoys, so someone CAN use Flash to compile an iPhone binary but they had better be producing something good. A formal app store review policy allows Apple to be more relaxed in other regards, because it keeps control over the final quality of applications.
Whats really odd is that it took this long to come up with any kind of review policy document!
"There is more worth loving than we have strength to love." - Brian Jay Stanley
It really hasn't been a failure in my experience, and I wonder why that meme keeps going around.
Funny. Javascript is code. Browsers that download and run Javascript should be banned.
Apple seem terribly random and unpredictable. It would be senseless for any developer to begin work on a project that has become permitted by this clause, because tomorrow the terms could change again.
I'm an Android developer, releasing my first game in the next 4-6 weeks. Then I need to consider whether or not to produce an iPhone version. The decision will only slightly be based on forecasted sales, market share of competing products, and demand for my product. For the most part I will need to decide if I can afford to invest the time developing for a platform that may, at any point, "ban" my product for some obscure reason. (For example, all of my graphics are produced in 3D Studio and rendered as 2D sprites. Suppose Apple takes a dislike to Autodesk...?)
Sure, so how does Skype get through.
Because it doesn't duplicte existing functionality. There is no built in VOIP client, and it uses the Apple contacts. GV linked back to Google contacts...
In fact, how do most apps get around points 2.11-2.13?
2.11 Apps that duplicate apps already in the App Store may be rejected, particularly if there are many of them
At this point that might be a problem for some applications but there's always a new idea without many apps in the store.
2.12 Apps that are not very useful or do not provide any lasting entertainment value may be rejected
I think you might just be able to work around that by writing an app that is useful or entertaining.
2.13 Apps that are primarily marketing materials or advertisements will be rejected
To me that simply repeats point 2.12 since an application that is primarily marketing is also not useful (though I suppose it could be entertaining, and thus possibly accepted).
I would say the vast majority of apps in the store fall under these points.
Like what? Very few of the applications I have seen fall under these points, except possibly for point 2.11 - but that's the thing, the avoidance of replication is more a point going forward than it has been (though Apple has been starting to reject some applications in crowded categories).
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Its the Apple IIe all over again. The company got cocky, started abusing their market domination with laziness, and now they are in deep sh*t.
After wrestling with itunes and the restrictive nature of the iOS, users are getting more advanced and realizing that the iPhone isn't the only answer out there. Because Apple alienated the dev community, the nerds are telling everyone to go Android. If I had Apple stock, I would sell and do it quickly.
Flash is a failure on Android? Since when?
It works great on my phone.
Security is mostly a superstition... Avoiding danger is no safer in the long run than outright exposure. - Helen Keller
as long as "the resulting apps do not download any code".
What's considered code? Anything that you interpret/execute as commands that conform to a specific grammar/language? So is HTML code now? How can one define "code" that HTML, for example, would be excluded?
I agree with you 100% as far as Safari is concerned and I'm glad that I don't need to hack my iPhone just to block flash.
However, as far as apps with a flash runtime are concerned, people will just see them as slow and broken and blame the apps. I don't think people would even use them long enough for it to interfere with the overall perception of battery life.
Doesn't Apple have to release an SDK to the public for this to mean anything??
I have seen several people make this mistake - this has nothing at all to do with Flash-the-web-content-platform discussion, as in this case we are not seeing Flash hosted by the web browser at all. No, this is about Flash as a generalised development language for the iOS platform, running code natively and replacing ObjC in the development process - it allows current Flash developers to target their skills at more than just the web.
Flash-the-web-content-platform can wither and die while this use of Flash-the-language can thrive completely independently.
I think this line from the guidelines is pretty funny:
"If your app is rejected, we have a Review Board that you can appeal to. If you run to the press and trash us, it never helps."
So basically, don't snitch.
To the contrary, however, in the past, it seems like running to the press and trashing them can really help get your app approved.
See, e.g. http://apple.slashdot.org/story/10/04/16/2327219/Bad-PR-Forces-Apple-To-Reconsider-Banning-Mark-Fiores-App
Is this for real? Wouldn't it be better to prefer to work with another platform that does not have to receive negative feedback in the first place? All companies and people make mistakes, but I don't recall any development platform that has made missteps this bad and drawn this much negative press in recent memory.
Also, you say, "That's why I prefer to work with iOS development, because they do listen to developers and take into account feedback or concerns, and really change fundamental policy instead of continuing said policy just because it exists as so many other companies would do..." Has there been any fundamental policy shift before today? If not, what were you saying prior to today on why you prefer to work with iOS development?
Flash on Android is what now? It works fine for me (well, as fine as Flash can, which is to say slow and buggy but no different to on my desktop).
After the disaster that has been flash on Andoid so far, perhaps this is just Apples way of saying "see we told you". I expect a plethora of sub-par apps flooding the app store soon, in the end this will probably help HTML5's cause much more than Adobe.
Personally, I would blame Apple even more when I couldn't visit a website at all because the site was designed around Flash. Personally, I just got Flash on my Droid about a week ago and I've already hit at least a dozen sites that wouldn't have been viewable before and it was in situations where I didn't have easy access to a PC and the information was something I needed right away. Everyone here seems to want to blame the site owners because Flash is a PITA (and it is, don't get me wrong), but it sure is handy to be able to actually visit every site on the web even if it isn't designed for mobile viewing.
Flash on Android is what now? It works fine for me (well, as fine as Flash can, which is to say slow and buggy but no different to on my desktop).
That about sums up one school of thought in the PC industry. I think I'll have to close my web browser for a while and take a walk outside.
"Apps that browse the web must use the iOS WebKit framework and WebKit Javascript." Looks like there's still no hope for third-party browsers!
But Atomic Web browser is great. It uses Webkit, and Webkit Javascript, so it renders no doubt exactly like Safari. But, it provides a much nicer UI, for Tabs, for Search, and for Fullscreen. I almost never use Safari on my iPhone since I found Atomic.
Might be something to do with apple fanboys that don't have a particularly close relationship with reality... you can hardly blame them.
What a lot of the articles pointing this out don't mention is that the rules governing advertisers and what information they can get from the user without their knowledge/permission also changed. Ars points out that this change may make it easier for large third-party advertisers (e.g. AdMob) to get data from their users. I'm not going to argue whether the other changes to the agreement are good or not (I'm a little worried that allowing interpreted code, particularly flash, will lower the overall quality of apps available in the store). But some of the changes to the ability of third-party advertisers to get information on their users could be a serious problem.
Science will save us. The question is, will it destroy us first?
Or can only Safari download JavaScript?
“Common sense is not so common.” — Voltaire
Or do the EEE - Embrace, Extend, Extinguish.
Embrace - there are many open-source Flash players out there. All Apple has to do is hire the devs and bring them inhouse to make it work great on iOS. The benefit here is no plugins or other crap to download - iOS just runs most Flash apps.
Extend - new iOS features are put into the Flash runtime. Developers are encouraged to use those features for their code, and an Apple version of the tools (because Adobe's tools won't do it) and runtimes will be released as browser plugins and everything. Imagine opening up a webpage and seeing "You need to install the Apple Flash player to continue", for example. (E.g., location services, accellerometer, gyro, multi-touch - all these things I don't think are in Flash, yet could be added by Apple).
Extinguish - Adobe's a slow moving company. A mobile flash player has been available since Flash 7 many years ago, and yet it still runs like crap on anything but a PC. Mobile flash seems ot have hit it big this year, because it's taken Adobe that long to actually have it ready, even though you could get Flash on your N800/N810 tablets, Archos had mobile flash, etc. The open-source version could actually beocme the Flash player of the future, after Apple pretty much wrestles it away from Adobe to make it Apple's platform. And it'll be Adobe playing catch up on their platform.
And Android and WebOS devices will be onboard, because well, it's open-source and you can be sure developers would want the same features as well. Hell, imagine Apple selling apps for Android this way (Apple can do it because they can sell anywhere they have an iTunes store, while the Android Marketplace has limited the countries which can pay for paid apps).
Flight of fancy, I suppose. But one of Apple's main objections ot Flash was the dependence on a very unreliable third party that moves very slowly. By wrestling control of Flash from Adobe, they not only control it, but they could go and try to make it run well.
it replaces the outbound phone number, the mailbox number, and it uses the native interface(!)
Most of the things you list are not possible for an iPhone application - it was already more limited than the Android version because an application is not allowed to basically take over the system to that extent.
You are decrying the lack of an application you could not have on the iPhone. The web app is not that far off what the native app could do.
As for "not being a smartphone user", I'm a mobile application developer (primarily iOS at the moment).
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Wouldn't it be better to prefer to work with another platform that does not have to receive negative feedback in the first place?
Sure it would. And I'd love to ride a Unicorn through the sky!
Too bad I can't do either. All platforms have some negative feedback from the user community. The question is, do the curators of the platform you are developing to listen to you?
I'm not even saying Google does not, I think they do as well. But Apple is very good about taking in suggestions for enhancements and eventually coming out with really good API's around them, or as in this case responding to something Developers saw as pointless and removing it (and in reality they had backed down on it months ago with a slight revision to the alternate platform clause).
It's not like Google is perfect either after all, like only allowing Skype to be used with Verizon, or allowing really crapping phone company specific UI to be added to Android.
Has there been any fundamental policy shift before today?
Yes, for example they had a no screen-scriping rule in place for camera use (because that was the only way to read the camera data realtime was a private API call) and they specifically allowed use of that private call so that basically every barcode scanner and AR app could function.
They've also backed of policy choices like not allowing free apps to change to paid apps (or something along those lines, I forget the exact details since I wasn't affected). Or they have also changed policy around in-app purchases to change some restrictions.
Basically there are a lot of examples of where Apple came out with some initial policy that had issues, and they fixed it is response to developer feedback.
If not, what were you saying prior to today on why you prefer to work with iOS development?
I'm saying it because I have found it to be a consistent pattern over the past few years. I was a Java developer for many years, I could do Android development just as easily - but I like more what Apple is doing around the iOS platform, and currently I see a ton more potential (and it's much easier to make a living at it).
"There is more worth loving than we have strength to love." - Brian Jay Stanley
A crappy app is a crappy app, regardless of what's been programmed in and it still has to be reviewed and approved.
If someone creates a flash app that doesn't kill the battery and provides a pleasant experience, it should be allowed.
Conversely, a bad app written in Objective-C should (and will be) rejected.
The problem is that Apple can't trust a third party development environment to take over too much of the app share. In the past stuff like that has wrecked OSes as a vital update breaks the third party APIs that are used in bestseller apps. Apple wants to be able to release iOS 5 and 6 without worrying if they break Flash's internal APIs
Apple is not microsoft and they won't do EEE on that basis alone.
Second, Apple is not going to favor Flash over Objective-C tools, which they would need to carry out EEE.
Third, promoting Flash will mean promoting subpar apps since they will not have the functionality or speed of Objective-C. Apple is not going to shoot themselves in the foot in order to extinguish a foe.
Fourth, wouldn't Adobe sue them for trying? Look at the current lawsuit between Google and Oracle over Java.
There are mistakes, and then there is an attitude that the whole world should bow to their wishes.
That would suck if it were the case. But I've not found that to be the case at all. I would certainly not develop for a platform that was true of, as I have a choice of what I can do.
Apple treats its customers as though it's only because of Apple's great kindness that those customers get to use Apple products. They treat their developers like a necessary evil, and it's only by Apple's grace and mercy that developers are permitted to write code for Apple products.
As a developer I don't get that vibe at all. Apple realizes the success they have enjoyed COMES from the development community, and offers a ton of stuff in support of developers. As I said they listen to feedback, and have done things like making all WWDC (Apple developer conference) videos free for every registered iPhone developer.
As a user of Apple products I don't get that vibe either. It's not like consumers have no choice, but a lot of them have CHOSEN to use Apple products because they like how they work, and treat the user with more respect than other platforms.
That's how you get things like the ridiculous hoops needed to write apps for the App store,
I never saw how that point was accurate either. There really are no "hoops" at all in application development, and honestly how can you claim there are with 250k approved apps? The restrictions have always been around a limited set of some categories of applications, and outside of that space development is really easy. People like you have been claiming the restrictions are absurd since day one, but from the standpoint of a developer it's been pretty easy all along.
The only reason Apple is backpedaling now is because they pushed it too far and received some backlash.
Isn't that the reason most people back down from a bad position? People tell them they are wrong, and eventually they see the light... but often not, especially with companies. That's my point, that to me it seems rare that customer complaints change anything about how a company works.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Probably because of the many youtube videos showing awful flash performance on mobile phones.
Looks like the app is using the iPhone contacts to me... (or at least includes them in addition to supporting toktumi contacts).
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Apple also might not have the resources to support another language. Objective-C is essentially Apple's (Well, technically NeXT's) baby, so if Apple decides to make a language change, it is their decision, and theirs alone. If Apple wanted to start using BEGIN and END statements a la Pascal in the next objective-c release, they can and nobody can tell them otherwise.
By absorbing Flash and making it a supported language, Apple would either have to walk lock-step behind Adobe with every change they do to ActionScript, or fork and have a version that "mostly" works, forcing developers to have to make sure they don't do something that isn't supported, or may cause a crash or incompatibilities later on.
Instead, what would seriously sell would be the ability to take Java bytecode made to run in the Dalvik VM for Android, and convert that into Objective-C source code. Of course, this is a lot harder than it sounds, but if someone is able to make a tool like this where software companies can have essentially one code base for Android and iOS, it would rake in the cash big time.
That explains all the fart applications.
As Apple even said in its app store submission guidelines, they have "enough" fart apps (one could argue zero is the right number). So the thing about Flash compilation is that it comes into a world where there are already a ton of these small semi-pointless applications, yet it makes it all too easy to make more of them for even novice developers... so Apple is saying "sure you can use Flash, but don't expect to be able to do dirt-simple applications going forward because they have been done".
"There is more worth loving than we have strength to love." - Brian Jay Stanley
I'm trying in vain to find where they admitted they were wrong. All I see is "we listened to our developers,"
That and changing the clause so dramatically is saying they were wrong.
which is nothing more than a nice way of saying "we think this is beginning to hurt our bottom line"
That's your interpretation, but it rests on the restrictions "affecting the bottom line". But did it?
I would assert it did not. During the period the clause was in place there was no slowing of app store submissions, nor were there problems getting a ton of iPad specific applications submitted. In fact in no way does disallowing submissions created via alternate toolchains hinder Apple's bottom line, while allowing them poses somewhat of a danger as you noted about intermediate layers and lots of apps potentially failing at once. But it seems Apple though developer demand was sufficient to allow this in the general case, very probably driven by the needs of game developers who rely heavily on these intermediate platforms.
But trying to frame it as some sort of benevolence instead of ANOTHER self-serving action
You'd have to make more of a case for why it was actually hurting Apple in any way other than developer goodwill (which is important but even there was a smallish segment of the developer base).
Because I see more downsides than positive aspects of this change for Apple, to me it appears more altruistic than self-serving (and possibly done only to increase developer goodwill). Apple did not have to make this change as they would have kept having quite a lot of applications flowing through the pipeline as it was.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
It uses them alongside their own contact list. A given contact can be in either or both lists. If that were the distinguishing characteristic, it seems like that would be easy enough to handle in a Google Voice app.
Dewey, what part of this looks like authorities should be involved?
It uses them alongside their own contact list. A given contact can be in either or both lists. If that were the distinguishing characteristic, it seems like that would be easy enough to handle in a Google Voice app.
Apple said they'd be willing to work with Google to make the changes that would get the app accepted But Google instead opted for the web app path... in part because Google also has the desire to have you use Google for contacts, not your local phone. So they would rather have you using an app that doesn't present local contacts at all.
There are two powerful forces of will at work in that story.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
One guy recently posted an article and video showing how Flash video wasnt loading properly on one site and then proclaimed Flash a miserable failure, followed by the blind support of uber-nerds blinded by pathetic Flash hate.
Too little...too late. Smart developers abandoned ship last year.
User experience is definitely paramount to iPhone success but I think the real issue is about app store revenue.
This post on the SDL mailing list thinks dynamic linking is now allowed opening the door for LGPL and even GPL in commercial projects on the devices. http://forums.libsdl.org/viewtopic.php?t=6549
"While the Windows and Xbox 360 versions of The Orange Box were developed and published by Valve, the development of the PlayStation 3 port was outsourced to Electronic Arts."
Try again...
http://en.wikipedia.org/wiki/Orange_Box#PlayStation_3_version
Maxim: People cannot follow directions.
Increases in truth directly with the length of time spent explaining them
So where is Apple's helpful feedback saying "Simply include the iPhone contacts in your list and we'll approve your app?"
If there was a problem, any real problem, they'd have told Google what it was so that they could fix the software or work around it.
The problem is that they'll walk all over any developer they feel is getting too close to them, or a feature Jobs feels proprietary about. There's no objective user or developer benefit behind any of their decisions. Any time there's innovation that threatens Apple's stranglehold on something they'll do their best to strangle it. If fortune smiles your app sails through, if not it's just lost for no stated reason and nothing but tons of bad PR will ever sway them.
The problem is that Google Voice shows how the specific phone/device doesn't matter any more than the specific PC you do a search from does, the network can route to you. Those fancy iPhone apps won't follow you? Ohhh, burn. And so Apple can't allow it.
But...anyone on this website will know that you are an apple fanboy
I am at times an advocate for the company, mostly because I enjoy the design philosophy they have but also because someone on this earth has to speak out for common sense, good engineering, and against blind hatred. It might as well be me even though some people seem to bitterly hate Apple and attack any who dare speak well of them. If you're pleasing everyone, you're doing something wrong.
and a particularly tiresome one at that
Which means you are tired of me, which means I am once again painfully (for you) on target in dismissing Hater complaints. Thanks for the feedback!
"There is more worth loving than we have strength to love." - Brian Jay Stanley
I've seen quite a bit of evidence to suggest that Flash video runs fine on Android ( http://www.youtube.com/watch?v=stW8gS6rBvg & http://www.youtube.com/watch?v=cb9jfdltkUU ) and I don't have any problems myself - so the youtube tests showing awful Flash performance would have to be entirely disregarded.
Unless their phones are faulty - the simplest explanation is that there are some idiots out there with an axe to grind on this issue - something it would be quite difficult to argue against.
I expected them to back down on that requirement as soon as I heard about it. It was rank idiocy to begin with, not least because it was unenforceable and a bad PR move. I'd be surprised if anyone actually paid attention to it.
i'd hit it so hard, if you pulled me out you'd be the king of britain [bash.org]
This has always been the modus operandi of every company: shit on users when you're on top, become user friendly when you started losing. Nintendo, Microsoft, Apple, Sony, etc. When they were king of the hill, they would ignore developers and consumers? Why? Because they could! One example is Nintendo. When they released the Nintendo 64, they were the ABSOLUTE undisputed kings of consoles. 3rd party developers could get NO support, their in house stuff was priority. Then Sony came along and ate their lunch. The Gamecube saw a humbled Nintendo start to be more friendly to developers. Of course the success of the Wii has seen them revert back to the hostile patterns.
Yes, you and your sample size of 1 means nobody has Flash issues, and if they do, they must be dumb.
Apple's App Store Guidelines Don't Change Anything
Falcon
Should there be a Law?
The fact that windows does not have a central update system and every app has to do their own update mechanism is a bad thing of windows.
No, it's a good thing, you don't have a single gatekeeper deciding what can be installed. While a gatekeeper may work for some people many others want to be able to install whatever. While it's obvious many people love iPhones and iPads, if I ever get a smart phone or tablet it's likely to run Android. Well, I'd like to get a tablet like the Modbook Pro, however it runs OSX not the crippled iOS.
Falcon
Should there be a Law?
this /. post makes no sense. no downloading code? so no embedding a web browser in a ui that downloads javascript code? Did /. f this up and misunderstand again? Sorry I'm not an apple developer, so I'm not reading their license
Only 'flamers' flame!
Does slashdot hate my posts?
Now if they'll relax a few more I might actually buy an iPhone again.
Specifically. Let other music app/stores exist. I want Amazon to be able to download songs directly, not only iTMS. I also want to be able to subscribe to podcasts on my iPhone. I shouldn't have to plug it in to desktop iTunes for that.
Finally, let me read the memory as a USB drive for all data so I can copy music, pdfs, videos, pictures and other stuff on/off the phone without iTunes. Apple doesn't have to add this to iOS they just have to allow apps that make it possible.
Well, here's hoping.
But then again, I believe iphone gaming is a fad. Apple are too hostile to game companies who want to be able to update their own code
Again, they can simply release a software update through Apple. It's really not like that's as time critical as a potential game crack is...
You think updates for games delivered via PSN do not see any Sony double-checking? Or any other platforms? Dream on.
And if you think iOS gaming at this point is a fad, you REALLY haven't been paying attention to what is going on in this space! Apple is supporting game makers big-time now, and I'm not sure there are any major independent game companies now who have not got a number of iPhone or iPad projects going. Nor have you seen the latest Unreal Engine tech demo...
"There is more worth loving than we have strength to love." - Brian Jay Stanley
i can't use iphone4 to make order online on replica hanbdags wholesale website www.milanmall.com ,also can't visit www.idoebay.com
The FTC investigation would only need to insist Apple play by the rules and remove all apps that were not written only in Objective C.
You would probably lose 99% of the games on the store.
How long will it take until they change it again, 2 months? I'm not exactly sure developers rejoice in such a dynamic legal landscape. Can't they just work it out right one time and stick to it?
I didn't say anyone was dumb. When i referred to idiots i was talking about fanboys that might deliberately introduce bias into their test.
The point is that if I've seen evidence that something works (youtube vids) and i also have direct personal evidence that it works (my own experience) then when someone suggests that this something does not work then i will tend not to believe them, and will question whether they are testing in a fair way.
Let me know if this is clear or i can rustle up a car analogy for you :)