Flash vs. Silverlight

Question

We are building a training website where we need to track viewers watching videos and store detailed info about the viewing (when they paused, if they watched the whole video etc)

What should we consider when deciding between the two technologies?

I forgot to add. This is for an in house app. We have complete control over the environment. If it this was for a public application I would definitely go with Flash.

I'm just looking for technical advantages of one over the other from someone who has used both.

Answer 1

Pls find some additional info here:

http://stackoverflow.com/questions/20910/silverlight-vs-flex

Answer 2

Flash is more widely use but SilverLight got good press during the Olympic. Can't you have both to have the more user. Because if you stop just with SilverLight you might cut all user that doesn't bother to install the needed file.

Answer 3

I'd personally use Flash due to installed base. The way I see it, if YouTube and Google Video are using Flash than just about every computer on earth has it so it wins hands down.

Answer 4

I have yet to find a silverlight video that works properly in firefox. As far as I know there is also no linux viewer.

Also there are more users out there that have flash already installed so not having to install another app to watch a video will have more people watch the video

Answer 5

Both can fulfill all of your requirements, so go with the one with the higher install base - which is, hands down, Flash.

Answer 6

If you need stats to support a decision for Flash, you can grab it's install stats here: http://www.adobe.com/products/player_census/flashplayer/version_penetration.html

About 97% install rate. That's pretty sweet.

Answer 7

having had to make the call between silverlight and flash recently for a very intense interactive component, i had to go with flash. and for one reason: online support. If i have a problem building something in flash, chances are pretty good that I'll find help somewhere online from someone thats overcome the same issue. And with Silverlight being new and still fresh from beta iterations, finding that same volume of help is unlikely (at least right now.) In the end, my Flash app was pretty complicated and I still had quite a few issues that I was unable to find help for and just had to dig through api's and try a few things out. Had I gone with Silverlight instead, I would have been desperately idle. dont get me wrong, i'm dying to jump into silverlight and I'd love to convert my flash app to SL someday. I just need the online community/forum presence to grow. And it will. I'm excited to see where Silverlight will go.

Answer 8

If you are looking for maintainablility, its silverlight, their programming api, is way cleaner.

But, its not only not installed everywhere, its not supported by every browser or client OS.

If you can, do it in both, but if you can't, do it in flash , and port it when you get a chance after the install base is larger, since silverlight is easier engineering wise.

Answer 9

i found this blog (not mine!) very interesting on the subject. personally i would adopt a solution based on needs, if i was building say a internal app for a company on a windows network, then silverlight seems great. Otherwise, it seems you leave out the entire rest of the world by going with silverlight on a public site.

I'm all for competition and both are still proprietary products. Although the flex3 compiler and framework have been released open source the actual flash player is still proprietary. That said almost every computer online has some form of the flash player, though it might not be the needed version 9 for flex apps, it can easily be upgraded through a simple click in the browser.

Answer 10

It does matter how many concurrent queries you're awaiting. This was also the decision-base for the Olympics-Website, because a lot more server-ressources are needed to deliver videos via flash instead of silverlight. So silverlight might be cost-saving.

Answer 11

Flash because I don't trust Microsoft to be interoperable

Answer 12

What do your developers know? If they already know ActionScript then use Flash, if they know C#, VB.NET, JavaScript, Ruby, or Python then use Silverlight.

Answer 13

Sounds like you have got complete control over the environement So it is better to choose Silverlight because of the ease of development and extensibility features of this new technology. It supports the best scripting language(C#, the most matured language ever). I bet the investment you can make on this new technology wont depress you in the future.

Answer 14

There is a valuable blog where the author compares Silverlight and Flash from a developer and end-user point of view.

Both Silverlight and Flash running the same use cases are shown, the code can be downloaded and the users can up/down about the best one.

I consider this site as a great Silverlight vs Flash resource.

http://www.shinedraw.com/

Answer 15

Silverlight is actually closing in in flash, and functionality flash just recently got is rapidly being implemented in silverlight, but there's still a lot more users with flash than with silverlight, so you'll reach out to more with flash.

here's statistics of how many % of users have them installed.

http://riastats.com/#

as you can see, flash is far ahead

Answer 16

I've gotta say silverlight has a much better API and with the .NET it's got a huge benefit

Answer 17

If you have full control of environment, consider WPF/Web Browser Application. Compared to Silverlight, development is a bit easier and learning curve for typical .NET developers is practically flat.

Answer 18

I'll chime in because it seems people missed the point of the question: What are the technical advantages of Flash vs Silverlight? (as it pertains to an in-house app)

Flash Pros

• The "artistic" interface is much better, in my opinion. If you have artists and designers that are used to using Illustrator or Photoshop, this is pretty straight forward.
• The way their environment integrates frame-based movie timelines is pretty slick and has been for years. It makes it very easy to integrate and layer many different animated elements and sounds into your movie or animation.
• All coding is done in the JavaScript-esque language ActionScript, so the learning curve for the syntax at least is pretty low for non-microsoft developers.
• Online support. There are years and years worth of posts that can help you figure out what you need to do to get what you want in Flash.

Silverlight Pros

• It uses .Net as a back end. If you have a lot of .Net developers, you'll be able to leverage the .Net framework which is a much more powerful set of tools, programmatically speaking.
• Easier to debug. In my experience it's easier to debug than Actionscript, largely due to the superior IDE.
• Bringing me to the IDE. The coding IDE is vastly superior to Flash's clunky, cobbled together, fancified textpad. It has intellisense, auto-complete, etc.

Flash Cons

• In my extensive Flash experience, If you're making a highly interactive app, it can be buggy as all get out. Some of the bugs bordering on nonsense, the work arounds being hackish at best.
• The IDE sucks. Period. It's notepad with some poorly implemented intellisense-esque keyword identification.
• The language falls on it's face at times. I've seen instances where all of a sudden a var got all type-sensitive on me, where it wasn't just two stanzas prior. My fault? Maybe. Probably. But nonetheless I've seen some weird behavior from ActionScript, whereas C# has always done what I've told it to.
• No real standard way of doing things. No "best-practice put your code here" way to do things. Flash lets you put code on anything. A frame, a MovieClip, an object, an array... sure whatever, just pop some functions on some stuff and party! This makes finding bugs in someone else's app a real chore.

Silverlight Cons

• Not a lot of documentation yet, in my opinion.
• Substandard "artist" interface by comparision. If you're going for a certain look, it may be harder for your designer to acheive.
• If you're not used to XAML, layouts can be a real pain in the butt. If you've never used XAML, and you've got a sort timeline to get this thing done, you best be prepared to put in some extra time, or be okay with a less than stellar look and feel. It's not quite as easy to get the look that you want with XAML as it is in Flash.

Again, all of this is in my own opinion and from my experiences. Other people may have different opinions.

If you have a few designers and some Flash experience, go with flash. If you want to learn something new, pad your resume, and you've got nothing but .Net experience, go with Silverlight.

In the end, do whatever it is that makes you like coming to work. (as long as it meets your deadlines. lol)

Oh, and I should note, I wasn't talking about FLEX here, but Flash.