<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/plusone.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar.g?targetBlogID\x3d18703586\x26blogName\x3dVideo+Game+Marketing\x26publishMode\x3dPUBLISH_MODE_BLOGSPOT\x26navbarType\x3dBLUE\x26layoutType\x3dCLASSIC\x26searchRoot\x3dhttp://vgsmart.blogspot.com/search\x26blogLocale\x3den_US\x26v\x3d2\x26homepageUrl\x3dhttp://vgsmart.blogspot.com/\x26vt\x3d1313292277018552030', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>

Video Game Marketing

Indie Game Marketing from the author of the Game Marketing book, The Indie Developer's Guide to Selling Games. Video Game Marketing made simple... or at least as simple as I can make it.

My Photo
Name:
Location: Philomath, Oregon, United States

As you can see on the left: I am a professional juggler. The rest you can learn from this Blog.

Tuesday, May 23, 2006

Intro and Exit

I was reviewing a client of mine when I brought up a point that I kinda of brush on in my book. In hindsight I should have emphasized this more in the book- its there, but it is a little obscure. In my book I talk about, in a demo, where you have chances to 'sell' your game. Two of those listed are when the game starts and when the person exits.

And now I change tracks for a moment. My speech and debate teacher, in highschool, was a jerk... but he was good at speech and debate. One of the lessons he taught was the way to effectively get an idea across is to first, tell them what you are going to say, then tell them what you came to tell them, and finally tell them what you just said.

A demo is kinda the same way. When it comes to a product with two nag screens, one on entry and one on exit, you want the two nag screens to be DIFFERENT.

The first nag screen should tell them what they are about to play and experience. The game will let them experienced, and the final nag screen should tell them A) what a good time they just had and B) What they were missing out on.

The final nag screen is a closer, but your FIRST nag screen shouldn't be the same message. Otherwise you have the equivolent of walking into a store and having the sales clerk say "So, this is the one you want" before you even tell him what you're looking for. Your opening nag screen should pitch them all the glory of the demo. The closing nag screen should pitch them all the glory of the final version.

This is just a rule of thumb for most products- it may not be true for every product. Nag screen contents should vary based on audience and complexity of your game.

And since my mother has informed me she is reading my blog as a second religion now- You could always just take her voice and record it as your intro or exit, there's no greater nag in the world than my ma.

I'll just stand here and wait for the phone to ring. A count to 10 should be enough ....

0 Comments:

Post a Comment

<< Home