What Was The First Third-Party Nintendo Console Game Ever?

By Ishaan . October 6, 2010 . 8:18pm


In the latest Iwata Asks column, conducted with Masayuki Uemura and Hiroshi Imanishi, Nintendo president, Satoru Iwata, delves into the development of the Famicom in 1983. At the time, Uemura was in charge of developing Nintendo hardware while Imanishi headed the the General Affairs Department, which was responsible for providing auxiliary support.


The talk with the two developers is rather long, so here’s a few bullet points to give you an idea of the kind of content you can expect to find:


  • Since the Famicom used a processing component called “6502” that wasn’t widely used or understood by programmers, Nintendo developed the majority of games for the Famicom themselves. In fact, they considered the complex nature of the CPU an asset as it allowed them to be the only company developing Famicom software.

  • Shortly after its release, however, an engineer at Namco was counted amongst the first game developers to recognize the Famicom’s CPU outside of Nintendo.

  • The first third-party-developed Famicom peripheral was created in collaboration with Hudson. It was titled Family BASIC and was composed of a cartridge and keyboard for creating game using the BASIC programming language.

  • Unsurprisingly, one of the very first third-party games for the Famicom was created by Namco in 1984. It was called Galaxian (pictured above) and was based on its arcade counterpart, released in 1979. Namco followed it up with Xevious, also based on its original arcade version released in 1983.

  • Random tidbit: Recently, Iwata cited Xevious as being the game that convinced Nintendo to re-release classic games touched up with a stereoscopic 3D effect on the Nintendo 3DS.

  • Ultimately, third-party developers resorted to manufacturing their own Famicom cartridges to develop software for the machine, as a licensing model didn’t exist at the time. As the number of faulty cartridges grew, Nintendo established their first ever licensee system whereby they would manufacture the cartridges.

  • Problems weren’t restricted just to cartridges, however. The Famicom itself suffered from a number of problems including the tendency to heat up quickly and render quick-moving sprites invisible. The square buttons on the controller would also get stuck.

  • This was despite a one-million-punch test Nintendo put the controllers through before manufacturing them. However, this made no difference whatsoever and the company’s repair service was soon flooded with complaints. The buttons were later made circular to deal with the issue.

Read more stories about & & & & & on Siliconera.

  • Code

    hooray, facts! It’s funny, I’ve often wondered what the first 3rd party game on the NES was actually!

  • Overheating? Man I thought Nintendo consoles were problem-free and that ovetheating was something xbox only.

    • Tom_Phoenix

      To be fair, the NES/Famicom was Nintendo’s first console and this was in the days when there was practically nothing to base the design on. They had to think of everything from scratch, so it’s little wonder that it had problems.

      Fortunately, Nintendo has always been a quick learner, so they have been doing a preety good job since then.

  • WonderSteve

    Ah all these “Iwata Asks” are interesting. It sometimes shows you how “protective” Nintendo are in the old days.

    By the way, can someone also please ask Iwata when we are getting Xenoblade and The Last Story?

  • cmurph666

    I still have my Galaga: Demons of Death cartridge for the NES. Man, did it suck.

    It was also released by Bandai.

  • Icon

    It’s funny reading this and picturing Nintendo, at least at one point in time, as being pretty amateur at the video game business. Funnier still is that only a few years later they would dominate the gaming world and define the hobby for so many people. These days you can’t say that only the Wii = games, or only the PS3 or the 360. But many moons ago, all you had to say was “Nintendo,” and everyone knew what you meant.

  • The 6502, complex? Tish. I’ve written code for that chip and it’s really not bad at all. I taught myself 6502 programming on the C64 using only a reference guide, back in the days before the internet!

Video game stories from other sites on the web. These links leave Siliconera.

Siliconera Tests
Siliconera Videos