Frisky Friday Poll-o-Rama

Fri, Jan 29, 2010

Frisky Misc

It is with great excitement that I introduce the inaugural edition of the Frisky Friday Gamer Poll…

You game?
Fingers crossed you fine folks won’t let us down, each Friday we’ll survey the smartest social, mobile and casual gamers we know – you! We’ll dish up a selection of the hottest current games in each of three categories (social, mobile and casual) and all you (dear Frisky Mongoose readers) have to do is pick your favorites! Three easy clicks to make your voice heard – couldn’t be simpler. Please note: You can only pick one game in each category, even if you play and love them all (sorry!)

Speak up!
If you don’t see your favorite titles on the list this week, let us know what they are. Or if there’s a question/topic you’d like to see on the next Frisky Friday docket, let us know that too! Just leave a comment or drop us a line at friskymongoose (at) triplepointpr (dot) com

And the winner is…
After all your votes have been cast we’ll reveal the weekly winners and losers each Monday, based on friskiest opinion. Polls close on Sunday night. There may even be something special at stake for lucky voters in upcoming Frisky Friday Polls – keep casting your ballots each week to find out!

So without further ado, welcome to the Frisky democracy, Mongeese… In Facebook and Apple we trust! Go cast your vote in the first Frisky Friday Gamer Poll now!

Be Sociable, Share!

Related posts:

  1. FIRST! Frisky Friday Gamer Poll for January 29, 2010
  2. Spin the Wheel in Prize-O-Rama – A Frisky Hands-On
  3. Frisky FarmVille Photo Grab Competition: Round 1, Vote!
  4. Black Friday at Mafia Wars: Three New Items and a Sale
  5. Must-Have Mobile Game Candidates Close-Up & Reminder: Weekend Poll Closes Tonight
, , , , , ,

This post was written by:

- who has written 1010 posts on Frisky Mongoose.


Contact the author


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