Mobile Commerce meets the Real World - Mobile Ticketing
•Transferir como PPTX, PDF•
0 gostou•569 visualizações
Ben Whitaker of Masabi's presentation to the Cellcom conference in Tel Aviv, Israel.
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (9)
Semelhante a Mobile Commerce meets the Real World - Mobile Ticketing
Semelhante a Mobile Commerce meets the Real World - Mobile Ticketing (20)
Último
Último (20)
Mobile Commerce meets the Real World - Mobile Ticketing
- 1. Mobile Commerce meets the Real World:Mobile Ticketing
- 2. Technology Warning! Just because you can do something with mobile technology - Does not mean that customers will want to use it Does not mean that corporations will promote it
- 3. Customer Adoption: Normal people will only try to use new technology to do a regular daily activity… …if the old way of doingit is painful enough to make them try something new. At that moment: offer them a better way.
- 4. Corporate Adoption: Make a clear business case first Must make more money Reduce Costs or Increase Sales Must pay for itself in the first year Capital is not easy to raise right now $$$
- 6. 4 alphabets
- 7. 2 Factor Authentication
- 12. Mobile Services WAP / xHTML Browser based, like on the web No javascript or Ajax on most mobiles Application Installed on the phone Dedicated, customised
- 15. Faster responses
- 17. SMS failover from GPRS
- 18. Avoid settings, reception & roaming problems
- 19. Cheaper + faster for the user
- 20. Send only the data
- 22. Not just the “easy” ones
- 23. Adapt content and graphics to screen size
- 24. Automatic handling of handset bugs
- 30. 1024bit RSA, 256bit AES
- 32. Tiny 3Kb library
- 33. Works on all Java phones
- 34. Extremely fast
- 36. SMS, GPRS, Bluetooth, NFC
- 38. Mobile ticket opportunity Only 12% of UK rail tickets sold on the internet – most bought at station Over 2/3 of mobile users do not complete registration if it’s on the web So: Sign up the users when they need it in a queue in a hurry next to a broken ticket machine
- 40. Repeat Purchase
- 41. Key usability points No sign-up process no usernames no passwords Mostly off-line interface, SMS backup Fast repeated regular purchases Auto-show tickets, full screen barcodes
- 42. E-Ticketing Options Contactless RF Smart-Card (Oyster, Mi-Fare) NFC Phones Barcodes Self-print Mobile Dependant on scanning hardware Soft rollout option with visual inspection
- 43. Soft roll-out option Avoid up-front capital cost of full barcode scanner rollout Visually inspect at launch Staff report barcode ticket usage levels each week Occasional SMS or scan checks Staged scanner rollout for routes with significant adoption
- 44. UK Rail Barcode Ticket Standard RSPS3001 Approved in December 2008as the UK standard for self print and mobile barcode rail ticketing
- 45. Shared Barcode Standard Share self-print and mobile barcodes between Operators and 3rd party retailers Public and open security Based on PKI, standard SSL certificates Decentralised system - robust Cheap to implement and use
- 46. Scanner Options Any barcode scanner, online or off-line, must support: 2D Aztec with CCD imager Handheld Small basic scanners for door staff Advanced PDA based scanners for service staff Bluetooth scanner upgrade for Avantix Mobile 2 Cash Register/EPOS Scanners Connect via USB or as “keyboard wedge” in between keyboard and EPOS like a normal scanner Fixed Scanners for gates or check-outs Retro-fit to existing gates, user places phone on rubber face to scan Or built in at manufacture by gate supplier Basic Advanced Bluetooth EPOS Scanner Retro-fit Fixed / gate scanner
- 47. Benefits: Customer Sign-up in the queue (no usernames or passwords) No queues ever again Quicker re-purchase Tickets same price Corporation Lower cost per sale No need to expand stations (major cost) Staged capital expense on scanners
- 48. Example Heathrow Tickets Adaptive layout, size, rotation, DRM
- 50. No need for explicit sign-up or passwords
- 51. Just type CVV again for future purchases
- 52. All user data entry and validation performed off-line by application
- 53. Secure SMS for users without data settings or with poor reception
- 55. No paper, no queues - barcode tickets
- 57. Auto-detects SMS or GPRS
- 58. 1-2 SMS per ticket
- 59. Doubles the consumer uptake by removing Data issues
- 62. ben@masabi.com+44 7788 895 894
Notas do Editor
- Masabi have been producing downloadable mobile applications for over 7 years, and today Masabi secure mobile applications process millions of dollars worth of transactions every year
- Our applications are built on three core principals –Make the application usable and relevant to the end user, and make the default use cases quick and easy on the mobile. (I’ll show you some sides of that later)Then, PORTABILITY to all popular handsets, including the older handsets that many developers avoid, to ensure the largest possible user-base for your service.For Mobile commerce – security, on all phones, to modern public standards.
- [The screenshots above are animated, to show useful UI widgets helping the user to select from large lists, or input Credit Card numbers correctly]WAP and WEB services are Thin Clients ; good when you have a reliable, low latency connection. Mobile is not like that. – inside buildings, moving vehicles and in remote locations: connections are often dropped or unavailable.Mobile Java allows us to build FAT clients, and not just glorified mini-browsers!Applications should provide most of the interaction while OFF-LINE and then only require an occasional connection at the end to make transactions, or get updates.e.g. you should be able to review your bank account and create new payment instructions while on the metro, not only when stood still in good Here are screenshots showing how you can quickly select one station from a list hundreds long, and also how to perform local validation of credit card numbers before sending to reduce the number of unecessary network connectionsSMS Failover:Many users (more than half, we reckon) cannot make network connections from Java using WAP, because they need to switch to the correct INTERNET settings. To provide these users with an out-of-the-box instant purchase, the application can automatically detect the lack of functioning GPRS and switch to encrypted SMS instead.
- Hold up 3510i or old Nokia S40 phoneWhen you provide transactional software for these old phones, we find that significant numbers of people use them. Can you afford to throw away 10-20% of your users?(By way of comparison Microsoft and iPhones represent around 1% of the market)To provide Portability, we use our own porting Framework: DevelopMEWe’ve seen many mobile products that are either attractive, but high-end only; or basic-looking and available on all handsets.Through DevelopME we are able to provide attractive apps on all Java phones.You have to work hard to build full function applications that work on the older phones, and you can’t out-source it, or think about it late in your dev cycle – it has to be at the core of how you build everything.It’s not just different graphics sizes and bugs, you have to build variations of UI’s that make the best use of very different input mechanisms on the different phones, and not expect the end consumer to re-learn new UI concepts that they don’t already use on their phone every day.