Corona Geek #76 – Flappy Bird, Why Was It Successful, Why Was It Removed

Corona Geek Hangout
Share on Facebook0Share on Google+1Tweet about this on TwitterShare on LinkedIn1

Corona GeekDuring this week’s Corona Geek Hangout we discussed the viral success and ultimate demise of Flappy Bird with Goofo Escape game developer Dario Sangiovanni. Dario and the rest of the developer panel shared many insights into what it takes to make a successful mobile game.

Also mentioned was:

Thank you for listening to and following Corona Geek:

Need to market your app? Sign up for a PreApps developer account and use the promo code “CoronaLabs” at checkout to try their PreApps Featured Feedback app posting free for 30 days. Hurry, offer ends February 28th, 2014.

Share on Facebook0Share on Google+1Tweet about this on TwitterShare on LinkedIn1
Charles McKeever

Charles McKeever is a life long computer geek who enjoys exploring technologies to understand how they work, how they can be smashed together, and how they can be used to fuel entrepreneurial endeavors.

This entry has 3 replies

  1. You guys all missed the point with Flappy Birds. I wish I was in this conversation. Why? This is ironically happening to me right now with two of my apps. It’s stress related! Dealing with lawyers, and Nintendo!

  2. Good observation Nick. It’s very easy to comment from the stand, but I’m sure the developer feels/felt a very real element of stress that just wasn’t desired. Some people would just say, “oh well” and keep moving forward. But, not everyone is built that way. Hope your dealings go smoothly.

  3. develephant says:

    @Nick – Actually, Nintendo stated that they had nothing to do with the removal. I’m sorry to hear you’re having some issues with them. Good luck.

    http://toucharcade.com/2014/02/10/nintendo-didnt-remove-of-flappy-bird/

    Best

Leave a reply

You may use these HTML tags and attributes: <a href="" title="" rel=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>