<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>game development on QuickCharge Games</title>
    <link>https://quickchargegames.com/tags/game-development/</link>
    <description>Recent content in game development on QuickCharge Games</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>Copyright &amp;copy; 2012-2016 QuickCharge Games, All Rights Reserved</copyright>
    <lastBuildDate>Mon, 05 Dec 2016 00:00:00 +0000</lastBuildDate><atom:link href="https://quickchargegames.com/tags/game-development/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Choosing a Technology Stack</title>
      <link>https://quickchargegames.com/news/choosing-technology-stack/</link>
      <pubDate>Mon, 05 Dec 2016 00:00:00 +0000</pubDate>
      
      <guid>https://quickchargegames.com/news/choosing-technology-stack/</guid>
      <description>Not This Kind of Technology Stack  I always end up spending too long choosing what game engines and technologies I want to use to build my games. So much wasted time. Last time around I couldn&amp;rsquo;t find a single game engine that looked competently developed: I tried everything that was available at the time, and nothing really worked for me.
Hardly anything even supported Android, which was one of my desired targets, so I didn&amp;rsquo;t have a lot of choice.</description>
    </item>
    
  </channel>
</rss>
