3 ms·
So there are two arguments in this article. The first is that Flash makes development and bug fixing harder because you rely on someone who is a Flash expert to
by dougmccune 17y ago
So there are two arguments in this article. The first is that Flash makes development and bug fixing harder because you rely on someone who is a Flash expert to fix any bugs, and from anecdotal experience the author was working on a team with no Flash programmers, so that was then a bottleneck. Part of his argument then is that if you want a rich application on the iPhone you can just make an iPhone application. Yet that has the exact same problem if you don't have good iPhone developers in house. The argument of "this technology is hard when you don't have programmers that know it" seems pretty ridiculous and would even apply if I wanted to write HTML apps but my team only knew Fortran.
The second argument is that Flash apps don't scale well to different resolutions. As a Flash developer I think this is simply false. There's no basis for the argument, you can make Flash apps scale in whatever way you want, and you have completely control over nice fluid layouts (at least with Flex you do, but you can do a lot with non-Flex Flash too).
If part of the argument is really that you don't want to have to develop different versions of your app for different devices (in this case he worries about resolution), then Flash is a clear winner, since that will let you develop the same codebase that can be used across any Android/RIM/non-iPhone phone. Sure, you'll have to rework parts of the UI to accommodate different screen sizes, but that's just a part of mobile development. Anyone who thinks you can design a mobile app for very different devices with different resolutions without reworking the main UI is simply naive, regardless of technology choice.
- ram1024 17y agopretty much what i was thinking. the position that flash is unviable on a mobile device is just untenable. sure not all web-flash applications will work without tweaking simply because the usage cases are different, but that does not invalidate the platform in the slightest
- mortenjorck 17y agoIt is indeed a rather contorted argument. I think a much better case is made by Daniel Dilger at RoughlyDrafted: http://www.roughlydrafted.com/2010/02/20/an-adobe-flash-developer-on-why-the-ipad-cant-use-flash/ http://www.roughlydrafted.com/2010/02/20/an-adobe-flash-deve... . His contention is that Flash's mouse-heavy interaction model and the iPad's (and the iPhone's) touch model are too fundamentally different for a majority of the content to work, which I'm surprised more people haven't been talking about.