the evolution of mobile development tools - from mobilize 2013
DESCRIPTION
Presentation from Jay Srinivasan, Appurify #mobilizeconf More at http://event.gigaom.com/mobilize/TRANSCRIPT
Wednesday, November 13, 13
Jay SrinivasanCo-Founder and CEOAppurify
SPEAKER:
THE EVOLUTION OF MOBILE DEVELOPMENT TOOLS
Wednesday, November 13, 13
The Evolution of Mobile Development Tools
(or)
How to Launch Better Mobile Apps
Jay Srinivasan, CEO and Co-Founder, Appurify
Wednesday, November 13, 13
Mobile application development is broken
Limited use of continuous integration, automated testing
Lack of mobile-specific debugging and performance tools
Inefficient launches, stability/network/laggy client issues
Find problems post launch
Results in poor ratings & lost revenues
Wednesday, November 13, 13
Users punish apps with bugs
0 10 20 30 40 50 60
App#2#
App#1#
Stability,)performance,))and)quality)
Reten6on)and)ra6ngs)
DAU)and)installs) Revenue)
DAU#by#days#post#launch#
App1 and 2 are similar games, released around the same timeMain difference was time spent on QA prior to launchIt’s not just the first launch—buggy updates will hurt you as well
Wednesday, November 13, 13
Appurify’s working on fixing this!
Mission to create comprehensive mobile lifecycle management platformFounded early 2012Funded by Google Ventures, Foundation Capital, Felicis Ventures & others~20-person engineering-focused team in San Francisco
Wednesday, November 13, 13
Over the last 1.5 years, we’ve worked with mobile developers to pinpoint ways to improve launch quality
How to launch better apps
1.Test and optimize on real devices
2.Not just real devices. Real user conditions too
3.Automate! Manual testing not enough
4.Not just functionality. Stability, network, lag are critical
Wednesday, November 13, 13
1. Test and optimize on real devicesYour users are on real devices, not simulators and emulators
Many crashes, memory issues, network issues will only show up on real devices
Appurify provides:Dedicated, shared or private device clouds
Simulate network, location, accelerometer, gyroscope, magnetometer events, device memory
Wednesday, November 13, 13
2. You need to test on real user conditions as well
70%$
90%$
0%$FTUE*3$FTUE*1$
AT&T$
FTUE*2$
Verizon$
50%$
60%$
80%$
FTUE*6$FTUE*5$FTUE*4$
FTUE$comple?on$rates$for$the$same$app$on$AT&T$vs.$Verizon$
Comple'on)rates)on)AT&T)below)
minimum)threshold)for)organic)app)
growth)
Real user conditions as important as real devices
Network performance, battery consumption, memory usage are leading causes of poor performance
Wednesday, November 13, 13
3. Automate! Manual testing not scalable for mobile
Too many devices and operating systems to test on (>40 combinations just for iOS!)
Too many user conditions to test on
Manual testing is going to miss bugs, and will slow down releases
Many open source or free automation frameworks out there
Appurify runs all frameworks on real devices, continuously from your build server
Wednesday, November 13, 13
4. Not just functionality. Stability, network, lag are critical
Functional bugs are not the only drivers of poor ratings
Users particularly intolerant to crashes and network issues
Appurify provides pre-launch crash reports, network waterfalls, performance statistics, and powerful on-device run-time debugging tools
Classification of 1-star reviews (Top 200 apps in iOS app store)
Crashes,(bugs,(40%(
Slow(network(perf.,(8%(
Laggy(client(perf.,(5%(
Non@perf.(related,(47%(
Wednesday, November 13, 13
Questions or more info?
Contact: www.appurify.com
[email protected]@appurify.com
Wednesday, November 13, 13
Wednesday, November 13, 13