Ge#ng Your App Dev Un-‐Stuck
Chris Schroeder CEO, App47
Nasrin Azari CEO, Mobile Reach
2
Speakers
Chris Schroeder CEO, App47
Email: [email protected] Twi9er: @chris_schroeder
Nasrin Azari CEO, Mobile Reach
Email: [email protected] Twi9er: @MobileReach
3
Isn’t Everybody Mobile?
Mobile Apps must have PURPOSE
CUSTOMER FACING • Provide informaOon
– Account informaOon – Usage informaOon
• Improve markeOng / image – AdverOsing – Features / benefits / etc
• Customer support – Easy to get answers – Easy to find contact info
EMPLOYEE FACING • MUST Improve a Process
– Faster – Easier – More accurate – More complete – Safer / more secure
• MUST be Used! – UI must be simple/intuiOve – At least as easy to use – Usage must be enforced
4
• ConnecOvity – Strength and Reliability of Network access
• DistracOon – Noise – LighOng – Other
• Elements – Ruggedness requirements (likelihood of drops, etc) – Heat, Cold, Moisture
5
Consider the ENVIRONMENT
• Customer-‐facing: – Customers
• Employees: – Field technicians – Sales force – Managers / supervisors – Support personnel
6
Who are the App USERS?
• Customer-‐facing – Drive towards desired acOon – As few clicks as possible to get to informaOon – Limited to what customers want / need
• Employee-‐facing – Response-‐Ome requirements – SIMPLE and unclucered screens – Minimize errors during data capture – Automated as much as possible
7
User Interface / User Experience
• Should cater to a wide audience • Should not assume a specific device or skillset • Web-‐based / HTML5 apps are usually best: – Performance is not a key factor to success – Availability with connecOvity is acceptable – Availability on a variety of plaeorms is a MUST – Typically very one-‐direcOonal (B2C) – SOll important to keep the UI unclucered and simple!
8
Customer Facing Mobile Apps
• Should have a very specific purpose / goal • Performance & UI is KEY to success • NaOve apps are usually best: – Offline usage is necessary for good performance – Offline usage is necessary when connecOvity is unavailable or poor
– Business can control the plaeorms / devices used – Apps are typically bi-‐direcOonal
9
Employee Facing Mobile Apps
1. IdenOfy the GOAL and USERS of the App 2. Specify the DATA used and/or captured 3. Determine TYPE of App and DEVICE(s)
4. Plan out Design, Development, and Test
5. Plan out Deployment and ongoing Maintenance
10
5 Steps to Mobile App Development
• What do you want to App to Accomplish?
• What are current metrics and success targets?
• How will you measure success (that the App has achieved its goal)?
• Who will be using the App, and what are their skills?
11
Step 1: What is your GOAL?
• Customer Support App: – Goal: Improve Customer support – Current metrics: x number of minutes to resolve an average customer support request
– Success targets: y number of minutes to resolve an average customer support request
– Measuring: Track resoluOon Ome, before and aner – Users: Business customers, low-‐skill level
• Create a set of requirements for the app based on these goals
12
Example Customer-‐facing App
• Field InspecOon App: – Goal: Reduce data entry errors, implement real-‐Ome data capture,
speed up InspecOon Ome – Current metrics: x number of minutes to complete an inspecOon; %
accurate inspecOon records; real-‐Ome report accuracy – Success targets: improvements in current metrics – Measuring: Track each inspecOon, Ome to complete, accuracy of data
capture, accuracy of report data – Users: Field techs, savvy with and knowledgeable about task itself, may
not be proficient mobile device users
• Create a set of requirements for the app based on these goals
13
Example Employee-‐facing App
• DATA: – IdenOfy the Input and Output required for the App – Specify parameters around the data
• TYPE: – Based on Users, environment, and Purpose, idenOfy whether you want to go Web or NaOve
• DEVICE: – For NaOve apps, what plaeorms do you want/need
14
Steps 2 and 3: DATA, TYPE, DEVICE
• Design: – Base on Data requirements and Purpose – Keep it simple
• Development: – Buy versus Build decision – Assign appropriate resources
• Test: – Pilot with small group of users
15
Step 4: Design, Development, Test
• IniOal Deployment • Ongoing Management – Tracking end-‐user usage and saOsfacOon – Iterate mobile apps and re-‐deploy based on feedback – Modify apps, Deprecate apps, Deploy new apps – Training
• Managing updates – Plaeorm changes – Bug fixes – App updates – New apps
16
Step 5: Deployment, Ongoing Support
Chris Schroeder CEO App47
Email: [email protected] Twi9er: @chris_schroeder
17
Thank you
Nasrin Azari CEO Mobile Reach
Email: [email protected] Twi9er: @MobileReach
