2011.01.31

iPad is the new IE6

Imagine you are working on a project targeted for the iPad, Chrome and Safari that should contain an interactive HTML5 video… Design and feature-wise the project seems pretty simple and since you assume that the newest Webkit browsers have a good support for CSS3/HTML5/JavaScript (and Steve Jobs says it’s “amazing”) you shouldn’t have any issues building it, especially since you have coded many video players and interactive videos using Flash before and you are pretty experienced with HTML/JS projects and have used HTML5 video and CSS transitions/animations on a couple other projects.. A couple weeks of development should be fine… – Now you have a big problem.

Since the last year with all the hype around HTML5 and the buzz about “how HTML5 is going to save the web” and that “flash is dead”, etc… A lot of people started to believe that HTML5 is ready for production and that it is more stable and have better performance than Flash… Since the beginning I’ve been saying to everyone that it isn’t true and it won’t be for a long time. Why not? because every single platform have bugs, and it takes years to find, document and fix all of them, and more complex systems have more room for problems… – Browsers don’t even support all the CSS 2.1 features that I’ve read about on specs and blogs around 5 years ago (yes, I read the “whole” CSS 2.1 spec back then and got frustrated since I couldn’t use the cool features..).

Yesterday I’ve sent this on twitter and I really mean it:

People complain that Flash have bugs only because they never tried to do anything “complex” using HTML5 video on the iPad.. – Miller Medeiros, Jan 2011

Things that you would take for granted like seeking to a specific time, preloading/buffering a video on the background, starting a video without user interaction, having multiple videos on the same page, testing on the simulator, looping the video after end, etc… simply won’t work the way you expected without hacks or even worse, some of them don’t work at all.

The worse part of it is that you can’t simply search blogs/forums or look the documentation to figure out how to solve the problems, since “nobody” knows how to do those things, information gets outdated really fast with the release of a new OS version, documentations are very poor and doesn’t cover edge-cases, specs are constantly changing and different versions of iOS adopt a different set of rules and to add to the mix Apple is also creating many proprietary features…

Why am I having this kind of issues? Because a lot of people have been advertising that HTML5 can totally replace Flash and even that it is better than Flash, it may be true depending on the kind of project, but for heavily interactive/multimedia content Flash still the best available option… People are expecting too much of HTML5 and unfortunately the browsers can’t deliver it yet.

I’m saying that the iPad is the new IE6 because we are expecting it to be something that it isn’t, the same way that we were expecting that IE6 would have the same features/performance/reliability than the latest versions of Firefox/Safari. It takes years and many iterations to a technology become “stable”, early adoption of standards and poor implementation leads to headaches. It happened with IE6 and it is happening with the iOS Safari right now.

It took years for the community to learn how to deal with IE6 and to solve many bugs, the “problem” nowadays is that the release cycle of the browsers is so short and there are so few people doing this kind of things that the solutions for most problems may come “too late”. Nowadays it usually takes me less than 1 hour to make a website that I coded during 2 weeks testing only on Firefox to run on IE 6-7, but it took me 3 days to make something that I coded in 1 day testing on Chrome to run on the iPad (almost the same ratio of when I didn’t knew how to fix/avoid IE problems..) – and no, I’m not exaggerating/kidding.

Important notes:

  • HTML wasn’t created for dynamic/interactive content, it was created to present academic documents.
  • JavaScript performance on iOS is 100x worse than desktop.
  • Canvas performance on iOS is so bad that it is barely usable.
  • A lot of people don’t upgrade their software, iOS 3.2 is completely different than iOS 4.2 and you should support both.
  • The iOS simulator is different than the actual device.
  • It is very important to note that every single Webkit browser works differently and that older versions of the iOS have many bugs and missing features (the new ones as well).
  • Chrome and Safari have a bunch of rendering problems related with HTML5 video and CSS3 as well when you start overlaying content and adding CSS transitions.
  • Android 2.0-2.2 also have many bugs related with HTML5 video.
  • Using specs as documentation can be really frustrating when things don’t work as described and/or if the specs changed since the feature was implemented.
  • Apple bug tracker sucks, you can’t even see if anyone reported the same bug before, I won’t post anything there because of that and because I don’t agree with the company policy… - If you are a jerk, I will be a jerk with you as well…
  • If it works well the end user will not care about which technology was used to create it.
  • Don’t believe in keynotes, even better, don’t watch them…

Maybe I will write a new post after I finish the project explaining the bugs (with example files) and how to solve them. But I don’t promise anything and if I do it, it should take a while since I’m really busy now fixing bugs :(. For now you will have to believe that the bugs exist, if you don’t believe me, just search stackoverflow for it, here are a few examples:

I managed to solve some of those problems and a couple more but didn’t had time to reply to the questions yet since I’m really busy and I don’t even know exactly how I fixed some of the problems (I will have to spend a long time reading the notes I left on the source code and isolating the problems).

TL;DR

The closer you are to edge the more problems you will find. Every software/platform has bugs and HTML5 still very young and at “beta quality”, stop spreading lies.

PS: it is strange how companies like Apple, Microsoft and Facebook make me not want to share information about how to solve problems on their platforms and also not report bugs… I always report bugs on Firefox, Chrome and Flash when I’m able to isolate the problem and make sure it is a real bug. – I guess it’s because I don’t like to help people/companies that just want to screw the others…

Follow up: HTML5 video issues on the iPad and how to solve them & Unsolved HTML5 video issues on iOS


Comments

Gabriel Plegge

Simply the best article about html x flash, not for defending flash, but for being written by who understands the development of both technologies.

As for testing, you just need an iPad with 4.2 installed, and another with 3.2, and an iPhone 4 with each, and and iPhone 3GS with each, and ... hmm... Apple's strategy is starting to make sense.

The last comment was somewhat in jest, but in truth, my company has a number of devices hanging around, with older OSes on them for just this purpose.

Really well written and argumented! Congrats.

You can report problems for just about any Microsoft product at http://connect.microsoft.com...

John The Dancing Monkey

— "HTML wasn’t created for dynamic/interactive content, it was created to present academic documents."

"Was" being the operative word. We've come a long way and HTML has evolved, your statement simply isn't the case any more. HTML has done more for communication and to support interactive information than Adobe could ever dream of Flash doing.

As for you experience with the iPad, I'm not entirely sure what you're doing wrong but every site I've built so far has worked first time, the same can be said for the sites in most smartphone browsers.

In addition to this I've had an iPad for maybe 6 months now, not once have I wished I had Flash running on it, it's just not necessary in all but the rarest of cases.

I've been enjoying the comments I get on my video that I produced shortly after SJ gave his infamous "About Flash" letter. People just don't get it when they claim that HTML5 is the way to go, "it'll solve all your problems". We know better... http://www.youtube.com/watch?v=rfmbZkqORX4

You forgot to mention Silverlight.

@John_The_Dancing_Monkey: if you keep things simple it will work on most devices without major problems, but when you do things that are outside the "common ground" you start experiencing problems that "no one else" had before. (all the bugs I've cited are known and many people reported it before though)

The difference between iOS 3.x and IE6 is that iPads die after a year or two of daily use so you have to buy a new one, effectively reducing the release cycle to a max of 2 years. Which is better with the 10 years+ we had to stick with IE6. But that said: I think the worst problem is how fast the software actually got scattered. I have here a iPod touch my wife uses with iPhoneOS2( at least I hope its 2). Very few features of html4 will actually make it into html5 that way anytime soon: i mean seriously: Who expect that millions of buyers that buy a tablet today to buy a new one in two years when they should spend all their money on it. This will lead to either a lot of old tablets in some areas, lots of scattering (meaning areas with lots of versions of the product) or just same IE6. All we developers can hope for is that the iPad is really that bad ... and breaks together with the iPhone and all that android phones out there. Better sooner than later. To me this statement itself sounds very ... uhm ... "mottainai"="a waste of resources".

Okay: But anyways: Thanks for putting that statement so well into words. Delighted by the reading.

Flash can't be the better option; simply because isn't there as an option on iOS.

Just get over it, and make amazing HTML5 sites, like so many other people do; or get into native apps. Embrace the constraints.

I feel better now, thanks.

@Thomas_Fuchs: I'll keep doing my work as I've been doing on the past years (I see bugs as a challenge)... The thing that upsets me is that a lot of people been helping to spread wrong information and fanboys and zealots simply can't accept the "truth"...

The iOS Safari have bugs the same way that IE6 do, the only difference is that people expect it to be flawless (and advertise it as being "amazing") while everyone has very low expectations with IE6. Clients and designers are expecting the same kind of features that the high-end flash websites have and nowadays it still impossible to do it, be it for the iPad, Chrome, Firefox, Opera or IE9... - I also had high expectations since I know about what Safari 5 and Chrome 9 are capable of and what is included on the HTML5 drafts but many of the "advanced" features that works on other browsers doesn't work on the iPad..

It doesn't mean that you cannot make cool HTML websites. It all depends on the kind of thing you are trying to do, how many platforms you want/need to support and how polished you want it to be... - I know your point-of-view and expectations are completely different than mine (specially after your comments on twitter yesterday).

Don't think that because you are not having problems that bugs doesn't exist.. iOS Safari is the new IE6 not because it has a broken CSS box-model, but because it has really poor implementation of standards and many proprietary features as well (the same way as IE6 did).

You know, if this were about brilliantly original multilayered multimedia experiences that would be one thing, but most Flash is either ads, slideshows, or video players.

Ads I don't care about. Slideshows and video players work fine in HTML5, and the simpler they are the better (bare video tags give you a better end-user experience in Safari than any other option, which is as it should be).

The only really proprietary things about Safari on iOS is either stuff you don't need to use (e.g. 3d CSS stuff) or touch-related. The latter is proprietary because no-one else has caught up to Apple on touch. Whether you like the way Apple has built out events etc. is another thing. I guess time will tell whether they become a standard for touch, or MS and Google forge different paths.

Standards only work when everyone uses them, which is extremely difficult to accomplish. With Flash, you only have to worry about what Adobe does. There are no gotchas, you can reasonably expect your app to work everywhere that has the minimum required version. The funny thing about HTML5 is Apple insists that open standards are better, yet they implement the standard very poorly and include their own proprietary extensions.

P.S. Slightly offtopic, but please learn your verb tenses for the verb "to have".

By now I've come to believe the flat-out worst thing about IE6 is not any single one of its bugs, but the sole fact it simply refuses to die and keeps on going and going no matter how many years pass and how old it gets. Let's hope the iPad browser in its current form doesn't endure anywhere near as long.

My grandmother still prefers her old rotary phone to her new cell phone. I understand why. But that doesn't make the rotary phone superior.

I can understand your frustration but I don't agree with your policy of not reporting the bugs. It just doesn't help anyone.

Why would you bother supporting iOS 3.2? Much like Firefox and Chrome, iOS pushes updates strongly enough that it seems reasonable to expect people to stay reasonably up-to-date. If you'd said 4.1 or similar, I could understand not taking advantage of bleeding-edge features right away, but 3.2?

Matt Johnston

That's an awful simile. IE6 still haunts the corridors of the web, foisted upon us by unscrupulous developers who insist on it for security purposes - a big WTF in my book.

No-one says the iPad is perfect. No-one says WebKit (the real target of your diatribe) is perfect. No-one says HTML5 is perfect. But the difference between these imperfect tools and IE6 is that they all have the Potential to improve.

No-one other than rabid fanbois (on every side of tye equation) disputes there are bugs but this discussion is just one more big FUD dollop to add to the pile. Why?

Because your diatribe is against iPad and not WebKit. But the latter won't get the hits. So you end up click-baiting. Because you talk in reasoned tones about Flash being preferable to a future HTML solution - which is a ridiculous position.

WebKit is here to stay. It's used on the top 3 mobile platforms.

Flash has found a fair weather friend in Google and the handset OEMs because people think it's a big deal on the web. But performance on every Android handset I've tried has sucked - if it works at all. And it would be naive to think that Google doesn't have some of their übermensch savants working on a lightweight flash killer. And they'll turn on Adobe and kill Flash support just like they pulled H.264 support when it suited them.

iPad at least can change, can be updated and can display content that works pretty much everywhere. It's not perfect and there's stuff it can't do but that stuff won't work on a lot of other devices either.

So make stuff that works. Simples.

What a load of waffle. Flash still has bugs, this has nothing to do with anything else having bugs. Yes, the ipad is not perfect, and support will get better. But flash down right sucks, it is a closed implementation controlled by one company, and while loved by designers, loathed by developers and everyone else.

@MATT JOHNSTON +1

I'm surprised there aren't Google ad's on here.

Phil Ricketts

The iPad isn't the new IE6 - simply because Apple update their software regularly. IE6 was shit because it never received incremental improvements - whereas Apple update iOS Safari often.

Even the original iPhone 3G gets a new version of Safari with the new version of iOS.

yawns, moves along

Hmm, controversial post, nice writing although I disagree on many points. Thank you.

Anyway, I don't see why on earth you would waste time making something work on older iOSes, you'd have used your time better supporting IE<6, those browsers having as much share of the internet usage as the older iOSes. And IE6 is probably the last thing on the usage share list you want to support, after that it's all so marginal that it's just a plain waste of resources.

However, I appreciate your view being from the both sides, and I appreciate dissing Apple, just remember it's not HTML5's fault that iPad sucks. It's also not WebKit's fault.

Evolution is painful, there's no denying it, but some can handle it smoothly instead of forcing people to buy new devices every time there's a software update.

... I did not know that HTML5 meant iPad and Safari Mobile ... and a full-screen canvas project I am working with is actually speeding pretty well. I got your anger my dear colleague, but I don't get why people still compare Flash and HTML5, neither why you pretend to enlightening us spreading other lies.

HTML5 is partially the present, and we all know this already, surely an overrated buzz-word as well, but most likely the cross platform future.

All bugs and feedbacks are more than welcome and the W3C, as well as other groups, are usually listening without problems.

Oh, the irony. Using the argument of a closed platform controlled by one company against Flash when referring to Apple and iOs?

If Apple cared so much about openness and developers: they would implement OTA updates in iOs to reduce OS fragmentation. They would allow developer to downgrade devices to older versions of iOs. They would provide links to download all the previous versions of the SDK. They would implement open formats like Ogg and webM and webGL...

The truth is that they don't give a monkey. What matters is the bottom line. And on iOs that means selling native apps and get their cut.

Finally! Finally someone sane enough not to jump on the cart of "all you knew is dead, throw away your desktop, because it's mobile time!".

You say HTML5 is young, no, it's not, it haven't been born yet. The specs aren't even ready.

So yes, the future might be in HTML5, mobile devices and whatnot, but right now, if you want stuff to work, there are tools that have been proved over the years to work, and people are not going to abandon them that fast.

It will take years until these new technologies mature to the step we can throw flash away.

Android might have problems with HTML5 video, but at least it supports flash. So no problem there :)

There should always be a fallback, and for the next few years I think you should always give the user the option to use flash instead of HTML5 video. Or better yet, turn it around. Show a flash player by default, and show a HTML5 option. That way you won't obstruct the user, and give them a chance to try it.

I think we can get away with simply laying out elements in HTML5...we may need Modernizr to do it but we can do it. It's waaaaaaay too early to use the APIs like and what not. You can use tag, but it takes a lot of fallbacks.

Compound "HTML wasn’t created for dynamic/interactive content, it was created to present academic documents" with "If it works well the end user will not care about which technology was used to create it", and the conclusion is still: The web browser is a document viewer, not an application platform. If Microsoft word viewer were more popular we would be doing VBA instead of JavaScript. Conceptually they are the same thing.

If you want to develop apps, you need to go native.

Most of your comments tell me one thing; you don't know anything about the technologies you are talking about.

You can get away with a lot of crappy tech these days just by saying it's "open" or "FOSS". It's the sorry state of things.

I bet a lot of these video issues boil down to the hardware video decoder. It probably doesn't allow smooth mixing into the OpenGL scene, doesn't support multiple videos at once, etc. Flash would trip on this too if using hw decode as it would have to on iPad.

hw decode limitations would also explain why the simulator doesn't match the device.

Groan. I'm with Fuchs.

Good read, "If it works well the end user will not care about which technology was used to create it." - exactly my point, people go on-on about Flash is dead, HTML5 will save the web. What a load of non-sense! Your article is good, because you take both sides into consideration. I agree, HTML5 is young, it needs more time and a lot of attention. In today's world developers should have been at the point where the platform/browser shouldn't make a difference. What should be important is the device capabilities e.g. screen size, processing power, gpu acceleration, etc. So in essence Flash is my platform of choice, because it's almost at that point. Theoretically you can build one application if multiple front-end implementations and you are assured that your app will perform correctly everywhere.

Thanks for article. :)

So really, the title of this post should be "The current version of mobile Safari on iOS is the new IE6". A bit less sensationalist than the current one...

Your complaints are valid, and your point is well made. But you're treating it as if mobile Safari will be the same forever. Apple sucks sometimes, but I'm pretty sure iOS Safari will keep being updated and the problems you list will slowly disappear.

I just happened to blog about something similar: that the Web is for Documents". Not that I don't like al the awesome web things, but I think trying to make the web the end-all and be-all for user interfaces and application platforms is wrong. We need to embrace what the web is best at: presenting and linking together documents and see how we can work to its strengths.

Can't say your arguments are 100% valid except for the one showing HTML5 as beta. Sure it's like beta, it is not finished yet.

To the point, people can also not update flash, and while you might dismiss this argument - it's still valid. If you have old flash you don't get some features youtube has to offer and so on. So how do you take this into account?

And on mobile devices? There is, to be honest, no flash on mobile devices. What is available currently can be compared to JS/HTML5 being terribly slower or being unusable completely.

Oh and by the way - Flash performance and stability is horrible on every platform except MS IE (PC X86). Forget about ARM and even OSX X86/64.

And touch interfaces in Flash? Plus, Flash is a plugin. It is hard to call a proprietary not-always-present plugin thing as a standard.

What is your point actually? All the HTML5 cons are subjective at best if what you're doing is comparing them to Flash.

Either Flash or HTML5, there are no warranties.

At least WebKit and HTML5 are here to stay. For a very long term. Take Windows coming to ARM platforms, take mobile markets which do f* explode, look some time forward to HTML5 being completed and endorsed as such.

It's going to be the future web standard. No questions there. Talking about future, you should think about future, not about today.

Reading this article, Apple's strategy seems clear: promote HTML5 as an alternative to Flash but make it just crappy enough so that developers targeting the iPad/iPod prefer to write native apps. Bad canvas performance, especially, should severely hurt Adobe's new Flash-to-HTML5 converter.

Pretty stupid article ;)

Hisham has nailed this one. Talking up HTML5 is a marketing ploy to move folks away from android/flash, but its a bait and switch once you realize their implementation is intentionally crippled. The critical evidence to support this is that Apple has turned off sound support in mobile HTML5 web apps. The user must explicitly click on a sound link to activate it.

They claim that this will save bandwidth on expensive phone plans, but if you consider that the user may be on WiFi, they have provided no option for the user to opt in, and Apple/AT&T has never cared about excessive bandwidth usage before, you see these phony technical decisions are really all about protecting their native app business, just like what we typically see from Microsoft.

Ipad crashes on webfonts, and thats a bit fail.

I agree with Thomas. You say canvas is slow and unusable - how do explain this: http://www.mikechambers.com/html5/easeljs/PixelFlow/

Works smoothly on my Touch

Not so balanced an article.

One of the main reasons flash has become so hated (count me in) is the fact that flash has been used for everything under the sun. I have flash blocker and I can easily see pages filled with flash objects.

It is imperative that one makes the distinction between complex applications of flash and the banal image player or animations that can easily be done with the html 5 canvas.

This is a big distinction that allows, unfortunately, for the war to go on as both camps see each other right.

What I find ridiculous is the pompous superiority of the typical web designer who brags of advanced non obtrusive CSS, of graceful degradation of javascript because, you know, some people (in the arid deserts of Mongolia) might not have javascript turned on. And then, on the other hand, they fill pages with garbage flash that does not degrade at all. Even more so, some make their websites so dependent on flash that render them useless.

Go figure.

So, I suggest people keep their flash in the 20% of the web where it fits, and leaves the 60% to canvas and the remaining 20% to people like me who can do well without glitzy decorum

Alban Auzeill

I had the same experience with HTML5. I'm an expert in DHTML and a beginner with Flash. But for smooth and complex animation, it's easy and nice with Flash/Flex, and slow and jerky with HTML5.

The fundamental problem with HTML5 replacing flash is that HTML5 is a subset of Flash. HTML5 simply cannot handle interactive media like Flash can.

Some may justify this by saying that they don't want the web to be highly interactive, a notion which is fine by me too. Although I personally object to having manufacturers dictating the design of the web, that is unacceptable whether it be microsoft or apple.

But let's not forget the principal reason flash was actually banned by apple, they want to promote the apple store by eliminating all technologies with the potential to compete with it on the web. Hence, all VMs/emulators were explicitly banned, even Java. HTML5 was embraced by apple because of it's deficiencies.

It happened with IE6? I think you are doing revisionist history. Having broken implementations of internet standards was intentional with IE6. With the iPad, this is not the case. No matter how frustrated you are, people at Apple are at least trying, which is more than could be said for Microsoft during the IE6 days.

@THECARS

HTML5 is a subset of Flash? Have you been sniffing petrol?

The term you are all looking for is "appropriateness."

E.g., experiences on the desktop and not always appropriate on mobile/tablet. Pick up some decks on the usability of tablets and learn those contexts.

When feature A is implemented using HTML5 features from iOS v.B, that means it has to remain compatible within iOS v.C due to numerous apps written for v.B. So it is ie-like situation.

"A lot of people don’t upgrade their software, iOS 3.2 is completely different than iOS 4.2 and you should support both."

I wouldn't call 10% a lot. See : http://techcrunch.com/2011/01/17/ios-android-breakdown/

for me as linux user, a move to html is great because the linux version always lag behind in quality and performance. My native language is Hebrew and flash doesn't support display or input of Hebrew on linux for years now. We tried to send bug reports but i guess we're just too small fraction of thir userbase and it doen't pay for them to fix it. So you see? HTML5 is a great improvement for me and I can use it with my native language which makes it btter than Flash for my use.

[...] HTML5 Video = quebraderos de cabeza: Parece que está dando problemas a todo el mundo… [...]

What might a blind web developer learn after html to get started with css? I should read a css guide plus documentation for Non Visual Desktop Access and Job Access With Speech (jaws). I am blind.

[...] Here is the article: http://blog.millermedeiros.com/2011/01/ipad-is-the-new-ie6/ [...]

So, back to (old) school!? Thank fot this precious issue...

Yes, you are right but IE6 was a great software success! In the last 6 years I have used IE6, and thanks to library like jQuery and smart CSS guys I saved my days. So, if iPad will be our IE6, it will be a trouble for us, but every work must have its nasty problems. So, wellcome iPad!

There are blogs built on HTML5 and not e-commerece sites. I have asked many to show any e-commerce site built on HTML5 and never I get response.

I really like your last line "HTML5 still very young and at “beta quality”, stop spreading lies"

Brilliant! Maybe Stevie J has bitten off more than he can chew...

As @HTML5DOUCHE put it in twitter: TODAY I'M GRATEFUL FOR ALL THE YOACHES WHO THINK HTML5 ISN'T READY. GO AHEAD AND OBSOLETE YOURSELVES, IT WILL OPEN UP JOBS.

Couldn't have said it better myself.

Keep your eyes open to the future, the present isn't here to stay, you can keep saying HTML5 isn't ready for the next hundred years, but it won't change a thing. If you've studied history at all you'll notice that the people / companies who won't jump the sinking ship early enough drown with it. If you're not going to go HTML5 first you might as well start looking for a new job.

[...] Tweet RT @hackernewsbot The iPad is the new IE6… http://blog.millermedeiros.com/2011/01/ipad-is-the-new-ie6/ – by TLMDDM (julien [...]

"I wouldn't call 10% a lot. See : http://techcrunch.com/2011/01/17/ios-android-breakdown/"

According to http://www.dmwmedia.com/news/2011/01/19/apple-posts-record-profit-ipad-sales-surpass-projections, Apple sold 15 million iPads in 2010. That would mean with 10% of the people not upgrading, there are still 1.5 million people on the older OS. Have fun dealing with complaints from that many people because you don't want to support both versions of the OS.

Too much was promised, and 90% was marketing. In fact, I think in a few updates Apple will bring iOS to where it should already be. However, it's weird they developed support for WebSockets but have a poor HTML5 Video support.

Changing the topic, I think you shouldn't post on bug tracker if it's a mess. But let me give an opinion about the "If you are a jerk, I will be a jerk with you as well". If you accuse someone of doing something bad (being a jerky, for instance), you can't do the same thing or you will lose your point. If A kills B, then C will say A is wrong, but then will C try to kill A? Completely irrational.

I will wait for your tips on solving these problems.

HTML5 is the future, wether you like it or not. Just grit your teeth and work at it, or you will become obsolete.

Apple are looking to the future (as Steve Jobs does best) and the move to 'force' developers to 'embrace' HTML5 is a smart move that people just don't see yet but will appreciate further down the line. It is still young and comes with it's problems, and Apple has used this to it's advantage regarding native apps but this is a temporary biproduct of a bigger picture, not Apple's ultimate goal. Just good business, a smart move from a very successful company, what do people expect?

HTML5 is the future and Apple is one of the few companies who could get the ball seriously rolling, having a collection of products powerful enough to push the industry to take that big step. This move will not be given the credit it is deserved until looked back on further down the line.

At the end of the day Steve Jobs sees into the future in fine detail, better than anyone else and he continues to prove it with revolutionary products that change the game as we know it and sparks new technology races that spit out amazing things. Apple are innovators and if it wasn't for them the phones you use today or the tablets you're reading this on would probably not exist.

Anyway, HTML5 is the future and you need to get on board sooner rather than later, those of you who just deal with it, grit your teeth, stay strong and stick it out will be the ones reaping the rewards later. Those of you who just collapse, cry and refuse to move with the times opting to just p*ss and moan about how hard it is and how it is not ready (not ready for you) are going to fail and you may as well start thinking about a new career. I suggest you quit your moaning, get your arse into gear and work thru your issues. HTML5 is here to stay and it is going to be big, get in now and be ready for the next revolution.

[...] can provide, as by its nature that specification is in constant change. Witness this recent comment on a developer’s blog: “The worse part of it is that you can’t simply search blogs/forums or look the [...]

Flash has been open source for awhile. The Flex sdk is free, and there are free apps to code as3 without using the flash IDE. Also their seems to be a universal assumption that Flash has not and won't improve, when they have implemented upgrades very year. And the countless frameworks people have developed such as Papervision, Pixel Bender, wich add functionality that HTML5 can't touch. But alas this one needs to learn new technologies to stay competitive. The devs I know that do not embrace flash refuse to learn new languages in general that are not close to home, such as an HTML dev learning HTML5, do learning a language that requires OOP and design patterns such as as3 and iOS. We should attempt to learn as much as possible for our own career opportunities. So kudos to working with both flash and iOS, and documenting an opinion on both. Thanks.

You can either sit back and just wait for the spec and it's implementations to "mature themselves" or you could wake up, use the parts that are well known to work and join the effort of finding, fixing and documenting it all.

There's a whole community forming around these "polyfils" now and being a part of it, I can honestly say it's one of the most interesting movements I've ever seen in the world of technology. Yes, there are lot's of issues arising but why not take the time you spend writing disparaging, defeatist articles and come help instead.

Nothing would ever get done if people just played with specifications tentatively whilst telling everyone "it's not ready yet". Either be a part of it or shut up!

@Dev You'll change your tone pretty fast when you progress beyond being a complete and utter noob. It's a shame how people can't see how clueless they appear to others until they cease being a noob, which unfortunately for you may never happen.

born99andwhatisthis

Funny comic you have here, I have seen this quite some times. May I ask from which site it originates? Surely from truly funny and entertaining website.

Mmm fishies. Tastes so great. Hard to catch on a Microsoft device, easy to catch on Apple devices.

http://www.youtube.com/watch?v=FG30mtlDKOs&feature=player_embedded

HTML5 won't be "Recommended" until almost 2020. Until then, everyone needs to either put up or shut-up. If you think you're smarter than the developers writing the spec, and your not helping out - then help out or shut up. Flash is still a critical player and will continue to be for decades to come, and Silverlight is even a larger critical player now that its used in the XBox360, Desktop browsers, Windows Phone 7, many flavors of Windows, POSIX OSes, and many different flavors of Browsers.

Apple should stop being a donkey or a mule and start being more of the Mustang they once were and support the rest of the world. If you own your own OS and are worried about some plug-in the browser YOU WROTE wouldn't you just set-up a security context around your plug-in model.

One more thing, if we all spent 1 hour a day helping someone out instead of trolling the internet, the world would be a lot better and a happier place to live in. KTHXNJoyTheFish!

Congrats on your post! I love the way how "every" browsers are standard compliants, but they still doesn't show the same stuff, the same way...

"I always report bugs on Firefox, Chrome and Flash when I’m able to isolate the problem and make sure it is a real bug. – I guess it’s because I don’t like to help people/companies that just want to screw the others…" : I hope you're kidding here. Adobe loves to screw others (their free "CMS" in Dreamweaver which isn't free anymore, the mess they have made with Flex 4, Dreamweaver which hasn't been able to support XSL correctly for years, Adobe Reader which get more bloated at each new release,...) For me, Adobe is the Apple of the PC world.

I always use flash for video since I can design the UI to fit into the design better and I'm confident it will be consistent between browsers. Then I offer a HTML5 fall-back for H264 / WebM.

Flash was never alive. It has nothing to do with the Internet, it breaks all the rules of expected usability, etc etc etc... It's for making movies! I hate it, always have always will. To quote you and your 'simple' problem:

"Things that you would take for granted like seeking to a specific time, preloading/buffering a video on the background, starting a video without user interaction, having multiple videos on the same page, testing on the simulator, looping the video after end, etc… simply won’t work the way you expected without hacks or even worse, some of them don’t work at all."

— All those things are things that users DO NOT WANT; they hog bandwidth, relinquish our control, don't ask for our permission, etc etc... Get the hint!!! This is good for the web; not bad.

first time i found an article good enought to be shared and you don't have share plugins je je je... don't worry, i'll do it by hand :)

perhaps this could help you with the Video - http://www.kaltura.org/project/HTML5_Video_Media_JavaScript_Library

"The worse part of it is that you can’t simply search blogs/forums or look the documentation to figure out how to solve the problems, since “nobody” knows how to do those things"

This amused me. You mean that I, as a developer, might be required to do more than copy-paste solutions from the tubes? I might have to troubleshoot something?

you know, some of us are making complex html5 sites now. But if you would rather wait until you can read the O'reilly cookbook, by all means, I don't mind being first to market.

Fascinating post, and I'm sure that lest care is taken issues like these may persist with anything implementing or being implemented in the new HTML standard. Also great to see the Apple apologists trolling a subject matter like this, as expected, without even considering the issue at hand. Between a quote like "Embrace the constraints" and people making up lists of reasons why they don't, never have, never will, need anything presented using Flash, the unintentional humor of the comments don't disappoint.

I agree that HTML5, as a standard, leaves a lot up for interpretation, and there's plenty of fairly key functionality that's missing (read: everyone will implement it eventually, in their own broken, incompatible way).

According to Apple lore, Flash is a frequent cause of crashes, and I can't but agree with it. Heck, for me the behavior is cross-plaform! I've experienced it over the last 3 years of using OS X, that Flash is a source of frequent crashes. Maybe it's just me and the technical content I'm looking at, but it seems that Flash crashes at least 2-3 times daily for me, on three different machines, under two different OSes. Yes, everything is up to date, and it's on desktop/laptop machines, not on handheld devices. It'd be very rare that any sort of non-flash content, HTML5 or otherwise, would cause a browser crash for me. But Flash does it day-in, day-out. Since it recurs with some regularity, on diverse hardware and OS platforms, please don't blame flaky hardware on it. My regular uptimes on OS X 10.6 are measured in weeks, even XP in a VM manages mostly to stay up that long between VM reboots.

Side note: I've never ever had Flash crash on Youtube's video viewers. I consider them to be perhaps the best debugged and workaround-equipped pieces of software.

[...] iPad is the new IE6 | Blog (tags: article editorial technology apple flash html5 blog) [...]

Use JWPlayer to serve/present your video content. It conforms to the needs of browsers that can use Adobe's Flash Player, it also conforms to the needs of browsers that don't use the Flash Player but can use HTML5 (like iPad/iPhone), you can XML-skin it, you can do cool stuff with it using JavaScript APIs, etc.

[...] http://blog.millermedeiros.com/2011/01/ipad-is-the-new-ie6/ [...]

First, I work in the field since Netscape 3, I know many languages, server and client side. To be clear I'm more skilled on javascript and canvas api than 99,9% of idiots touting HTML5.

This world is full of shit, and this field is not different. HTML5 is not a standard, Canvas is a joke, Javascript is a nightmare. Who say the different is just ignorant. But arguing on that is pointless cause people are stupid and don't even know what are they talking about, and you can see that in the comments here ( a costumer today asked me if HTML5 can make coffee ).

Anyway, big corporations will do what is better for them not for you. So Google show CSS stuff that nobody had seen in any standards, push for WebGL that's you can't use since it's NEVER going to be on IE. Microsoft proudly present a new browser that still sucks but with super fast canvas, like someone care. Mozilla don't want to implement WebSql couse they are too smart for that ( ok, client storage is useless anyway since it has 5 Mb limit ) and they showcase their lighting fast firefox 4 with a demo that cripple a top level brand new pc ( the faces shadows). Apple, that made big money with retarded people, lie on anything and HTML5 on his iDevice is ridiculous slow, unusable.

The point is: developers are just going to be fuck up. Don't cheer up, you are not going use all the cool stuff you see unless you are sponsored from a browser maker.

Jobs damaged me with his lies and for this I don't feel sorry to say that Flash will die, but it's not going to be the first one.

Marvelous features of IE6 Mobile.

[...] lumea știe că iPadul este magic. Nu? Well… Nu prea. iPad pare a fi un fel de IE6. În plus, zilele astea am lucrat la un soi de webapp pentru ipad. Câteva din problemele [...]

BD I got to "At the end of the day Steve Jobs sees into the future in fine detail, better than anyone else" and then continued scrolling with my apple mouse, the one that right clicks without having to put my other hand on the keyboard.

Html5 on the iPad does suck. The animation is choppy and sometimes unnoticeable and u can only play one sound effect at a time so no rich applications or user experiences, also we can't position elements in a fixed state without some hacks and lose the ability to pinch zoom.

People that hate on flash don't know that they will hate HTML5 even more...I can use both so don't try to pin me into a fanboy corner. I'm pushing HTML5 on the desktop by I'm limited by what the iPad can do....

Ps Keith peters you are my hero for "making things move"

[...] iPad is the new IE6 article. .fb_iframe_widget { vertical-align: top !important; margin-left: 16px !important; } [...]

[...] So, this article was written over a year ago, but after working with the iPad, trying to develop HTML pages, having them work directly in Safari on this Mac I have at work, and then NOT working on either an iPad or the iOS simulator, I have to agree. The iPad is the new IE6. [...]

Very well told ... here is my story somewhat similiar http://sushilbharwani.blogspot.in/2012/03/apple-in-developers-day.html

["Browsers don’t even support all the CSS 2.1 features"].... CSS 2 API for javascript offers many great functions...none of them where ever implemented...

Excellent. Yes you really helped me with video on iPad thanks for the articles. I am a Flash coder but did an ipad html 5 ad. Wow! Some cool things but OMG what a bunch of work arounds! I can safely say html5 is as much an art as working on cross browser hacking for ie6. So many projects are coming back to Flash recently it is crazy. We are finding more people still on ie 7 and 8 than have html 5 on iPads, so we just have to go back to flash. I do think Apple of all should have had a rock solid video implementation in html5 on ios, But alas!

hmm but To set-up animated feature apps, it requires foresight and right communication between designers and coders.

I don't agree with you, I believe iPad is worst crap, one can simple workaround IE6, with iPad there is many times when there is no workarounds. F U C K APPLE

Leave a Comment

Please post only comments that will add value to the content of this page. Please read the about page to understand the objective of this blog and the way I think about it. Thanks.

Comments are parsed as Markdown and you can use basic HTML tags (a, blockquote, cite, code, del, em, strong) but some code may be striped if not escaped (specially PHP and HTML tags that aren't on the list). Line and paragraph breaks automatic. Code blocks should be indented with 4 spaces.