Ballast Lane at North Shore Tech Council 2
19
Picking the Right Areas for Mobile in Your Por7olio Larry Ehrhardt Ballast Lane Applica>ons, LLC
-
date post
14-Sep-2014 -
Category
Business
-
view
960 -
download
1
description
Larry Ehrhardt of Ballast Lane Application shared again at the North Shore Technology Council's IT SIG meeting
Transcript of Ballast Lane at North Shore Tech Council 2
Picking the Right Areas for Mobile in Your Por7olio
Larry Ehrhardt Ballast Lane Applica>ons, LLC
Agenda
• A look at a few “Men>oned” apps
• Por7olio Selec>on Criteria • A couple of case studies
• Ques>ons / discussion
Card Munch
• Men>oned by App Annie on MSNBC
• Bought by LinkedIn in 2011
• Camera connected to a sweatshop
Uber
• Men>oned at Xconomy
• Removes scheduling and transac>on fric>on
• Historically mundane industry with liQle tech
Ne7lix
• Men>oned at My House
• Portability, search, recommenda>ons
• Same content, but much beQer user experience
1. Removed the Data Collec>on Barrier
• Gather Data With Other Tools – Camera – Loca>on
• GPS • Wifi / bluetooth
– Scanner – Transac>ons – Algorithms – Voice – Facebook / customer account
X
2. Focused and BeQer
• Limited use cases
• Offloaded data intensive work to the web
• Built on rich content
• Significantly improved status quo
3. Neatly Fit a Business Driver
• Marke>ng / customer acquisi>on
OR
• Help users do something beQer
OR
• Deliver something new
Adding Mobility to Current Assets
• Picking the opportunity • Designing for the opportunity • Dealing with APIs
• Selec>ng the pla7orm(s)
• Improving the app over >me
Case Studies
Website – Designed for Scanning & Drill Down
Mobile App – Designed for Paging and Discovery
Website – Color Matching Online Items
Mobile App – Matching Your Items
APIs • Custom APIs
– RESTful – SOAP
• Web Pla7orm APIs – Drupal – Wordpress
• Mobile “Back-‐Ends” – Kinvey – Parse
• Quality Checks – User Management – Performance – Completeness – Consistency – Error Messaging – Versioning – Mobile Libraries – Caching
App Pla7orm Choice: Business and Technical Decision Na-ve Mobile Web Cross Pla7orm
Owner Demographics
Distribu>on Flexibility Library Support
Quality of Experience
Development Costs Pla7orm Op>miza>on
Pla7orm Switching / Evolu>on
Design In Ways to Learn About Users
Surveys
App Sign-‐up
Event Tracking
Crash Reports
Adding Mobility to Current Assets
• Picking the opportunity
• Designing for the opportunity
• Dealing with APIs
• Pla7orm(s) selec>on
• Improving the app over >me
Ø Based on goal and the fit
Ø Leverage the device
Ø Start here and monitor quality
Ø Na>ve
Ø Add analy>cs
