Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
Graphics Handhelds Software Apple

Why Flash Is Fundamentally Flawed On Touchscreen Devices 521

An anonymous reader passes along this excerpt from Roughly Drafted: "I'm a full-time Flash developer and I'd love to get paid to make Flash sites for the iPad. I want that to make sense — but it doesn't. Flash on the iPad will not (and should not) happen — and the main reason, as I see it, is one that never gets talked about: current Flash sites could never be made to work well on any touchscreen device, and this cannot be solved by Apple, Adobe, or magical new hardware. That's not because of slow mobile performance, battery drain or crashes. It's because of the hover or mouseover problem. ... All that Apple and Adobe could ever do is make current Flash content visible. It would be seen, but very often would not work."
This discussion has been archived. No new comments can be posted.

Why Flash Is Fundamentally Flawed On Touchscreen Devices

Comments Filter:
  • That's okay... (Score:5, Insightful)

    by Anonymous Coward on Sunday February 21, 2010 @01:03PM (#31219298)

    Current Flash-heavy sites do not work well on any other device either.

    Welcome to the problem of confusing "web site", "application", "advertisement" and "art installation".

    • Re:That's okay... (Score:5, Insightful)

      by multisync ( 218450 ) on Sunday February 21, 2010 @01:22PM (#31219562) Journal

      Straight up. Sites that use flash or javascript for navigation are an abomination.

      • Sites that use flash or javascript for navigation are an abomination.

        In that case, Slashdot is an abomination. It (optionally) uses XMLHttpRequest to load pieces of the comments page without requiring a refresh of the entire page. So why do you post on an abomination?

        • by multisync ( 218450 ) on Sunday February 21, 2010 @01:44PM (#31219838) Journal

          So why do you post on an abomination?

          I use the "old style" Slashdot interface, and reading a few comments back in my posting history would inform you on my opinion of changes Slashdot has made to this site (including changes to the interface and fundamental changes to the (meta)moderation system) in the name "Web 2.0."

          In that case, Slashdot is an abomination.

          You must be new here ;)

        • by cgenman ( 325138 ) on Sunday February 21, 2010 @03:55PM (#31221244) Homepage

          In that case, Slashdot is an abomination. It (optionally) uses XMLHttpRequest to load pieces of the comments page without requiring a refresh of the entire page. So why do you post on an abomination?

          A: Slashdot has interesting content.
          B: Slashdot is an abomination. Pagedown goes too far because the bar at the top steals precious real-estate for no reason. Accidentally navigating away and back loses all box text, despite years of tools which save that state for just such eventualities. It runs incredibly slow on iPhones, despite being basically a static page with a reply box. It has a bunch of "Web 1.5" stuff hanging around in the options which hasn't really done much in years. It took about 2 years after the site refresh before it would serve consistently across all browsers.

          Hooray for pushing the envelope for sake of pushing the envelope's sake. But if every website were coded like Slashdot, the web would be a far more painful place.

    • Re: (Score:3, Informative)

      by plover ( 150551 ) *

      The problem in TFA actually isn't about Flash(TM) itself, the real problem is the direct coupling of the mouse to the user interface experience via the web. "Hover" is a mouse-specific capability. Flash supports this capability, as well as javascript and other languages, (although Flash sites seem to rely on it more often than others.)

      Too many web designers assume a mouse is present, leading to all kinds of human factors problems, not the least of which is handicapped accessibility.

      Of course the idea that

  • Flash only? (Score:5, Insightful)

    by Anonymous Coward on Sunday February 21, 2010 @01:06PM (#31219328)

    I'm not into Flash development, but how would that be different from javascript hover and mouseover features? I think this is a flaw for any advanced interaction feature on any touch enabled device, which means it is not limited to the Flash technology in particular.

  • Really? (Score:3, Insightful)

    by Anonymous Coward on Sunday February 21, 2010 @01:07PM (#31219338)

    Most flash apps don't do anything interesting with hovering, so it would be perfectly fine if the implementation just did clicking, or hovering with some weird gesture.

    • Re:Really? (Score:5, Insightful)

      by im_thatoneguy ( 819432 ) on Sunday February 21, 2010 @06:24PM (#31222664)

      It's ok. Don't work to hard to understand the article because it's complete bullshit. I use flash all the time on my tablet PC using my finger. I've never ran into a problem. It would be a problem in a game where something follows your cursor but I personally find flash much more often used for video/interfaces etc.

    • Re: (Score:3, Insightful)

      by mjwx ( 966435 )
      The FTA's Authors complaints narrow down to one thing.

      But there's no mouse.

      I'm not a big fan of touchscreens, I'm not against them per se but I don't see them going beyond the phone/kiosk due to the physical limitations of using a touchscreen so they wont supplant the Mouse and Keyboard on the PC, at best they will become another peripheral (mouse, KB, Joystick and now touchpad).

      Now correct me if I'm wrong but is it not the job of the operating system to interpret user input from whichever input de
  • Not entirely true (Score:5, Insightful)

    by Runefox ( 905204 ) on Sunday February 21, 2010 @01:08PM (#31219340) Homepage

    If there's anything I've taken from all the Apple talk on its multitouch technology, it's that gestures are everything. What if when Flash is in use, dragging your finger across the display results in "moving the cursor", while a single touch results in a click? Or why not make it function much the same as how laptop touchpads work, where a double-tap+hold equals a click and drag? I can't see that being terribly difficult for Apple or anyone making a touch-based device to implement, really.

    I mean, perhaps there's more to it than that, but I can't see the concept of mouseover/hover being a huge showstopper for Flash support on touch-based devices. There are definitely ways around it, and for that matter, there's also CSS/JS mouseover/hover that works the same way. How is this handled on devices like the iPad? Is this also unusable?

    • by Nursie ( 632944 )

      I've been playing with the Nokia N900 recently and it has flash. Works fine *except* when I tried to play a flash game that required click and drag to draw lines. I couldn't find a way to do it that didn't just end up with the page being dragged around rather than the line I was trying to draw.

      It might just be that I don't know how to operate it properly, or it could be that there are a few input-related hurdles to get over, but fundamentally flawed? Don't see why at all.

    • Re: (Score:3, Insightful)

      by ink ( 4325 )

      How would you distinguish between drag and hover in that case? A touchpad has no buttons; it's not a trackpad.

      • by nahdude812 ( 88157 ) * on Sunday February 21, 2010 @01:24PM (#31219584) Homepage

        If the object under the start of the drag is draggable, then it's a drag. If it's not, then it's a hover. Just like trackpads, single finger interactions should not be a scroll action (I know they are, and that's the fundamental problem, not something endemic to Flash). You should use two fingers to scroll, one finger to drag/hover.

        Trackpads have solved all of these problems a long time ago, they are not unique to "touch" interfaces, except that touch interfaces have undone many of the solutions already discovered.

        • Re: (Score:3, Interesting)

          by ink ( 4325 )

          Google maps breaks your proposition; as you pointed out, it's using drag to scroll.

      • Re: (Score:2, Informative)

        by Runefox ( 905204 )

        Well, you can actually use a trackpad without buttons, too. A quick tap is a single click, a double-tap+hold is a click and drag.

      • Re: (Score:3, Interesting)

        by Ihmhi ( 1206036 )

        Drag your finger over the button and then remove your finger from the touchscreen?

      • by T Murphy ( 1054674 ) on Sunday February 21, 2010 @02:22PM (#31220268) Journal
        Easy. Use an optional peripheral that acts as a "virtual hand"- it controls where the "virtual finger" is at all times, so the cursor always has position information. This "virtual hand" could have buttons on it to perform "virtual clicks", and with multiple buttons it could perform both "virtual left clicks" and "virtual right clicks". The simplest implementation would track movement by having a ball on the bottom, so that it must be dragged on a surface to move it. With the right technology, an optical version might be feasible, reducing the number of moving parts.

        This is all theoretical of course. I doubt there would actually be any demand for these "virtual hand" devices.
    • From my understanding of Apple's capacitive sensing, it should be able to simulate variations in pressure by reading the rough diameter of touch. A light touch would have a small contact area for mouseover, a "click" could be a somewhat heavier touch or tap.

    • All that Apple and Adobe could ever do

      Does this guy really think he's smarter than the engineers at Apple and Adobe?

      Sounds to me like a defeatist attitude... The authors microwave probably flashes 12:00.

      I can think of a very simple fix - don't let the cursor hover over flash when a finger isn't on the screen.....move it off the animation. Dragging across the flash can activate the hover actions, releasing from a drag can act as click if hovering over a button immediately followed by moving the cursor off the animation. Wham, bam, he's wrong.

      • Simply do your animations on mouseDown and activate it on mouseUp like most sane people. I've also been doing flash (consequently, on 40,000 mobile devices for the company I work for) and I've been able to make flash work on a touch screen mobile device. I agree with your statement about being defeatist. It sounds like a rigid thinking programmer who took a course on how to do something and can't wrap their heads around alternative solutions.

    • Flash is one of the main languages used to develop Surface tables-- and those are nothing but giant touchscreens.

      I think the real point here doesn't have anything to do with Flash itself, it's just "applications built for a mouse won't necessarily work on a touchscreen." Which is... duh. (Also true of DHTML applications that make use of rollovers.)

    • Re: (Score:3, Insightful)

      by Anonymous Coward

      There's a very simple reason why this might technically work, but Apple will not allow it: It's unnatural. Touching the surface is not equivalent to the actionless pointing that the hover event represents. When the user touches the screen, that is already an action event and consequently it's usually mapped to what would be the start of a drag or click interaction on a mouse desktop: "Finger touches the surface = mouse button down." But note that the latter is not the cause but the consequence of touching i

  • Never? (Score:5, Insightful)

    by Rydia ( 556444 ) on Sunday February 21, 2010 @01:08PM (#31219348)

    "current Flash sites could never be made to work well on any touchscreen device"

    Really? Never? Just off the top of my head, I could envision a button that put the device in "pointer" mode, maybe with scroll buttons where appropriate, and then used the movement of your finger on the touchscreen as either 1:1 or some kind of relative movement of the pointer. There are probably issues with this approach, yes, but it took me seconds to cobble together. Saying that something is impossible as a matter of user interface is silly. You can always change the UI in some way to make it possible, or even good.

    • Re: (Score:2, Informative)

      by Apotekaren ( 904220 )
      The Nokia N900 has a "pointer-mode" in its browser. Slide your finger onto the screen from the left, and a pointer icon appears on the left. Click it to activate, and the icon gets a red x over it. You guessed it, clicking that icon will put you back in regular mode. It works very well on websites that use JS hover functions with say dropdown menus or something of the like.
    • Translation (Score:5, Informative)

      by Sycraft-fu ( 314770 ) on Sunday February 21, 2010 @01:26PM (#31219604)

      "I'm a Mac fanboy who also does some extremely bad flash design (http://adamsi.com/). I can't figure out how to make the silly, and unnecessary, rollovers on my site work on an iPad. I'm believe everything Apple does is brilliant so their decision to exclude Flash must also be brilliant. Therefore I have to conclude that Flash could never, ever, work on a touchscreen device."

      Serious bunch of BS in my opinion. For one, a large number of Flash sites, like the author's, seem to use mouse over for nothing more than effects. Fine, but hardly essential. If all that is transmitted is clicks, they still function ok. Second, the big reason people are up about Flash these days is videos and the like. For better or worse, Flash has become THE web video standard. That may eventually change, but no time soon. As we all know, standards change extremely slowly when there's something works and, well, Flash works. It's not perfect but on most computers, it works just fine for seeing a video of a silly cat jump in a box. Finally, if a site didn't work properly, oh well, shit happens. As it stands all Flash sites are GUARANTEED not to work at all.

      I don't buy this as a legit argument at all.

      • Re: (Score:3, Insightful)

        by Belial6 ( 794905 )
        More to the point. The author is not only an idiot because he isn't smart enough to think of how to make flash work with a touch screen... He is an idiot because there has already been a very successful touchscreen device that is 100% flash. The Leapster by Leapfrog [leapfrog.com] is a Flash only device [adobe.com]. You can buy it in any Toys R Us, and has been very successful. It works just fine.

        It seems that the current trend by Apple fanboys is to claim that Apple engineers are completely incompetent. Not long ago, it was
  • What??? (Score:5, Insightful)

    by MTO_B. ( 814477 ) on Sunday February 21, 2010 @01:11PM (#31219388) Homepage
    Just because some flash sites are not developing flash taking into account touchscreen devices (it's a new thing!) does not mean it cant be done. The whole thing seems stupid to me. It really scares me to think this person makes money developing flash sites. It seems he is totally unable to adapt, change his methods or do things better than he does. Come on! Sure there are flash files that would create problems and would need to be further developed, but to say it's fundamentally flawed because of that is bullshit.
    • Re: (Score:3, Informative)

      by yerM)M ( 720808 )
      I completely agree, at some level this seems like an implementation detail. A good example is how The Secret Of Monkey Island(TM) was ported to the iPhone. This had exactly the same problems as Flash. Being a port of an old point-and-click game they had issues with hover-over and they were able to form a solution for these issues.

      I thought it strange at first that it used a virtual cursor instead of just tapping on an object on the screen but it actually ended up working better and they were able to use

  • by shumacher ( 199043 ) on Sunday February 21, 2010 @01:13PM (#31219422)
    I have a ClarionMiND. It's one of the few Intel-based MIDs that made it to the US, and with firesale pricing, the $130 for an atom-based handheld looks quite a bit better than the $699 price at launch. It runs Firefox 3 and includes flash, but flash is of only limited utility. The on-screen keyboard can't detect when it's needed inside of flash. Mouseover doesn't exist. On the other hand, many sites use mouseover in their (x)html. Facebook, for example, allows one to delete a post or comment. The delete link is hidden until you mouse over the link. For me at least, it's surprisingly intuitive to use with a mouse, but I'm completely lost with a touch-only device. I find that I spend an excessive amount of time trying to figure my way around the car crash that is the merging of a mouse-centric internet with a device interface that doesn't do enough to cover for the internet's lack of accomodation for the devices interface.
    • by RulerOf ( 975607 ) on Sunday February 21, 2010 @01:40PM (#31219772)
      I have a Viliv S5 [myviliv.com] MID, and while I can't echo specifically to issues using Flash (other than the fact that the hardware accelerated 10.1 Flash doesn't yet support my chipset) I can say that mouseover based features are very difficult to utilize with the touch screen. I can switch the joystick on the left side to move the mouse, but that's tedious. I find that when I want to make right-click actions on things in the start menu, to bring up computer management for example, I often open the menu, do an invalid drag/drop (like documents to computer) and then hit the right click button.

      I could likely click and hold to get that functionality, but I sort of just figured that out while typing this.....
  • I agree with this article but I wonder if Flash could be changed to work differently on mobile devices - an auto-detect mode for mobile phones, for example.
  • by vitaflo ( 20507 ) on Sunday February 21, 2010 @01:13PM (#31219426) Homepage

    I'm in no way a supporter of Flash, but how is this any different than anything else in the browser with a :hover state? With the advent of HTML5 and the Canvas element, which does work on the iPad et al, you're going to run into the same issues if you program them the same way. Now I get his concern that Flash devs would have to rewrite a lot of their already written stuff to work on the iPad if it allowed Flash, but I fail to see how this is any different from the multitude of websites that use hover drop downs for navigation and the like.

    The point that we shouldn't be relying on hover states because of the push towards touch devices is a good one but it's not an exclusive problem to Flash. The reason Flash shouldn't be on the iPad, etc, is because it's a horrible bloated and proprietary plugin, and Canvas, HTML5 video, etc can do the same thing. Flash is now a dead end technology. It's only a matter of time before it's phased out altogether.

    • Re: (Score:3, Interesting)

      by hitmark ( 640295 )

      give the guy a +1. Hover issues exist, even without flash. I have seen several pages that use html, css or something similar to trigger drop down menus on hover. The better ones allow access to similar resources via a sub page accessed by clicking the trigger spot, the bad ones do nothing...

  • by h4rr4r ( 612664 ) on Sunday February 21, 2010 @01:14PM (#31219436)

    The title of the article should have been: "Why Flash is Fundamentally Flawed."

  • Thank you for spelling out the conclusions Apple likely made (internally) leading up to the decision not to support flash on
    it's initial release and brain storming some possible solutions. I don't see why the problem you've defined is anything more
    than just another engineering challenge. The web is a pretty elastic place, I'm sure it'll evolve as touch screen interfaces
    become more mainstream. I encourage you to view this as an opportunity to make a ton of money instead of a crisis.

    • Re: (Score:3, Insightful)

      by nahdude812 ( 88157 ) *

      Thank you for spelling out the conclusions Apple likely made (internally) leading up to the decision not to support flash on
      it's initial release and brain storming some possible solutions

      No, this isn't it. Their decision process goes more like this: "Flash allows people to run software on their phone that they didn't buy through the App Store. We have to reject it, but start thinking of reasons that don't sound so much like 'we are greedy bastards.'" Otherwise, where is Java? Hover is certainly not uni

  • First, the amount of hover usage in flash isn't that great. There are tons of completely static animations that don't have any interaction of any sort. And there are plenty games that just require clicking in place. A lot of flash content that gets passed around is stuff like the Kenya and Magical Trevor animations.

    Second, the lack of hover is simply a lack of imagination on Apple's part. On my N900 for instance, I can have a pointer that works for flash by starting to drag from the border of the screen. No

  • Most new devices with capacitative screens also support multitouch. Interpret touches with two fingers as mouse hover, and one finger as a click/click & hold, or vice versa, depending on what's more intuitive and better for accuracy. There, issue solved, no new hardware required.

    Or switch to digitizing technology for the displays which support better resolution for pressure. Interpret light touches as mouse hover.

    Not to mention that proximity detecting screens that Apple, of all companies, patented a wh

  • Reading TFA and the author's description of the mouseover/click problem, I get the sense that it's not a Flash problem per se but actually a fundamental limitation of the touchscreen interface. Simply put, the mouse/keyboard combination is a vastly more efficient and powerful way of accepting user input than a touchscreen.
  • No matter what excuses Apple comes out with or what other people say, the real reason is that having flash on the ipad or iphone would cost apple money. What is the main thing people use flash for? Watching video and playing games. What does Apple want to sell you through itunes? videos and games.
    • Ding ding ding ding ding ding!

      I love Apple's products as much as anyone, but the above comment's assessment of the situation is dead-on. They *could* make it happen, they certainly could make it an imperfect option, but the real fact is that Apple wants to keep a tight control the delivery of downloadable music, video and games on this platform.

    • So, um, why does it have a Youtube app? Hell, if that's their only motivation, why do they allow streaming music services like Spotify?
  • One is tempted to divide the flash world in two -- the majority of the flash apps are advertising plug-ins, while a minority are useful applications like games and such.

    The former should simply not be used on mobile devices. Most web pages are too filled with crud as it is, flashing ads that I don't ever look at are nothing more than a waste of space, time and power. On a mobile device this moves from annoying to a real problem.

    The games, on the other hand, I'd love to have. Sadly, in this case I agree full

  • Whatever reason Apple has for not liking Flash (I have yet to see a definitive explanation) all this negative press about Flash, coupled with the Flash/HTML5 debate can only be a good thing. In my view, Flash has way more things wrong with it (breaking the semantic web) than the benefits it brings to the table. If all this discussion either prompts Adobe to fix all that, or something better is suggested instead (HTML5?), it can only be a good thing.

  • The free games take away from the locked in app store.

  • The App Store (Score:5, Insightful)

    by jrap ( 614351 ) on Sunday February 21, 2010 @01:23PM (#31219576) Homepage
    The real reason why Apple would never allow Flash to work on one of it's mobile devices is simple. The App Store. Most of the available apps could easily be mimicked using Flash, and made easily available. This would not be a good thing for Apple's bottom line.
    • Not really. The AppStore makes a fair amount of money, but for Apple, it's just above break-even once they've taken bandwidth, marketing etc.
      What the AppStore is add value to the product; it sells hardware, much like iTunes does for iPods.

      So yeah, it would affect the bottom line somewhat, but that'd probably be bolstered by the fact a lot of good apps would be in the AppStore without any of the trivial crap-apps (iFart etc.).

      In addition they'd also be able to talk abut excepting Flash, which some people th

    • by RulerOf ( 975607 )

      Most of the available apps could easily be mimicked using Flash

      Indeed. I'm shocked at how frequently Slashdotters will offer technical reasons as to why Flash isn't on the iPhone, without realizing this. It makes me wonder if there was ever an article posted here on this.

    • Re:The App Store (Score:5, Informative)

      by Reverberant ( 303566 ) on Sunday February 21, 2010 @02:00PM (#31220000) Homepage

      The real reason why Apple would never allow Flash to work on one of it's mobile devices is simple. The App Store. Most of the available apps could easily be mimicked using Flash, and made easily available. This would not be a good thing for Apple's bottom line.

      As noted above [slashdot.org], this rationale is easily disproved by Apple's encouragement of offline HTML5 [apple.com] web apps.

  • I don't understand the massive criticisms Apple gets for not including Flash on the iPhone/iPad. These are not desktop computers; they are mobile devices with limited resources for limited purposes. If the iPhone came with Flash support, people would be complaining to the hills about their web surfing being SO SLOW and their batteries getting drained to the max.

    Many people (I'd even bet on saying most people) use Flash for viewing video, and HTML5 + H.264 take care of that quite well and much more efficient

  • by Spykk ( 823586 ) on Sunday February 21, 2010 @01:40PM (#31219780)
    Apple does not allow any software on these devices that could be used to develop an application. They would not even allow a basic interpreter. If flash worked people would be able to develop applications for the iPhone without Apple's blessing. Chances are they won't support things like the Canvas element in HTML5 either. Expect your browsing experience to become more limited in the future.
    • by Spykk ( 823586 ) on Sunday February 21, 2010 @01:45PM (#31219848)
      Well, I foolishly decided to do some fact checking after submitting my post and it turns out canvas is already supported on the iPhone. Excuse me while I pull my foot out of my mouth.
      • Re: (Score:3, Interesting)

        by jo_ham ( 604554 )

        Apple are in support of HTML5, even as an app development market. Flash is off the iPhone/iPad purely for licensing cost reasons and secondarily due to the UI issues - it's got little to do with competing with the app store itself. They make the bulk of the money on hardware sales, the app store breaks even/has small profit.

  • The article boils down to one argument: Many current Flash applications expect mouse hover, and since mouse hover is not supported on the iPad, all Flash applications will not work. Let me tear this down quite simply.

    1) This problem has nothing to do with Flash. It applies to all development tools. By his reasoning, no programming tools should be ported to the iPad.
    2) This problem has nothing to do with the iPad. It applies to almost all hand-held, portable, or touch-screen devices. By his reasoning, n

  • At the risk of sounding like flamebait... allow me to explain.

    There is absolutely nothing unique about Flash that makes it “fundamentally flawed” on a touchscreen. You have the same “problem” with ANY application on such a device, whether it be native code, Java, javascript/ajax, or Flash.

    It’s only a “problem” when you INSIST on using mousover effects, which are usually redundant and annoying anyway... and you’re an idiot if you design an application which can

  • Come on, is that really the only thing that this person could think of that is fundamentally flawed with flash?
  • Seriously people, this is Roughly Drafted we are talking about here. Sure the zealot in charge has now toned down the abusive comments and graphics on the page and made it look somewhat sanitised, but this is a site that is the Apple equivalent of Little Green Footballs in its heyday. Memorably referred to as the "lunatic fringe of Mac fandom [google.com]". Pretty much any article on that website is guaranteed to be slanted so much in favour of the Apple Party Line that to expect rational, even analysis is pointless. Flash has worked on dozens of touchscreen devices for years now. Many of these devices have come up with UI and/or gesture cues to invoke the rollover/mouseover state that Flash and Javascript like using (often involving a "pointer mode"). Because of Adobe's new push, Flash will soon be working on hundreds of new devices. As a result, I am sure that both the workarounds and new gestures to replace and to augment rollover will become both more usable and more common.

  • by Tronster ( 25566 ) on Sunday February 21, 2010 @01:50PM (#31219898) Homepage

    This entire story is FUD; I took the bite though...

    I'm a user interface lead at a game studio which is leveraging a Flash-based solution that could target consoles. I already did this once before on CnC3:Kane's Wrath (a title with PC and 360 SKUs), and have done contract work creating a Flash Lite application for the Sony Mylo 2 (touch screen.) Besides all this I also teach Introduction to Interactive Media at a local college which has a successful curriculum based around Flash, and yet touches on aspects of touch-devices and alternate input (non-browser) environments.

    All that said about my qualifications I make this statement:
    Flash works in it's existing form on these devices.

    Its my professional opinion that it would work fine on an iPad or iPhone and the non-technical agenda Apple has is what's preventing it from manifesting itself on those platforms.

  • by Achillez ( 314223 ) on Sunday February 21, 2010 @02:06PM (#31220060)

    I find it interesting that the title is why "Flash is fundamentally flawed on touchscreen devices" and not "Why Certain Touchscreen Devices (aka iPad) are limited and will not work with Flash". This is obviously an attack on the Flash framework as a way to redirect criticism away from the iPad. Apple has clearly mistepped here and now they are trying to do damage control. My understanding is that other touchscreen devices that are coming out in the market place will support Flash (e.g., HP Slate), and it will probably be seamless. I was quite interested in the iPad when the news came out but now that it won't support Flash, and locks users into the monopolistic "App Store" I am no longer interested. Only Apple would try something like this... they seem to be stuck in the monopolistic 90s.

  • by kiddailey ( 165202 ) on Sunday February 21, 2010 @02:31PM (#31220382) Homepage

    ... well, to some degree anyway.

    It does this by essentially transforming the mouseover event to a intermediate click event. For example, if you have a link that has a popup menu displayed on :hover, clicking the menu item will first show the popup menu. Clicking again follows the actual navigation. Although this doesn't address the issue of mystery-meat navigation and over events that are less obvious, it does seem to work well. I don't see why Flash couldn't do the same.

    To me, the issue with Flash is all about playback experience. Adobe can't even get the player to be efficient and smooth under OS X on decent hardware, so having it on my iPhone sounds tortuous.

  • by RzUpAnmsCwrds ( 262647 ) on Sunday February 21, 2010 @04:12PM (#31221402)

    RoughlyDrafted is nothing but an Apple apologist site. This is the same site that told us why we didn't want apps on the original iPhone (never mind that apps have now made the iPhone a huge success), how Android was doomed to fail (despite the fact that it's taken a significant share of the smartphone market in under two years), and how the iPad doesn't need HDMI (apparently a VGA output that does 1024x768 is a good substitute).

    To RoughlyDrafted, any problem with an Apple product is a problem with us, not with the product. No apps? We don't really want them. No HDMI? We didn't really need that anyway. No real multitasking? We didn't want that either because it opens the door to "viruses and spyware that run in the background".

    What a bunch of crap. Not even Mossberg is that bad.

A bug in the code is worth two in the documentation.