Silhouettes
Quick notes and thoughtsArchive for open source
Exploring a Mobile-Based Video Game Console
Ever since Atari and Pong became household names, video games have been a way to bring people together. Early generation game consoles used multiple controller connections to connect people playing games, but recently consoles with internet access have allowed people to interact across the world, and in much larger numbers. What has developed as a result of this is a new form of social networking where people can meet, though through avatars, and interact with each other. Of course, this type of networking is not exclusive to game consoles. Home computers with access to the internet can also run multiplayer games, while the internet itself contains countless web browser-based games. The problem with all of these examples is portability and often the skill level required to operate the games. No major console manufacturer can provide a system that allows users to play anywhere and with anybody. This is the problem that the mobile-based video game console sets its sights on.
Background
Every idea has predecessors and the mobile-based video game console is no different. The following contains several case studies of companies, systems, and concepts that will become building blocks for the console.
Build on the prior work of others (whose?) in the field? Address flaws in previous work (again, whose?) Develop infrastructure (instrumentation, methodology, collaborations) that will take science in exciting new directions?
Wii
Blyk
MegaPhone
Social Networking
Video games consol direction and development
Market (x# of cell phones vs. x# of consoles)
Independent game manufacturers
Methodology
Business model (FREE)
Three pillars (Application, Connectivity, and Analytics)
Develop infrastructure (outsource/partner with hardware, sales, marketing)
Collaborate/acquire MegaPhone
MegaPhone model
-a viewer sees the phone number on screen
-they call the number with any phone, and interact using their microphone and keypad their mobile carrier forwards us the call
-the MegaPhone server answers the call and processes the voice and keypress data
-the MegaPhone server sends the data over the internet
-the MegaPhone Flash game displays the updated state on the screen
-the MegaPhone mobile content server can send the caller SMS, MMS, or digital files
New model
-player chooses to play game and dials corresponding phone number from list
-mobile carrier forwards call to main server
-server processes voice and keypress data
-server sends data back to a receiver connected to the users personal tv
-This method differs from the MegaPhone model in that the server sends signals to multiple receivers rather than one main computer. The receivers could be set up to receive signals via internet or cellular phone.
Discussion
Pace of mobile phone feature development eliminates need to develop new controllers. Simply provide software updates for new technology added to phones (accelerometers, jog dials, touch screens, ect.)
-Potential uses for accelerometer enabled cell phones
-Tap accelerometer as a signaling device similar to voice input or button press
-Tip and turn phone for driving, water and snow sports
-Use the existing MegaPhone model
-Adapt to allow server signaling to multiple computers/receivers
-Use buttons for game play and voice data for talking with friends and other gamers
Design the Future/round 3
Another helpful insight from KP: custom molds. It’s possible that if each component of the phone is able to connect wirelessly with each other, then why not throw everything into a mold to create a custom enclosure? There are plenty of problems with this concept (toxicity, materiality, melting circuit boards, ect.), but if it could be made as easy as the Creepy Crawler Bug Maker then it could be an incredible selling point.
A good example of a custom blow-mold procedure was designed by DAG Design Lab. It includes customizable pin-walls that allow it to adjust to stuff like the weather. Check it out:
More thoughts for Design the Future
I recently had the chance to bounce some ideas off my good friend Kelly Peoples regarding the competition. She reinforced the idea of modularity and how the modules/parts could be easily re-entered back into the product stream after a period of use or upgrade. She also mentioned that a necessary software component would be to have some type of program-writer that allowed laymen to more fully customise their phone. I know something like that was been done before with things like Rhinoscripting with Grasshopper, but I haven’t been able to dig up anything substantial. If anyone has any further information feel free to drop a comment or two.
Initial ideation for Design the Future Competition
“What do you think mobile phones should look like in 2, 5, or 10 years?”
I’ve just started looking at the details for LG’s Desgin the Future competition and have started pulling ideas from various sources. My initial thoughts are to say something about the open source hardware/software revolution by proposing that the future of mobile phones depends on the open source community. An totally open source phone would also allow phone use in developing countries to explode. The current business model is for a few service providers to lock up all rights and software and prevent modifications to the operating system. While this may be practical for most of the western world, it discourages innovation where it is needed most. Every country has slightly different needs for cellular devices… Read the rest of this entry »
