Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

2011 dmo mojo gruber

6,237 views

Published on

Presentation on how to develop a successful mobile strategy for travel companies. Presented at DMO Mojo event in New Orleans on March 3, 2011.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

2011 dmo mojo gruber

  1. 1. 5 Steps to a Successful Mobile Strategy in Travel<br />Glenn Gruber<br />AVP, Travel Technologies<br />Ness Software Product Labs<br />
  2. 2. Poll<br />Who already has a<br /> Mobile-optimized Web Site<br /> Mobile App<br />
  3. 3. Mobile is Not a “Nice to Have”<br />
  4. 4. Mobile is Not a “Nice to Have”<br />
  5. 5. Mobile Devices at the Center of Traveler Interactions<br />Mobile is for when you’re not at home<br />Always-on, always-available communications channel<br />The Local Resource Guide: What can I do and when can I do it?<br />Reminders<br />Mobile is social<br />
  6. 6. 5 Steps to Success<br />
  7. 7. Step 1: Determine Use Cases<br />Understand what role mobile plays within the traveler lifecycle, how it supports, extends other channels<br />What are the gaps in current communication, interaction channels?<br />What changes in behavior do you want to achieve?<br />Complex decisions v. Spur of the moment<br />Social, Location-based Services<br />Do not lose sight of your Brand<br />
  8. 8. Step 1: But Don’t Lose Sight of Your Brand<br />Source: Forrester Research<br />
  9. 9. Mobile Application Development Challenges<br />Hardware diversity<br />Screen Parameters, Keyboard features<br />Memory<br />Processing power etc<br />Software diversity<br />Platforms<br />User preferences<br />Environment<br />Deployment Infrastructure<br />Carrier Restrictions<br />Difficulty to “write once and run any where”<br />9<br />
  10. 10. Step 2: Prioritize Platform/Device Support<br />Ever increasing number, ever expanding definition of mobile devices, and operating systems <br />Do you know what your customers are most-likely using?<br />
  11. 11. Step 3: Evaluate Technology Options/Process<br />App-centric v. Mobile Web-centric<br />Consider which device capabilities will be leveraged<br />Optimized for Smartphone specifically, or “Write Once Run Anywhere?”<br />Flash v. HTML5<br />Leverage proprietary development platform or industry standards? <br />
  12. 12. So, where do you start?<br />Mobile Web<br />Mobile App<br />
  13. 13. Mobile Web<br />Pros<br />35% of mobile subs use browser<br />Search discoverability<br />Cross-device support<br />Cons<br />Latency<br />Loss of screen real estate<br />Not all browsers created equal<br />Best Practices<br />Browser re-direct to m.domain.com or .mobi<br />Provide mobile appropriate content<br />Design with mobile users in mind<br />Use tools that optimize by platform<br />
  14. 14. Mobile Apps<br />Pros<br />More than 60 apps downloaded for every Apple device sold<br />Robust user experience<br />Fully leverage native device<br />Placement on device<br />Cons<br />Cost & resources to develop for multiple platforms<br />Best Practices<br />Don’t rely on AppStores<br />Provide true utility <br />Android is just as important as Apple<br />
  15. 15. Mobile = Location<br />
  16. 16. Run mobile development like a product, not a project<br />Develop release schedules<br />Spend appropriate time on mobile architecture, don’t rush to code<br />Estimation<br />Be agile, don’t wait for “the big release”<br />Step 4: Create Your Roadmap<br />
  17. 17. Roadmap shouldn’t be static<br />Anything changing in the user base?<br />Evaluate new devices, platforms, access methods<br />Analysis of usage – where, when, features<br />Re-evaluate UI accordingly<br />Continuously changing mobile ecosystem may demand change in strategy<br />Step 5: Analyze and Adjust<br />In 2009, smartphone ownership in the US grew by 61% and daily mobile Web browsing grew by 89%. Annual planning cycles for a mobile product road map will result in dated plans. <br />With mobile Web and application development cycles running at three months or more for the custom design of complex services with deep integration into existing infrastructure, we're not suggesting rethinking mobile every three months. <br />We are suggesting that companies revisit their proposed offerings at least every six months to ensure that they are keeping pace with consumer expectations and skills. <br />-Forrester: Creating a Mobile Services Product Roadmap (July 8, 2010) <br />
  18. 18. Thank You for Your Time<br />Glenn M. Gruber <br />AVP, Travel Technologies<br />Ness Software Product Labs <br />glenn.gruber@ness.com<br />Mobile: 781.249.4049<br />@ggruber66<br />

×