etouches Introduces eMobile

1,255 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,255
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
23
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Tom starts
  • Tom finishes
  • suzanne
  • To tom
  • etouches Introduces eMobile

    1. 1. Presenter: Suzanne Carawan, VP<br />Presenter: Tom Kingsley, CEO<br />IntroducingeMobile<br />March 1, 2011<br />
    2. 2. Primer & rationale<br />etouches’ Mobile Design Principles<br />
    3. 3. Smartphone Usage<br />
    4. 4. eMobile Product Design Principles <br /><ul><li>Start with the basics and keep it simple
    5. 5. Avoid additional pain for event organizer and staff
    6. 6. Start attendees down path of independence from paper and people and reliance on technology
    7. 7. Create demand for increased networking/interactive capabilities
    8. 8. Native Mobile App
    9. 9. Integration between eReg and mobile app</li></li></ul><li>Start with the Basics<br />Serve the customer that we have today<br />Hard look at attendees’ usage:<br />Client surveys, market feedback, prospect requests and personal experience told us:<br />Adoption of event-specific mobile apps are still in infancy<br />Attendees not overly fascinated by complicated apps and just want simple info<br />Usage period for the app is very short (less than 3 weeks) because organizations seldom integrate mobile into the marketing plan and event’s educational content <br />We need to get attendees hooked on using mobile at event in easiest way possible and then add to the communication channel by delivering additional features and ideas for usage<br />
    10. 10. Avoid (More) Pain for Organizers<br />Little education exists on mobile, lots of hype <br />Many event professionals now in technology buying roles and haven’t been taught how to evaluate, what to look for, what to expect<br />Event professionals often buying on price or getting from mobile partner for in-kind swap:<br />> no one using the mobile app<br />> not properly promoted<br />> organizer didn’t fill out all the necessary info because there is additional set up of a centralized web application that pushes to mobile<br />
    11. 11. Understand Behavioral Drivers<br />People that can afford to go to events still like paper<br />Move to mobile is less about mobile adoption than it is about weaning people off of paper and to electronic communication/information reliance<br />Resources stipulate that the move to mobile is needed and critical<br />Focus instead on shaping attendee behavior towards using mobile for info access, scheduling, etc versus paper guides, etc.<br />eMobile starts this process and then will add features to lead attendees down this path<br />
    12. 12. Create User Demand<br />Technology often fails not because of lack of features, but because of introduction/adoption strategies<br />Less is more!<br />Achieve your target penetration rate of mobile usage with a finite set of features<br />Users will begin to ask for more and then will use features when they are released<br />Help event professionals learn product marketing techniques of new product introduction and adoption strategies<br />
    13. 13. Create User Demand<br />Focus on the purpose and the value of what the mobile app delivers—never the features!<br />Designed for simplicity, but convenience<br />Set up the situation so that users ask for morerationale behind investing in native mobile app which can be easily used year-over-year and that we can add features to versus one-off sites each year that require rebuild<br />
    14. 14. Select the Right Mobile App<br />Mobile Sites<br />.mobi<br />Website optimized for use on mobile phones<br />Pro: use on a variety of devices<br />Pro: cheapest<br />Con: requires internet access<br />Native Apps<br />App built for each device’s platform and compiled<br />Pro: can use without internet access<br />Pro: greatest flexibility in adding in features<br />Pro: fastest performance speed<br />Con: features are platform dependent<br />Con: more expensive and dependent on approval processes, etc.<br />Web Apps<br /><ul><li>browser-based app that provides a version of a site
    15. 15. More capabilities than .mobi site—features are selected for use on mobile
    16. 16. Pro: cheaper than native
    17. 17. Con: requires internet</li></li></ul><li>Why Native? <br />No connection needed<br />Content stored locally on device<br />Uses Familiar Device User Interface<br />Results:<br /> Fast<br /> Reliable<br /> Familiar<br />
    18. 18. New York Times, December 28, 2010<br />“ at the Web 2.0 Summit, where about 1,000 people heard such luminaries as Mark Zuckerbergof Facebook, Julius Genachowski, chairmanof the Federal Communications Commission, and Eric E. Schmidt of Google talk about the digital future, the Wi-Fi slowed or stalled at times<br />
    19. 19. Apple Debacle<br />Steven P. Jobs, Apple’s chief executive, had to ask the audience at his company’s developer conference to turn off their laptops and phones after his introduction of the iPhone 4 was derailed because of an overloaded Wi-Fi network.”<br />
    20. 20. New York TimesDecember 28, 2010<br />“Wi-Fi was never intended for large halls and thousands of people, many of them bristling with an arsenal of laptops, iPhones and iPads.”<br />
    21. 21.
    22. 22. http://crowdcompass.com<br />Times. Topics. Places. People.<br />
    23. 23. !<br />http://crowdcompass.com<br />Times. Topics. Places. People.<br />
    24. 24. http://crowdcompass.com<br />Times. Topics. Places. People.<br />
    25. 25. !<br />!<br />http://crowdcompass.com<br />Times. Topics. Places. People.<br />
    26. 26. Native App for Events<br />Solves major pain points for organizers:<br />Attendees on the go<br />Attendees in continual internet dead zones including: airplanes, hotels, taxis, shuttles, bars, ballrooms, convention centers<br />No time or patience to maintain yet another technology hub of event information<br />Works globally and across platforms because built for the platform<br />
    27. 27. Why Crowd Compass<br />Real apps with real cross-platform capabilities from which etouches can extend its product line<br />Track record of apps for large technology tradeshows<br />Committed to event space<br />Large feature set of items that can be added<br />Willing to customize and build additional features if needed<br />Product company before custom one-off or mobile app dev shop<br />
    28. 28. Integration to eReg Product<br />eReg is etouches’ event registration, reporting and badge/certificate creation tool<br />Integration solves major pain points for organizers and IT: <br />Created conduit for data exchange between etouches product line and native mobile app from which to build<br />Event data automatically moved from eReg to the mobile app once it is set up in eReg—nothing else to do<br />Any changes to eRegautomatically reflected. No dual updating of information<br />Allows attendees to get info when they need it<br />
    29. 29. Product overview and Demo<br />Introducing eMobile<br />
    30. 30. Cross-Platform eMobile<br />Blackberry<br />Android<br />iPhone<br />iPad<br />
    31. 31. Demonstration<br />
    32. 32. Resources<br />eMobile overview (via email)<br />CrowdCompass: www.crowdcompass.com<br /> -search for “CrowdCompass” in Apple iTunes or Android Marketplace <br />etouches: www.etouches.com-free trials and regular product demos-new webinar series is coming, including event marketing plans! www.etouches.com/mix<br />

    ×