Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Developer Advocacy for Native Mobile Platforms

Developer Advocacy for Native Mobile Platforms

Considerations for building communities and serving developers on iOS and Android

beardouglas

April 16, 2016
Tweet

More Decks by beardouglas

Other Decks in Technology

Transcript

  1. Bear Douglas
    Dev Rel Lead, Twitter | @beardigsit
    Developer Advocacy for Native Mobile:
    What’s Different?

    View full-size slide

  2. Hi, I’m Bear!
    Hi, I’m Bear. I work on Fabric, used to work on Parse and before that FB platform. I also run community for the SF Ember.js meetup.

    View full-size slide

  3. Mobile Is Growing
    App Store - 1.5M apps as of June ‘15 Google Play - 2M apps as of Feb ‘16
    Source: Statista

    View full-size slide

  4. But where are the people?

    View full-size slide

  5. Even specifying that this is a mobile conference, you don’t get all mobile developers. You get lots of people who are interested in general- it’s hard to attract a strictly targeted audience.

    View full-size slide

  6. Challenges For Native Mobile Community
    • There are just fewer of us.
    • The platforms are still new(ish)

    View full-size slide

  7. Android Getting Started, 2010

    View full-size slide

  8. Challenges For Native Mobile Community
    • There are just fewer of us.
    • The platforms are still new(ish)… so there aren’t lots of experts
    • “Authoritative” resources can be hard to find

    View full-size slide

  9. So what’s to do?

    View full-size slide

  10. 1
    Meet people where
    they are

    View full-size slide

  11. Find the native conferences that are specifically about the language or the platform. “Mobile” conferences are too broad.

    View full-size slide

  12. What about hackathons?

    View full-size slide

  13. Meetups are your friend

    View full-size slide

  14. Segment your docs
    WRITE FOR DIFFERENT EXPERIENCE LEVELS
    2
    What does this mean? It means that you can’t just teach your own content, you have to make your stuff a working guide to best practices on the platform

    View full-size slide

  15. 3 Levels Of Documentation
    • API Reference
    • Guides
    • Tutorials

    View full-size slide

  16. Reference Docs
    IN IDE example

    View full-size slide

  17. Reference Docs

    View full-size slide

  18. Invest in Shippable
    Sample Code
    3
    PRODUCT TUTORIALS = PLATFORM TUTORIALS

    View full-size slide

  19. if you’re working somewhere, you can learn from other people’s code. if you’re on your own, you need to read someone else’s production code to learn from

    View full-size slide

  20. If it was trivial to write,
    it’s probably trivially helpful
    This is not always bad- a small, simple sample that is easy to read and show a single feature has utility. But there is a huge need for complex, best-practice sample apps.

    View full-size slide

  21. This gives you a chance to show people things they wouldn’t know about otherwise- in an Android app, use Protobuf, e.g.

    View full-size slide

  22. 4
    RTFM? NOT SO MUCH.
    Support is a teaching
    opportunity

    View full-size slide

  23. Hard not to feel like this, but have to resist

    View full-size slide

  24. Guidelines For Making This Reasonable
    • Educate directly where the issue is simple
    • Looks like you need to fix ___. It’s a problem because ____. Try ___.
    • Refer where there’s something more complex to learn
    • You hit your [Dex method limit](link to Android docs)
    • Set community standards about what’s OK to leave
    Invest in teaching, but don’t be a martyr to the volume- decide what’s reasonable to take on education-wise and then do it well

    View full-size slide

  25. 5
    Tie It Together
    HELP OUTLINE THE BIGGER PICTURE

    View full-size slide

  26. 1. Meet developers where they
    are - and where they learn

    View full-size slide

  27. 2. Create docs and samples for
    audiences at multiple skill levels

    View full-size slide

  28. 3. Investing in leveling up the
    community is a win for everyone

    View full-size slide

  29. Thank You
    @beardigsit

    View full-size slide