title: Flash vs HTML5 game development for web & mobile
body: <p>I am an experienced AS3 programmer, and I've done Flash apps and games on the browser and on mobile (via Adobe AIR, e.g., on Android).</p>
  
  <p>I am about to start developing a game (basic 2D platformer with pixelart graphics. Think about Super Mario World) targeted to both web and mobile platforms. <strong>Thus I'm searching for easy deployment to these two kinds of platforms, having basically the same source code.</strong></p>
  
  <p>I'm divided between choosing ActionScript 3.0 (Flash) or HTML5/JavaScript for developing this game.</p>
  
  <p>My main question is, for those who've experienced the same situation before:</p>
  
  <h2>What is the safest way to go?</h2>
  
  <p>In other words, are there serious disadvantages with one of these frameworks that <strong>disallows</strong> me to develop multiplatform 2D games?</p>
  
  <p>Or am I just dreaming and practical multiplatform (web and mobile) game development is not so possible? (does someone know how Rovio did it with Angry Birds?)</p>
  
  <hr>
  
  <p>Here are some pros and cons that I already know:</p>
  
  <p>Pros for AS3/Flash:</p>
  
  <ul>
  <li><p>The state-of-art for web games.</p></li>
  <li><p>I'm experienced with it.</p></li>
  <li><p>(Almost) concealed source code.</p></li>
  <li><p>On the web, it's browser-independent.</p></li>
  <li><p>Can run as a "native" app on iOS and Android through Adobe AIR. It's not the best performance experience ever, but I know that you can get <em>playable</em> performances with it.</p></li>
  </ul>
  
  <p>Cons for AS3/ Flash:</p>
  
  <ul>
  <li><p>Performance on AIR for mobile is not optimal, so I might end up having to abandon a really cool but expensive feature (or even several features).</p></li>
  <li><p>People are saying HTML5/Javascript will substitute it.</p></li>
  </ul>
  
  <p>Pros for HTML5/Javascript:</p>
  
  <ul>
  <li><p>It's possible to do Flash-quality games using, e.g., engines like <a href="http://www.impactjs.com">ImpactJS</a> or Akihabara.</p></li>
  <li><p>Seems to be more stable and well supported on mobile in the future.</p></li>
  <li><p>Deployment as native app is possible through <a href="http://www.phonegap.com/">PhoneGap</a>, appMobi, etc.</p></li>
  </ul>
  
  <p>Cons for HTML5/Javascript:</p>
  
  <ul>
  <li><p>I have some basic knowledge of this technology.</p></li>
  <li><p>Source code is wide open exposed.</p></li>
  <li><p>Performance/behaviour is browser-dependent.</p></li>
  <li><p>Lacks a solid framework or engine which is free of co$t$.</p></li>
  </ul>