Mobile Apps For Events: Adoption and Longevity
•
0 recomendaciones•543 vistas
The document discusses positioning a mobile app for success at events. It provides examples from a case study of the Society of Critical Care Medicine's annual event app, which saw an 80% increase in downloads from 2011 to 2013. The presentation outlines questions to consider when developing an app, such as who will lead the project, what information to include, and how much time is needed. It also recommends not taking on more than can be handled and continuing to evolve the app with features like gamification, personalization, and data for increased sponsorship. Lessons learned include carefully evaluating vendors, thorough testing, and ongoing engagement rather than assuming the job is done after launch.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (12)
Destacado
Destacado (20)
Similar a Mobile Apps For Events: Adoption and Longevity
Similar a Mobile Apps For Events: Adoption and Longevity (20)
Más de Cvent
Más de Cvent (20)
Último
Último (20)
Mobile Apps For Events: Adoption and Longevity
- 1. Position a Mobile App for Success
- 2. Mobile Apps for Events: Adoption and Longevity Capitalize on the evolution of mobile technology Moderator Ada Walton Digital Content Editor, Meetings + Events Media Group at Tiger Oak Publications Speaker Kevin Long Director, CrowdCompas s Mobile Apps Marketing team at Cvent Speaker Melissa Nielsen Manager, Print, Online & New Media Communications at Society of Critical Care Medicine presented by: sponsored by:
- 3. Preparing and Marketing Your App for Success ‣ 4,000 medical attendees ‣ 100+ speakers ‣ 5-day event ‣ 80% download increase ‣ Focused selection process Speaker Melissa Nielsen Manager, Print, Online & New Media Communications at Society of Critical Care Medicine
- 4. Case Study: Event App Downloads Society of Critical Care Medicine Your App Downloads 2011 2012 2013 1,200 1,874 3,371
- 5. Position a Mobile App for Success Who will be the project lead? What info will you include? How much time do you need? How will information be populated? What will it look like? Layout and production schedules Glossary of terms Tools for Success
- 6. Don’t bite off more than you can chew The Evolution
- 7. Basic spreadsheets API personalization Gamification features Data for increased sponsorship Branding Culture Community commitment Year-round Engagement Tactical Strategic 2011 2012 20132010 The Evolution
- 8. Lessons Learned Do think carefully about the pros and cons when choosing a vendor Do test early and often Don’t assume when it’s launched you’re done Don’t wait – expectations are growing while you’re waiting
Notas del editor
- Moderator at left (paresh)
- Overview of my association and our meetingSCCM – multpirofessoinal members who work in the ICU - technical savvy About 4,500 professional registered attendees come to our congress each year / 6,000 total once you count exhibitors and facultThree years 1st year - 1200 2nd year - 1874 3rd year – 3371 of downloads, which is an 80% increase from the previous year.
- Need #s
- WHOI work in the publications department of SCCM and its sometime asked how I became in charge of apps in general. And I think it’s important to stress that I would value knowledge of a production schedule and organization of data over technical know how. Your vendor is going to be able to explain a lot of the technical stuff so you really want to turn to the person who is already doing the program book or someone like that to move this process forward because that person likely is going to be the one to proof your app as well. WHAT INFOEmpowered to make decisions -– don’t try to fit everything from the program book into the app- if everything is important, nothing is important! Obvious info, but also consider what maps are helpful and which ones are not; we sorted by location because we were spread out. TIMEI think we all try to build padding into our production schedules, but you want to be especially sure to account for the unexpected when launching an app. Start Planning in June > Launch a Shell in Oct. > Market in Nov. Dev POPULATED API vs. Spreadsheets / Pros and Cons LOOKI found it very helpful to actually sit with the team and the vendor to make a kind of story board for our app. In years previous, we kind of said okay, we need an icon for schedule, an icon for exhibitors and here’s some of the information that goes under each one. But, the staff and vendor found it very helpful when we created an actual spreadsheet that outlined each layer of the app. So we especially references two production spreadsheets throughout the process:
- Do and Donts DO Think carefully about the pro and cons when chosing a vender: uploading spreadsheets vs. building an API for your content Native vs. HTML – what’s your wifi situation going to be? Athetneication vs. non authentication Content management system access Don’t assume when it’s launched your done follow through on an marketing strategy test on numerous devices proof your app and make sure everyone understands how changes to the program are reflected in the app. Just because the program book is printed, you have make sure staff is also thinking about this other compeneent I’d say, Don’t Wait - Our meeting attendees are attune to new technologies and are growing to expect this type of technology. We don’t want to be going through growing pains at a time when meeting apps are a ubiquitous part of the meeting experience