12 wp7 marketing windows phone applications


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

12 wp7 marketing windows phone applications

  1. 1. Marketing Your <br />Windows Phone <br />Applications<br />Jason Lee<br />Ethos Technologies<br />
  2. 2. Agenda<br /><ul><li>Zune
  3. 3. You as a Developer
  4. 4. Silverlight on Windows Phone 7
  5. 5. Development Tools
  6. 6. XAML
  7. 7. Play Time
  8. 8. DataBinding
  9. 9. MVVM
  10. 10. Q & A</li></li></ul><li>Zune<br /><ul><li>Zune Software
  11. 11. Zune is a tool to synch media content of your PC and your phone
  12. 12. + Visual Studio
  13. 13. Zune is also used as link between Visual Studio and a real phone for deployment and debugging </li></li></ul><li>App Deployment<br /><ul><li>Marketplace
  14. 14. The Marketplace is the ONLY way for a user to get applications onto a Windows Phone
  15. 15. Applications can be downloaded directly from the phone
  16. 16. Users can also purchase applications from Zune, and deploy them on to the phone later
  17. 17. For developers
  18. 18. Developers has different way to deploy and test their applications</li></li></ul><li>You as a Developer<br /><ul><li>Real phone ? Real phone !
  19. 19. A real device is not mandatory for Windows Phone development
  20. 20. However, it is highly recommended to test your app on a real phone before submitting it
  21. 21. Unlock
  22. 22. In order to deploy your app to a phone, it needs to be unlocked
  23. 23. Registered developers can unlock devices( 3 devices for now), and deploy/test their own applications
  24. 24. Hook your unlocked phone to your PC, deploy using Visual Studio or Application Deployment tool provided by SDK
  25. 25. Zune software is necessary for debugging on a real phone</li></li></ul><li>Applications on Marketplace<br /><ul><li>Applications can be free or paid
  26. 26. “Try Before Buy”
  27. 27. For those paid applications, in order to attract as many users (which leading to as many buyers), it’s a good practice to provide trial phase (also known as the “try before buy” approach) in them.
  28. 28. The Windows Phone Framework provides you API to do it
  29. 29. Price it appropriately
  30. 30. So far, prices among 0.99$ ~ 1.99$ are best accepted.
  31. 31. Advertisement is another good plus
  32. 32. Even if your app is free, you still can make money by embedding AD in your application
  33. 33. The Windows Phone Framework provides you API to do it</li></li></ul><li>Beta Versions<br /><ul><li>Beta Version Support
  34. 34. The Marketplace supports distribution of beta version.
  35. 35. Beta version will expire after a short time (90 days for now)
  36. 36. No need to unlock phones to test while enabling developers to build higher quality apps
  37. 37. Beta version can NOT be updated
  38. 38. Steps
  39. 39. Developer selects a list of testers (up to 100 for now)
  40. 40. Developer sends an email with a private DeepLink to the testers
  41. 41. Only selected testers can test the applications and provide feedback</li></li></ul><li>Private Distribution Service<br /><ul><li>Private Distribution
  42. 42. A way to distribute certified apps privately to a targeted set of users
  43. 43. Can be updated
  44. 44. No limit on the number of participants and duration
  45. 45. Steps
  46. 46. Developer need to get the app certified before distribution (app is not discoverable on Marketplace Search)
  47. 47. Developer sends an email with a private DeepLink to users
  48. 48. Turn the distribution into public at any time</li></li></ul><li>Show Me The Money<br /><ul><li>70% For You
  49. 49. Money is transferred directly to your bank account, deducting taxes (tax rate may differ among different locations)
  50. 50. Payments are made monthly
  51. 51. 99$ per Year From You
  52. 52. In order to publish applications on Marketplace, you should pay a membership fee of 99$ per year</li></li></ul><li>XAP<br /><ul><li>XAP package
  53. 53. Contains all elements of an applications
  54. 54. Applications are deployed in the form of *.xap onto your phone
  55. 55. It’s is actually a zip file
  56. 56. Size
  57. 57. A XAP file should not be larger than 20M
  58. 58. Limit for all files is 400M
  59. 59. Still many more on App Hub
  60. 60. Refer to detailed information on App Hub.</li></li></ul><li>Localizations<br /><ul><li>Your Apps Are Sold Around World
  61. 61. The Marketplace is accessible from many countries
  62. 62. It’s a good idea to support multiple languages in your app
  63. 63. Localization Considerations
  64. 64. It’s a common practice to manage your localization resources in dedicated DLLs.
  65. 65. Leave enough area for display elements in case translations in some languages are longer.
  66. 66. You can use localization features provided by .NET Framework
  67. 67. Do NOT depend on any machine translations or online translators, have your app fully tested by experienced target language users.
  68. 68. Never hardcode</li></li></ul><li>Manifests<br /><ul><li>AppManifest.xml
  69. 69. Defines assembly parts that included in your app
  70. 70. Do NOT change it manually
  71. 71. WMAppManifest.xml
  72. 72. Defines phone services used in your app
  73. 73. Marketplace will use this information to notify end users of what this app is going to do (i.e. Location Services, Camera, Contacts, Push Notifications)
  74. 74. Remove unused capabilities to avoid any unexpected disfavor.</li></li></ul><li>! & ?<br />Thank You ! <br />Any Questions ?<br />