Download to read offline
Uploaded byMano Marks
Focus on (the Right) Content - Oracle Developer Community Day 2017
The document discusses the importance of understanding both the producer and consumer perspectives in developer-oriented content, highlighting questions around product benefits and monetization strategies. It emphasizes the need for content that informs, inspires, and delights developers while also addressing potential dangers like affordability and limited feature growth. Furthermore, it outlines various examples of companies and services that fit into different monetization and user engagement models.
More Related Content
Similar to Focus on (the Right) Content - Oracle Developer Community Day 2017
Focus on (the Right) Content - Oracle Developer Community Day 2017
- 1. Focus on (theRight) Content Understanding Developer-Oriented Content Mano Marks, @ManoMarks
- 2. Who Am I What’smy perspective? ● 9 years developer relations, Google ● 2 years Developer Relations Director, Docker ● Consumer of APIs
- 3. Questions to answer ●Why do you offer the product? ● Why does someone use your product? ● What learning objective are you trying to achieve?
- 4. Why are youdoing this?
- 5.
- 6. Developer Tools areProduced by Companies P.S. Yes even most open source tools
- 7. Companies exist tomake money
- 8. Content producers Ask: ● Howdoes your tool benefit the company? ● How does your tool benefit the user?
- 9. Content consumers Ask: ● Howdoes your tool benefit the company that produces it? ● If I’m not paying for this with money, how am I paying for it?
- 10. So back tothe money...
- 12. ● Charge forthe product ● Charge for support (Freemium Model) ● Charge for professional services
- 13. Examples Enterprise software companies ●Microsoft ● Oracle ● Canonical ● RedHat ● Docker
- 14. Examples ● Services ○ MapBox ○GitHub ○ GitLab ● IAAS ○ AWS ○ Azure ○ Google Cloud Platform (or G Suite or whatever) ○ Oracle Cloud
- 15. User benefits ● Theycan pay for what they need ● Direct investment by company in needed features ● Product support
- 16. Dangers ● Some userscan’t afford it ● Charging for professional services makes product more complex
- 17. USERS USERS USERS USERSUSERS USERS USERS USERS USERS USERS USERS USERS
- 18. Free products, createusers Examples ● Identity Services ○ Google Login ○ Facebook login ● Google Maps ○ Drove search ○ Builds Brand ● Mobile OSs ○ Android ○ iOS
- 19. User benefits ● Linksto other services ● Low to no cost ● Wall gardens can be big
- 20. Dangers ● Shapes product ●Walled gardens ● Users aren’t your own ● Originator Brand Maintenance ● Limited feature growth
- 22. User benefits ● Benefitfrom others contributing data ● Data heavy product
- 23. Dangers ● Provider losesinterest ● Low quality collective data
- 24.
- 26. Would they reallydo that? Source: https://sensortower.com/blog/facebook-and-parse-launch-bolts-on-github-to-simplify-mobile-app-development
- 27. Goals of content Reachlots of developers Help them succeed Make them feel good about your tools
- 28.
- 29. Inform Inform: Developers needto know!
- 30. Developers need toknow how!
- 31. Inspire: Developers needto know how to put it together!
- 32.
- 33. Refresh: Questions toanswer ● Why do you offer the product? ● Why does someone use your product? ● What learning objective are you trying to achieve?
- 34.