Mark Zuckerberg: Our Biggest Mistake Was Betting on HTML5


Recommended Posts

Today, Mark Zuckerberg revealed that Facebook?s mobile strategy relied too much on HTML5, rather than native applications.

Not only was this a big mistake with mobile, but Zuckerberg says that its biggest mistake period was the focus on HTML5. This is the first time that the Facebook CEO has openly admitted this, but things are looking good for the new iOS native app. According to Zuckerberg, people are consuming twice as many feed stories since the update to the new iOS app, which is great.

http://techcrunch.co...-much-on-html5/

Just another proof that HTML5 is TERRIBLE.

No, this is just proof that HTLM5 is a terrible sustitute for native apps. It's the only thing that this proves.

HTML 5 is being charged with delivering far too much. There is a strong attempt to reach the Software as a Service future and HTML 5 is being pushed hard as the road to get us there. There will always be a need for native apps and web apps... By allowing the two to co-exist and do what its best for them both we end up better off. No need to squish it all into one pot.

Well since HTML5 web-apps added to the home screen of iPhones and Android devices cannot send notifications to peoples devices or have badges placed on their icons on the home screen errr duh?

You can't have a social platform without proper notifications. It would be like having skype that never told you when you had an incoming phone call.

  • Like 3
Just another proof that HTML5 is TERRIBLE.

Boz, you should start working for the Ministry of Public "Enlightenment" and Propaganda of a dictatorial regime somewhere. You'll definitely be a great asset.

  • Like 2

Everyone knows that HTML5 is not a finished standard yet. Yeah, I'd say they made a huge mistake relying on it.

It's fine to rely on HTML5, just not to the degree where you completely replace native apps by the technology. Facebook thought they had found an easy way to build cross-platform apps. They were simply being cheap and lazy, something their mobile products clearly demonstrated.

It's fine to rely on HTML5, just not to the degree where you completely replace native apps by the technology.

It's not fine to rely on HTML5 because:

A) It barely works on maybe 50% of the browsers

B) It doesn't even work properly on mobile through a browser (fragmentation is even worse with feature sets) and on mobile it's even worse.

C) It's slow and any interactivity is a DOG on CPU and on mobile again tons of features don't even work right. Differences between iOS and Android implementation to start.

D) It doesn't have access to native APIs but only those who are supported by the browser and even then the supported APIs differ from one browser/platform to another.

E) It's not even finalized and now W3C and WHATWG have split the spec in two versions making even more problems with compatibility

F) It's just SLOW as hell. It can't even compare to anything native and even Flash. It's just slightly modernized HTML platform (not finished with specs I might add because they can't agree on many things) that is still relying on 15 year old scripting language that hasn't evolved at all and the foundation of the issues with HTML haven't been solved. They just tried to build upon an already broken model that is dependent on browser support for features.

G) Google, Mozilla and Microsoft are all trying to create their own HTML5+ specs that they think benefits their platforms. It's basically a clusterf***

The only thing HTML5, and actually HTML by default has, which is nothing new, is usability over the content shown as it is easily searchable due to it's semantic nature but even that is not really HTML5 thing.. This was a fact even before HTML5.

It's not fine to rely on HTML5 because:

It's fine for simple things. Per example I never experienced any problems with HTML5 videos in Safari. As I said before just not for advanced applications like basing entire apps around it. That's just plain stupid and obviously you're going to run into the problems Facebook was facing.

Just another proof that HTML5 is TERRIBLE.

It's fine for simple things. Per example I never experienced any problems with HTML5 videos in Safari. As I said before just not for advanced applications like basing entire apps around it. That's just plain stupid and obviously you're going to run into the problems Facebook was facing.

Adobe is focusing heavily on HTML5 for mobile platforms, even ditching their own Flash product for it.

http://blogs.adobe.c...lash-focus.html

Windows Modern UI, Windows RT, and Windows Phone 8 native apps are developed with HTML5. Microsoft even went as far as to bake JavaScript into their new runtime, WinRT, so that HTML5 applications would perform as well as C++ and C# applications.

The problem was that they didn't have a native app, period. It was a grand miscalculation to assume that people didn't want notifications from their social network, or direct access to the camera or sensors.

Adobe is focusing heavily on HTML5 for mobile platforms, even ditching their own Flash product for it.

http://blogs.adobe.c...lash-focus.html

Considering I'm also an Adobe partner I can tell you with absolute confidence that Adobe is not ditching Flash at all.. quite the contrary.. the new versions of Flash are going to be pretty amazing. Especially when we get to Flash Next. Even now, Flash 11.4 has multithreading//concurrency in code and full support for StageVideo and Stage3D fully GPU accelerated APIs.

Adobe AIR is taking a very good spot in creating fully GPU accelerated native app experiences with, you guessed it, Flash/AS (actually AIR but it's pretty much the same thing). Even Adobe's own apps like Photoshop and other stuff for mobile are made with Flash/AS3/AIR basically..

Only in the eyes of those who are narrowminded it's a HTML5 vs Flash thing. It was never like that and it won't be.. Flash is built on top of HTML. It's an addition to HTML/JS/CSS, it's not a versus thing.

Adobe is trying to find their own place and push HTML5 to the level of Flash and that's normal. They have always done that. It's not like Adobe overnight decided to just support HTML5. Dreamweaver, Fireworks and many other things produced before supported were helping people build HTML/JS/CSS experiences. They have just invested more trying to make some tools that par Flash ones for those who want to create animations and similar stuff with HTML. It's natural for a creative company like them.

Flash is actually getting used more and more again because people have built stuff in HTML5 and when they need to maintain it, build to support various browsers it costs clients 3 times more money to do it in HTML5. So they are going back to Flash for many things. I know this because I have spent a lot of time building stuff in Flash a while back and I have a lot of people in my profession getting more and more Flash work again. So I can see the reactions. Not only that, but Adobe has been forced by companies to re-publish Flash for Android in UK because companies are starting to complain now.

Both HTML and Flash have their place and that won't change. Actually if you add games to the equation you will see that a lot of people are making some pretty amazing games now in Flash too because HTML5 is just not up to par in providing a fluid and smooth experience like Flash does not to mention getting into the whole audio/video support fiasco.

Considering I'm also an Adobe partner I can tell you with absolute confidence that Adobe is not ditching Flash at all.. quite the contrary.. the new versions of Flash are going to be pretty amazing. Especially when we get to Flash Next.

Both HTML and Flash have their place and that won't change. Actually if you add games to the equation you will see that a lot of people are making some pretty amazing games now in Flash too because HTML5 is just not up to par in providing a fluid and smooth experience like Flash does.

Adobe seems to disagree with you on it's public statements to businesses and developers relating to the future of Flash.

... This makes HTML5 the best solution for creating and deploying content in the browser across mobile platforms. We are excited about this' date=' and will continue our work with key players in the HTML community, including Google, Apple, Microsoft and RIM, to drive HTML5 innovation they can use to advance their mobile browsers.[/quote']
We will no longer continue to develop Flash Player in the browser to work with new mobile device configurations (chipset' date=' browser, OS version, etc.) following the upcoming release of Flash Player 11.1 for Android and BlackBerry PlayBook.[/quote']

http://blogs.adobe.com/conversations/2011/11/flash-focus.html

Increasingly' date=' rich motion graphics will be deployed directly via the browser using HTML5, CSS3, JavaScript and other modern web technologies. While the primary role of Flash Player as an engine for innovation on the web remains the same, what it is used for will change.

Adobe believes that the Flash runtimes are particularly and uniquely suited for two primary use cases: creating and deploying rich, expressive games with console-quality graphics and deploying premium video.

This shift in focus for Flash does not mean that existing content will no longer run, or that Flash cannot be used for content other than gaming and premium video. However, it does mean that when prioritizing future development and bug fixes, gaming and premium video use cases will take priority.[/quote']

http://www.adobe.com/devnet/flashplatform/whitepapers/roadmap.html

If HTML5 is so terrible, why have Google, Apple, Microsoft, and Adobe embraced it so fervently?

Adobe seems to disagree with you on it's public statements to businesses and developers relating to the future of Flash.

If HTML5 is so terrible, why have Google, Apple, Microsoft, and Adobe embraced it so fervently?

Because it's HTML.. it's not some new thing. Companies supported HTML before.. this is not something new.

and btw, Adobe is looking at HTML5 hype and trying to make money off it. They have been contributing to W3C for a long time. Again nothing new.

And Flash Player for mobile was abandoned because they just felt the future is not in a mobile browser but in native apps thus pushing AIR and Flash on desktops. It's not brain science.

I personally think it was their mistake because as I said, they are getting a LOT of backlash for abandoning it but I fully understand their decision from logic standpoint. As this article proves, mobile web is dead or dying. Everything is going native app route. Even Google makes apps now natively for mobile and have pretty much abandoned HTML5 on it for their apps.

Because it's HTML.. it's not some new thing. Companies supported HTML before.. this is not something new.

It is new to state that it's better than Adobe's own technology for delivering content in the browser.

... HTML5 the best solution for creating and deploying content in the browser across mobile platforms.

And Flash Player for mobile was abandoned because they just felt the future is not in a mobile browser but in native apps thus pushing AIR and Flash on desktops. It's not brain science.

So they decided that ignoring everything in the browser on mobile devices was a good idea... brain science (I think you meant "surgery").

Any web developer who uses HTML5 and JavaScript can build apps for Windows 8, Windows RT, and Windows Phone 8. So, AIR will be a good way to build native apps for iPhones and Androids, OK.

Flash on the desktop will have TWO usage scenarios explicitly supported by Adobe in the future, high-end gaming and premium (Netflix, HBO) video.

Adobe believes that the Flash runtimes are particularly and uniquely suited for two primary use cases: creating and deploying rich, expressive games with console-quality graphics and deploying premium video.

This shift in focus for Flash does not mean that existing content will no longer run, or that Flash cannot be used for content other than gaming and premium video. However, it does mean that when prioritizing future development and bug fixes, gaming and premium video use cases will take priority.

http://www.adobe.com/devnet/flashplatform/whitepapers/roadmap.html

Adobe is saying here that not only will their future Flash development be focused in these areas, but so also should any businesses' or developers' future development In Flash. Developers can still use Flash for other scenarios, but at their own risk. "... when prioritizing future development and bug fixes, gaming and premium video use cases will take priority."

Mark Zuckerberg revealed that Facebook?s mobile strategy relied too much on HTML5, rather than native applications

Just another proof that HTML5 is TERRIBLE.

compared to native full fledged applications, yea. and is what Zuckerberg was saying

its shurely not Flash like you keep preaching on about

Developers can still use Flash for other scenarios, but at their own risk. "

LOL.. Flash is Flash and Actionscript 3 is Actionscript 3.. and basically those 2 things (gaming and premium video) are actually the things that improve performance for everything else.

Instead of quoting stuff, I'm telling you what Adobe is saying to all of us partners on private forums. They are pretty much focused on pushing Flash Player forward in a big way.

Having amazing 3D and video capabilities will allow anyone to build some pretty fantastic apps for the web too. It goes hand in hand.

And having premium video and awesome gaming performance and capabilities will almost certainly keep Flash around for A LONG time for a premium rich interactive media content. This means awesome 3D stuff, video, cool interfaces and so much more.

E) It's not even finalized and now W3C and WHATWG have split the spec in two versions making even more problems with compatibility

Perhaps you should quit your slandering of something that isn't finished.

Instead of quoting stuff, I'm telling you what Adobe is saying to all of us partners on private forums. They are pretty much focused on pushing Flash Player forward in a big way.

I'm just telling you what Adobe is saying to businesses and developers publicly, and on the record. This is information that Adobe expects them to use to make the best determination of how to invest in Adobe's technology, and to give them an understanding of how Adobe would like them to invest in their technology.

This shift in focus for Flash does not mean that existing content will no longer run, or that Flash cannot be used for content other than gaming and premium video. However, it does mean that when prioritizing future development and bug fixes, gaming and premium video use cases will take priority.

http://www.adobe.com...rs/roadmap.html

Having amazing 3D and video capabilities will allow anyone to build some pretty fantastic apps for the web too. It goes hand in hand.

The web, as in, on the desktop. If you believe the future of the web is on the desktop, that may seem like a good gamble. I would rather not take that gamble.

Perhaps you should quit your slandering of something that isn't finished.

Of course you can.. this whole hype has been going on since original iPhone came out in 2007. And it hasn't improved at all. Same problems, same issues. By the looks of it, it will be finished by 2021 if ever and by that time the question is whether or not internet and the tech landscape will even look as it does today.

The web, as in, on the desktop. If you believe the future of the web is on the desktop, that may seem like a good gamble. I would rather not take that gamble.

Well what are you going to gamble on.. mobile? HTML5 is already dead on that. People are going native not HTML5.

Btw, I agree with you, desktop will not last forever as well. But I wouldn't bet on building HTML5 stuff for mobile. That's a dead end if it ever was one.

Of course you can.. this whole hype has been going on since original iPhone came out in 2007. And it hasn't improved at all. Same problems, same issues. By the looks of it, it will be finished by 2021 if ever and by that time the question is whether or not internet and the tech landscape will even look as it does today.

And you know how people hate their iPhones and iPads... If only they had been successful Apple might not be in the horrible financial position it's in.

This topic is now closed to further replies.
  • Posts

    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
    • Tor Browser 15.0.17 by Razvan Serea Protect your privacy. Defend yourself against network surveillance and traffic analysis. Tor is a network of virtual tunnels that allows people and groups to improve their privacy and security on the Internet. The Tor software protects you by bouncing your communications around a distributed network of relays run by volunteers all around the world: it prevents somebody from watching your Internet connection and learning what sites you visit, it prevents the sites you visit from learning your physical location, and it lets you access sites which are blocked. The Tor Browser Bundle lets you use Tor on Windows, Mac OS X, or Linux without needing to install any software. It can run off a USB flash drive, comes with a pre-configured web browser to protect your anonymity, and is self-contained. Tor Browser 15.0.17 changelog: All Platforms Updated Tor to 0.4.9.11 Updated NoScript to 13.6.25.1984 Build System / All Platforms Bug tor-browser-build#41821: Update gpg subkeys for boklm Bug tor-browser-build#41827: Update morgan's keychain with renewed key Download: Tor Browser (64-bit) | Tor Browser (32-bit) | 109.0 MB (Open Source) View: Tor Browser Website | Other Operating Systems Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!