Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Mobile Presentation For Slideshare
Similaire à Mobile Presentation For Slideshare (20)
Mobile Presentation For Slideshare
- 1. 1 CLIENT NAME PRESENTATION TITLE Mobile Development
- 2. Mobile Me This 2 CLIENT NAME PRESENTATION TITLE
- 3. Mobile me this : app or site? 3 CLIENT NAME PRESENTATION TITLE Site Reach Non interactive, research based content Easy to deploy Easy to optimize HTML5 will make the experience more app like App Monetizing Superb experience utilizing features of the phone Interactive content Client side/always available
- 4. Now Jump… 4 CLIENT NAME PRESENTATION TITLE
- 5. Developer BSA Analytics Search QA 5 CLIENT NAME PRESENTATION TITLE Invite the right people to jump with you and your mobile project will swim right along
- 6. Let it begin 6 CLIENT NAME PRESENTATION TITLE
- 8. Screen resolutions and orientation
- 11. SEO Strategy
- 12. Goals
- 13. Tagging spec
- 14. Use cases and test plans7 CLIENT NAME PRESENTATION TITLE Let it begin- Make sure your development team knows these things
- 15. Track Attack 8 CLIENT NAME PRESENTATION TITLE
- 17. Keep mobile and desktop site version separated in the reporting suite
- 18. Don’t differentiate devices in reporting suite
- 19. Expect fewer standard conversion, be creative in conversion metrics
- 20. Apps must have simple tags built into app9 CLIENT NAME PRESENTATION TITLE Track Attack- how to prove roi and track users
- 21. Hide and Go SEO 10 CLIENT NAME PRESENTATION TITLE
- 23. Marketing
- 24. Announcements
- 26. Leverage typical best practices
- 28. Reviews and WOM
- 30. 13 CLIENT NAME PRESENTATION TITLE Circle of life- Development Process
- 32. Keep it simple- minimize data usage and user requirements
- 34. Keep it clean- as little user input as possible
- 36. QA needs and processes 16 CLIENT NAME PRESENTATION TITLE Internal Schedule time on the QA calendar Test plan Get access to QA environment Handsets External Redfoundry access Handsets Test plan
- 37. 17 CLIENT NAME PRESENTATION TITLE Push It
- 38. Publishing Apps 18 CLIENT NAME PRESENTATION TITLE
- 39. Rate This 19 CLIENT NAME PRESENTATION TITLE
- 40. 4 tips for boosting App ratings from Mashable Tip #1: Don’t beg for a rating in the app description. Tip #2: Don’t randomly ask for reviews via push notifications. Tip #3: Don’t Rush into Things. Tip #4: Don’t harass your users.
- 41. They Want What? 21 CLIENT NAME PRESENTATION TITLE
- 43. Version updates
- 44. Client changes
- 45. Ratings
- 46. Reviews
- 47. Site
- 48. A/B Testing
- 49. Best practices
- 51. http://en.wikipedia.org/wiki/List_of_common_resolutions http://en.wikipedia.org/wiki/List_of_mobile_phones_with_FWVGA_display http://en.wikipedia.org/wiki/List_of_mobile_phones_with_WVGA_display 24 CLIENT NAME PRESENTATION TITLE Resources: Mobile Phone resolutions
- 52. Resources: QA Device anywhere 10 tools to test mobile apps and sites Fire Fox in browser tool
- 53. Resources: Development Apple Development sign up Android Development sign up Developer Environment List Explanation of Thawt Security certification 26
- 55. Icon
- 56. Promo
- 61. Age Rating
- 62. Pricing
- 64. Slide share on publishing
- 65. List of app distribution platforms (stores)
- 66. List of Android publishing requirements
Notes de l'éditeur
- DeveloperBSAAnalyticsSearchQA
- Potential Conversion-
- Image Assets:ScreenshotsIconPromo Featured Graphic Marketing AssetsPromotional video linkMarketing opt-outSEO friendly titleDescription
- Tip 1:The worst method for requesting a positive review is to beg users for one. Even worse to ask directly from within the app description (or in the information describing an app update). The app description is for describing the value of your app. Many will view out-of-context pleading in the description as a sign the app is moderate-at-best. Users will be less likely to download it in the first place. So leave the app description for describing the app. Tip2:Push notifications are to be used to communicate data that is valuable and useful to the user in regards to the app’s function, not to promote or advertise your marketing needs. Abusing push in a self-serving way can result in a frustrated user, one who is more likely to simply uninstall your app or rate it poorly. Further, it’s against Apples ToS, and could result in your app being pulled from the App Store. Tip3:Wait until your user is enjoying your app - even on the cusp of getting addicted - before you ask for a rating. The game Cut the Rope does an excellent job with this timing, waiting for the user to get fully engaged before they ask for a review. At some point after the user has reached the 4th or 5th level, when the user is obviously having fun with the game and has stuck around, the game gently asks the user to rate the app with a typical alert box between levels.The fact that the app waited is important for several reasons, most importantly because it weeded out the users that didn’t want to play the game, or who felt the game was lame, or boring, or simply not for them. Those people are exactly who you don’t want rating the app, so filtering them out gives you an advantage. Of course, you don’t want to wait too long either—some players may never reach the higher levels and some might get frustrated by the increasing difficulty of the game. Cut the Rope grabs the user at the perfect moment, when they’ve felt satisfaction of some early success, but without the frustration of getting stumped.Non-game apps might ask for ratings based on usage, such as after a user has read three or four articles, checked in to a location X number of times, or filled out their profile to a certain point that shows a commitment to the utility. It really depends on what your app does and how quickly a user will feel satisfaction with your app. Letting them have a good experience is critical.Some people recommend waiting for a user to open the app a set number of times. The risk there is that a very small percentage of people open your app a second time to begin with, even if they had a good experience. Capturing them in the first visit, for most apps, is the best time to ask (again, this depends on the type of app you have and why a user is opening it to begin with).Tip4:Ask users one time to rate your app and provide them with the option to say “No thanks.” You could also add an option to “Remind me later” so you can try to capture users that might be willing to rate, but prefer to do so at a later time. Some people ask after every app update, but unless the update is pretty significant, and infrequent, I’m not sure I recommend that. You never want to annoy your users at the moment you’re giving them a public voice about your app.We do recommend using an alert from within the app, and linking directly to the app within the iTunes App Store. This makes it as easy as possible for a user. Implementation can also often be done in under an hour, so it’s hard to argue not doing it.http://www.mobiledevhq.com/fourtipsforboostingyourmobileappratings-3/article
- Image Assets:At least 2 screenshots of app (more is generally better) <320x480, 480x800, 480x854, 1280x800> must be 24 bit PNG or JPEG with no, full bleedHigh res app icon, must be 512x512, 32 bit PNG or JPEG and a MAX size of 1024Promo graphic (this will appear in the phone) 180x120, 24 bit PNG or JPEG, no border artFeatured Graphic (this will appear in the hero carousel on the full site version of the app store) 1024x500, 24 bit png or JPEG. Keep in mind this will be downsized Marketing AssetsPromotional video link is optionalMarketing opt-outSEO friendly titleDescription (4000 characters)Copy Protection (determines if the app can be copied) if turned on it will take more memory for the appContent rating: just think about the kidsPricing *if you check free you can never go back*After setting your default price, pretty up the prices for other countries Supported DevicesScreen LayoutsRequired Features