The DSi XL: From Social Networking Site to Sandwiches

Tue, Mar 23, 2010

Casual, Console

“What would you like 93% bigger?” These seemingly inappropriate words actually come from a Facebook application launched by Nintendo to create some hype around the Nintendo DSi XL, the newest version of the DSi. This entertaining app features the DSi XL among a random assortment of options one might consider enlarging (having always felt that I should’ve been born in the 80′s, I chose hair). Not only that, Nintendo has also sent two outrageously large sandwiches to the AOL offices of New York to get more buzz.

The Nintendo DSi XL, the 4th version of the DS to date, is due to be in North American stores on March 28th. Boasting a screen 93% larger than the DSi, the XL gives gamers an easier time seeing the visuals without having to sacrifice much of the quality of the graphics. It is officially priced at $189.99 (which is a price I’d be willing to pay so that my mom can fully enjoy Cooking Mama without having to strain her eyes).

Be Sociable, Share!

Related posts:

  1. Nintendo Adds Classic Literature to the Nintendo DSi XL’s Future Lineup
  2. Is Pairing a DSi XL and America’s Test Kitchen a Recipe for Success?
  3. New DSi XL Colors, Price Drops in Japan & U.K.
  4. McDonald’s Japan Trains Employees Using DSi
  5. Midnight Blue DSi XL Available in North America this July
, , ,

This post was written by:

- who has written 25 posts on Frisky Mongoose.

Camille is a Contributing Editor at Frisky Mongoose focusing on the casual side of the gaming world.

Contact the author

  • Brian Rojas

    I definitely look forward to trying out the DSi XL.

  • http://www.friskymongoose.com/ Kate Hancock

    And what about the 3DS? We'll have more on it tomorrow – what do you
    want to know?

  • http://www.r4dskarte.com/ R4 karte ds

    3DS is more promissing!!


Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0