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

Orrie Shannon - How We Share Wattpad with the W...

Orrie Shannon - How We Share Wattpad with the World

Orrie Shannon, Android Team Lead from Toronto-based social reading/writing app pioneer Wattpad, will discuss how the organization’s end-to-end release process and continuous integration with Google’s services mitigates risk with each release and helps to maintain a high quality rating with their 3 million active users.

Orrie will detail how the Android team leverages the support of their beta group of some 90,000 active users, utilizing Gradle to create and upload the different build variants as part of their release process. He will also touch on how Wattpad monitors usage information and crash data analytics to evaluate new features, as well as to detect and address bugs.

AndroidTO 2013

October 17, 2013
Tweet

More Decks by AndroidTO 2013

Other Decks in Technology

Transcript

  1. Aka, move fast while reducing these... “YOU WATTPADER JUST F$%&#@

    WITH A GOOD THING. I JUST UPLOAD THIS NEW WATTPAD AND IT F$%&#@ UP MYYYY LIBRARY! DO KNOW HOW PISSED I AM RIGHT NOW. BECAUSE OF YOU GUY I HAVE TO FIX MY LIBRARY & ITS REALLY F$%&#@ UP!” - a Wattpad user
  2. Wattpad Android App • Social app for reading and sharing

    stories • 13.5M user installs • 1.6B minutes a month • Cumulative rating 4.52/5.0
  3. A Year and a Half Ago... Development Testing Release! Monitor

    feedback Respond quickly to problems *Repeat roughly every 3-7 weeks
  4. The Challenge • Bugs have a bigger impact, there are

    more users! • Not sure how users will respond to feature changes • Patchwork fixes impact release cycle
  5. Separate APKs vs. Google’s Alpha/Beta • Difficult to recruit new

    users • No feedback on Play Store • Can’t have beta and production side by side
  6. • Distributed internally ~65 people • via Google Play Private

    Channel • Need Google Apps for Business account Internal Beta
  7. Internal • First iterations of new features • Emailing apk

    had poor adoption rate • Auto updates
  8. Day 7 New Features Introduced 1.0 Release Branch Work continues

    on 1.1 Day 14 Feature Com plete 5% rollout Develop Branch Day 21 UI tweaks and bug fixes 20% rollout Day 24 Bug fixes 100% forced rollout Day 27 M inor bug fixes Gold Candidate Day 30 Production Release Cycle
  9. • Major changes have been tested by many users •

    Releases every ~4 weeks Production
  10. • Track user behavior • Refine features before launch •

    g+ vs. Twitter sign in Google Mobile Analytics
  11. Crashlytics • Android and iOS • Monitor fatal and non-fatals

    • Integration with JIRA and other PM tools
  12. Mobile Wars • Android vs. iOS • Point scale for

    bug severity • Done before major releases
  13. Summary • Integrate often • Get early feedback from users

    • Use analytics and crash reporting to measure quality