Hear From A Panel Of Virtual Worlds Entrepreneurs

September 30, 2010

On September 24th, FountainBlue held its annual virtual worlds conference.  This year’s event was hosted on Cisco’s campus in Milpitas, CA.  In the afternoon, a panel of virtual worlds entrepreneurs spoke about new developments in the industry.  The panel was titled “Entrepreneur Panel: The Tools, The Goods, The Immersion Experience”:

  1. Facilitator Nina Gerwin, The NRG Group
  2. Michael Gold, CEO, Electrotank: virtual world & virtual games development platform
  3. Steve Hoffman, CEO, Rocketon: virtual world for tweeners
  4. Albert Kim, CEO, Zenitum: Augmented reality with 3D displays
  5. Jim Parker, President, Digitell: SaaS 3D immersive virtual events and virtual training

I covered some of these entrepreneurs’ businesses in a separate posting about virtual worlds technologies to watch.

Adapting your business

Each panelist was asked to describe the genesis behind their business.  As is customary with web startups today, no one is working against their original business model or vision.

For Digitell’s Jim Parker, business began by assembling content for online libraries.  Then, he was struck by the notion of allowing consumers of the library content to meet and collaborate in real-time.

Zenitum’s Albert Kim experiments with a number of different technologies.  When one set of technologies differs enough from the core set, he looks to spin that out into an independent company.

Online gaming

Online and social gaming may be the hottest trend on the web today.  So of course the topic arose with Electrotank’s Michael Gold and RocketOn’s Steve Hoffman.  Gold and Hoffman highlighted technologies available to game makers today:

  1. Flash
  2. HTML5
  3. Objective C
  4. Unity

Note: Unity’s David Helgason spoke on the Trends Panel at this event.

According to Gold, HTML5 has its benefits, but you can’t yet develop a game using it.

Note: Michael Gold posted the following clarification:

“I just want to make a quick correction on a statement about HTML5 that was attributed to me in this blog post. What I said on the panel was that HTML5 is not yet practical for developing *virtual worlds* but has great potential in a few years.

Virtual worlds and MMOs present unique technical challenges that are distinctly different than those presented by the majority of social and casual online and mobile *games* Thus in my opinion it is completely possible to develop *games* using HTML5 at the present time. There are several developers focusing on these games right now. In fact, Zynga recently purchased one – Dextrose, a German development studio. I actually believe you’ll see a significant number of HTML5 games on the market a year from now. Just not so many virtual worlds or MMOs.”

Virtual worlds and engagement

An audience member asked how virtual worlds can track engagement – so that in a corporate setting, the meeting host can measure whether the content is hitting the mark.  Digitell’s Parker notes his clients often use his system for accreditation.  The system uses an idle timer – it renders a “click to continue” message and if the user does not click within 10 seconds, “you don’t get accreditation.”

Studies have shown that viewers of webinars often lose attention and multitask.  A virtual world forces users to remain engaged.  Parker notes that for some sessions, the instructor leads the “students” on a guided walk.  “If Jim doesn’t follow the rest of the group, then you know he’s not paying attention.”

Conclusion

Believe it or not, it’s not a bad time to be a virtual worlds entrepreneur.  As the panel demonstrated, the key is to be nimble and adapt to a changing marketplace.  Next year, it will be interesting to see how these entrepreneurs evolved – and, to see what new entrepreneurs appear on the scene.


How Vendors Should Evolve Their Virtual Event Platforms

July 10, 2010

The following is a collaborative posting by Miguel Arias, Steve Gogolak and Dennis Shiao.

Content creation and collaboration was facilitated by a PBworks wiki – the wiki page can be found here: http://allvirtual.pbworks.com/How-Vendors-Should-Evolve-Their-Virtual-Event-Platforms

To evolve their platforms for enhanced experiences and broader adoption, virtual event platforms should consider the following:

Make it easier to experience

Most virtual event platforms are easy to use – on a first-time visit, users tend to grasp the overall user experience and can figure out where to go (and how).  That being said, for wide scale adoption, virtual events needs to be as easy as Facebook.  That is, our grandmothers need to be able to access the site and figure things out.  On Facebook, grandmothers can update their profile, read their “friends” posts and write updates to their Walls.  Can a grandmother login to a virtual event, update her profile and participate in a group chat?  We’re not so sure.  Similarly, navigation and interactions need to be easier.  Most virtual events are intuitive to navigate (e.g. Lobby, Auditorium,  Lounge, etc.) – but may not be so intuitive with regard to message boards, chat, blogging, rating, etc.

Along with a simplification of interfaces and the use of usability and navigation conventions, many customers and users seem to be demanding more immersive environments. While presenting a brand and hosting an interactive experience in a convention centre, it seems an interesting field to add some real-time rendered environments using engines like papervision3D or Unity3D. This said, it is unlikely that avatar-based real time rendered environments will make it to a mainstream audience. Key considerations (or obstacles) are plugins or applets downloads, system performance and learning curve barriers.

Make it easier to find

The typical “location” of a virtual event is quickly becoming outdated – microsite with registration page, with no ability to experience the event prior to completing all mandatory registration fields. The registration page serves as a “wall” not only to potential attendees, but to search engines as well.  Virtual event platforms need to move “outside the wall” and expose their technology on Facebook, on blogs and on publisher web sites.  Platforms should widen their distribution via widgets, embed code and application programming interfaces (API’s).  Facebook is not limited to Facebook.com – it has Facebook Connect, Facebook Open Graph and much more.  Virtual events platforms, on the other hand, seem to be restricted to “VirtualEventPlatform.com”

Make it easier to access

The most relevant virtual event platforms will introduce, or already have, Facebook Connect and Twitter API, and they will need to move to even wider standards like OpenID.  For public events, ease of registration is a must.  Using open methods for registering and/or connecting social networks have three-fold benefits:

  1. Registration is faster because basic information can be provided by services like LinkedIn, Facebook, etc.  Shorter registration forms increase completion, period.
  2. Intelligence gathered by the platform about the user’s existing social graph can enhance the experience within the event by automatically creating connections with other attendees based on that user’s connection outside the platform.  This will lead to more networking and awareness of actual people within the environment.
  3. Users opting into connections at the point of registration allows platforms to create publishable actions that can be spit out to twitter and facebook news feeds that can increase viral awareness of the event.  Marketing automation at its best.

On the other hand, desktop or mobile widgets to control your stand usage, statistics and reporting will be a must. Lastly, the platforms will have extensive APIs to manage their integration with various social networks, corporate databases, physical event managing software, etc.

Make the experience available on more devices

Most virtual event platforms support Windows, Mac and Linux.  They need to support more platforms, especially mobile.  On the mobile front, it’s important to consider iPhone/iPad, Android, BlackBerry, Symbian, Windows 7 Phone and WebOS (listed in our order of importance).  To start, we don’t believe the entire virrual event experience needs to be “ported” to mobile devices -rather, vendors should determine the most critical features for attendees and exhibitors – and prioritize based on importance.  For instance, chat is an important element of virtual events, so why not make a mobile app that allows exhibitors to staff their booth via their smartphone.

The entire 3D environment does not need to be supported on a mobile device, but the networking tools (visit card managing, real time conversation, etc) and the reporting tools certainly do. On the other hand, it will be interesting to see what happens with Flash and Apple, and see which vendors will try to develop their platforms using HTML5.

One of the key areas where mobile can play a huge role is the “reminder” needs that come from tons of scheduled activities within virtual events.  If attendees have the ability to build out a personalized agenda before the event and opt-in to either SMS reminders or download some kind of app that will push notifications at them throughout the day, it would be much easier to create a flexible agenda.  Currently we’re cramming so much into the shortest amount of time because we’re afraid of losing people.  If only we had better planning and reminding tools, driven by devices that never leave our pocket!

Make the platform more adaptable and flexible

Related to our point about mobile support, platform vendors have important decisions to make regarding the development platforms.  Virtual event platforms today are based on Flash, Flex, Silverlight, Java and JavaFX.  Are those the “right” platform technologies for the future – or, should platforms move in the direction of HTML5?  Does a combination off HTML5, Javascript and Ajax create a more adaptable and flexible platform?  What do we “lose” by shifting away from Flash, Silverlight, etc.?  And what are the mobile implications with the chosen direction?  All good questions for the platform vendors to consider.

Make the platform more adaptable for different customer needs and different usage

There are so many different kind of virtual events: trade shows, conferences, job fairs, corporate events, webinars, congresses… that vendors should decide in which market niche they are going to play. We will see generic platforms and other vendors delivering a tailored solution for one or many of the previous choices. It will become more and more complex to provide physical event managers with the features they need to handle their hybrid events at the same time as the platform is able to cope with the extensive data handling of the virtual job fair, or the networking tools of a professional tradeshow.

Take a hint from Apple and FaceTime

Video chat will, without a doubt, increase the effectiveness of networking.  It is the one key element that can be introduced that will get critics to come around to the idea that networking in an online environment can be as effective as the cocktail hour of a physical event.

Tweet this posting:


Let’s Collaborate On: Evolution Of Virtual Event Platforms

June 21, 2010

Let’s collaborate on how virtual event platforms (and their associated experiences) should evolve.  I’ve set up a wiki on PBworks that will allow all of you to chime in with your thoughts.  Here’s the link to the wiki – I invite you all in, to add your thoughts and make edits:

Be part of a collaborative blog posting

http://allvirtual.pbworks.com/How-Vendors-Should-Evolve-Their-Virtual-Event-Platforms

To edit the wiki page, you’ll need to register for a free account with PBworks.  Suggested ways to participate:

  1. Edit any of the existing material
  2. Add new paragraphs or sections
  3. Delete existing material (although I’d rather you re-write existing material than delete it outright)

Below, I’ve posted the current text of the wiki page.  If you have thoughts on this topic, be sure to visit the wiki and chime in! Based on the amount of activity this week, I may choose the publish the final version of this post here on this blog.  All contributors will be acknowledged.  If you do not wish acknolwedgement, simply skip the inclusion of your name in the list (bel0w).

Lastly, if you’d like to contribute, but would rather not use a wiki, leave a comment below and I’ll apply your comment(s) to the wiki (with proper acknowledgement).

Initial Draft – Visit the wiki to add your thoughts

To evolve their platforms for enhanced experiences and broader adoption, virtual event platforms should consider the following:

Make it easier to experience

Most virtual event platforms are easy to use – on a first-time visit, users tend to grasp the overall user experience and can figure out where to go (and how).  That being said, for wide scale adoption, virtual events needs to be as easy as Facebook.  That is, our grandmothers need to be able to access the site and figure things out.  On Facebook, grandmothers can update their profile, read their “friends” posts and write updates to their Walls.  Can a grandmother login to a virtual event, update her profile and participate in a group chat?  We’re not so sure.  Similarly, navigation and interactions need to be easier.  Most virtual events are intuitive to navigate (e.g. Lobby, Auditorium,  Lounge, etc.) – but may not be so intuitive with regard to message boards, chat, blogging, rating, etc.

Make it easier to find

The typical “location” of a virtual event is quickly becomin outdated – microsite with registration page, with no ability to experience the event prior to completing all mandatory registration fields. The registration page serves as a “wall” not only to potential attendees, but to search engines as well.  Virtual event platforms need to move “outside the wall” and expose their technology on Facebook, on blogs and on publisher web sites.  Platforms should widen their distribution via widgets, embed code and application programming interfaces (API’s).  Facebook is not limited to Facebook.com – it has Facebook Connect, Facebook Open Graph and much more.  Virtual events platforms, on the other hand, seem to be restricted to “VirtualEventPlatform.com”

Make the experience available on more devices

Most virtual event platforms support Windows, Mac and Linux.  They need to support more platforms, especially mobile.  On the mobile front, it’s important to consider iPhone/iPad, Android, BlackBerry, Symbian, Windows 7 Phone and WebOS (listed in our order of importance).  To start, we don’t believe the entire virrual event experience needs to be “ported” to mobile devices -rather, vendors should determine the most critical features for attendees and exhibitors – and prioritize based on importance.  For instance, chat is an important element of virtual events, so why not make a mobile app that allows exhibitors to staff their booth via their smartphone.

Make the platform more adaptable and flexible

Related to our point about mobile support, platform vendors have important decisions to make regarding the development platforms.  Virtual event platforms today are based on Flash, Silverlight, Java and JavaFX.  Are those the “right” platform technologies for the future – or, should platforms move in the direction of HTML5?  Does a combination off HTML5, Javascript and Ajax create a more adaptable and flexible platform?  What do we “lose” by shifting away from Flash, Silverlight, etc.?  And what are the mobile implications with the chosen direction?  All good questions for the platform vendors to consider.

This article was developed collaboratively via PBworks.  Contributors to this article include:

  1. Dennis Shiao, Blogger at “It’s All Virtual”
  2. <YOUR NAME HERE>

Tweet this posting:


%d bloggers like this: