How to launch a event ticketing sales business [Part 3 - Building for Mobile]
0 likes331 views
This document discusses 10 common mistakes brands make when building mobile experiences. It emphasizes that mobile is different than desktop, with different screen sizes, input controls, and data costs that must be optimized for. It also stresses understanding user contexts and scenarios, using location relevance, and integrating core mobile functions instead of just porting desktop sites. The overall goal is providing a seamless experience across devices by avoiding these mistakes.
How to launch a event ticketing sales business [Part 3 - Building for Mobile]
- 1. HOW TO LAUNCH A EVENT TICKETING SALES BUSINESS ON MOBILE ROCKET FUEL FOR ASPIRING MOBILE MARKETERS @FLEPHDOTCOM
- 2. SECTION THREE BUILDING FOR MOBILE
- 3. GOAL TO PROVIDE A SEAMLESS USER EXPERIENCE ACROSS MULTIPLE DEVICES OBJECTIVE AVOID THE COMMON MISTAKES SO MANY BRANDS MAKE WHEN IT COMES TO MOBILE DEVELOPMENT
- 4. MISTAKE #1 THINKING THAT BUILDING FOR MOBILE IS THE SAME AS BUILDING FOR WEB
- 5. THE BONUS OF DESKTOP DESIGN A HANDFUL OF BROWSERS & SIMPLE INPUTS
- 6. OH F%*&! 9,000+ PROBLEMS FOR MOBILE DEVELOPMENT
- 7. MISTAKE #2 “LETS TAKE OUR EXISTING WEBSITE AND JUST MAKE IT SMALLER TO FIT INTO THE SCREEN OF A MOBILE PHONE”
- 8. DON’T MINITIARISE - OPTIMISE
- 9. MISTAKE #3 FORGETTING THAT INPUT CONTROLS CHANGE THE GAME!
- 10. USE ‘FAT FINGER’ DESIGN CONTROLS
- 11. MISTAKE #4 IGNORING THE IMPLICATIONS OF MOBILE DATA COSTS
- 12. OH S%#@?! $4560 FOR DATA IN TEN DAYS!
- 13. OH S%#@?! $9,48 FOR ONE MB OF DATA
- 14. THE US HAS THE HIGHEST DATA COSTS IN THE WORLD $42 FOR 2 GIGS… LOCALLY!
- 15. ONLY DELIVER THE CONTENT THEY NEED!
- 16. MISTAKE #4 NOT LEVERAGING TECHNOLOGY
- 17. THERE ARE SO MANY… • • • • • • • • MOBILE VARIANTS SCREEN (REAL ESTATE) SIZES PORTAIT vs LANDSCAPE ORIENTATION MOBILE PLATFORMS OPERATING SYSTEMS FILE FORMATS INPUT CONTROLS etc
- 19. WE USE TECHNOLOGY MOBILE CONTENT ADAPTATION
- 20. MISTAKE #5 THINKING THAT CONTENT IS KING IN A MOBILE ENVIRONMENT
- 21. USER CONTEXT SCENARIOS RESEARCH DRIVING OUT & ABOUT LOST EVENT RESEARCH AND COMPARISONS ONE HANDED BROWSING WHILE DRIVING QUICK, SNAPPY BOOKING WHILE WITH FRIENDS AND NEEDING DIRECTIONS TO OUR EVENT
- 22. MISTAKE #6 SCREWING UP THE USER JOURNEY
- 23. SCREWING UP THE USER JOURNEY FOR EVERY ACTION THERE MUST BE A REACTION INSIGHT DIFFERENT TYPES OF ACTIONS REQUIRE DIFFERENT RESPONSES
- 24. ALWAYS USE ACTION CONFIRMATIONS 01 EVENT CONFIRMATION
- 25. ALWAYS USE ACTION CONFIRMATIONS 02 EVENT AND LOCATION CONFIRMATION
- 26. ALWAYS USE ACTION CONFIRMATIONS 03 EVEN,T, LOCATION AND DATE CONFIRMATION
- 27. MISTAKE #7 IGNORING PROXIMITY RELEVANCE
- 28. USE LOCATION RELEVANCE TO GET CUSTOMERS
- 29. MISTAKE #8 NOT BUILDING FOR THE LOWEST COMMON DENOMINATOR
- 30. REMEMBER NOT ALL USERS ARE CREATED EQUAL
- 31. CONSIDER THE LEAST SAVVY MOBILE USER OUR LOWEST COMMON DENOMANATOR NO MOBILE EXPERIENCE INTUITIVE NAVIGATION
- 32. CONSIDER THE MOBILE MANIAC USER OUR CONTENT HUNGRY MOBILE MANIAC QUICK LESS CLICKS INFORMATION QUICK TICKETS
- 33. MISTAKE #9 NOT INTEGRATING THE CORE FUNCTIONS OF A MOBILE PHONE
- 34. GIVE THEM ACCESS TO CURRENT FEATURES
- 35. MISTAKE #10 BUILDING MOBILE APPS BECAUSE YOUR COMPETITOR HAS ONE
- 36. DO YOU NEED AN APP? MOBILE WEB VS NATIVE APPS
- 37. SECTION THREE – WHAT HAVE WE LEARNT BUILDING FOR MOBILE • THE PITFALLS AND CHALLENGES FACED • WHY BUILDING FOR MOBILE IS DIFFERENT TO WEB • HOW INPUT CONTROLS EFFECT THE USER EXPERIENCE • HOW TO LEVERAGE MOBILE TECHNOLOGY (MCA) • USER CONTEXT SCENARIOS AND HOW THEIR IMPACTS • HOW TO USE PROXIMITY RELEVANCE TO GET CUSTOMERS • THE SPECTRUM OF MOBILE USERS AND ITS IMPACT • MOBILE WEB vs NATIVE APPS – WHAT DO YOU NEED?