Wearables, Things & Apps - Mobile Dev + Test '15
Download as PPTX, PDF0 likes314 views
This document discusses using mobile apps to interface with and control internet of things (IoT) devices. It describes disconnected and connected devices and how Bluetooth Low Energy (BLE) and other standards enable connectivity. Custom logic is needed on both devices to add value. Apps provide a functional and engaging user interface on phones and leverage their capabilities. Successful IoT apps are simple, fast, and display formatted data and alerts. Performance monitoring tools like Crittercism help diagnose and fix app issues to ensure a good user experience. Thorough testing of device and app interactions is also emphasized.
![Custom Logic :: Hub [Phone]
• Receive data from the thing
• Do… something… with it
– Display data
– Communicate with services
– Store information
– Configuration](https://image.slidesharecdn.com/mobiledevtest15-150415112734-conversion-gate01/85/Wearables-Things-Apps-Mobile-Dev-Test-15-7-320.jpg)
![Why an app?
• Functional
– Apps and phones are a powerful and flexible
combination – leverage them!
• CPU, memory, push, GPS, large batteries
• Engage users
– Always one touch away
– Larger interface than most wearables
and things
• [Relatively] easy to develop](https://image.slidesharecdn.com/mobiledevtest15-150415112734-conversion-gate01/85/Wearables-Things-Apps-Mobile-Dev-Test-15-8-320.jpg)
Wearables, Things & Apps - Mobile Dev + Test '15
- 1. Wearables, Things & Apps Chris Beauchamp Developer @WhitewaterLabs Evangelist @Crittercism @cjbeauchamp Using apps to help users experience IOT devices bit.ly/CritterDevTest
- 2. The Disconnected Thing • Disconnected from all other things • Limited functionality – Data collection • Wearables, sensors – User control • Automation, functional controls • Some things have WiFi or connections • Large, expensive, not always feasible
- 3. The Connected Thing • Connected to many other things – Wifi, Bluetooth, NFC, etc
- 4. Making the connection • BLE enables data transfer to/from phone • NFC (Near Field Communication) • Wired options (plugging into USB port) • Headphone jacks
- 5. Interfacing with the thing • We have two devices and a data connection between them, what next? • Need to install our own logic on both devices to add value
- 6. Custom Logic :: Thing • Keep the logic lightweight • Resource constrained – CPU – Memory – Storage – Battery • Keep the thing doing what it does best • Data transmission
- 7. Custom Logic :: Hub [Phone] • Receive data from the thing • Do… something… with it – Display data – Communicate with services – Store information – Configuration
- 8. Why an app? • Functional – Apps and phones are a powerful and flexible combination – leverage them! • CPU, memory, push, GPS, large batteries • Engage users – Always one touch away – Larger interface than most wearables and things • [Relatively] easy to develop
- 9. So. Many. Apps. There’s an app for everything… there needs to be an app for YOUR thing!
- 10. Apple Watch BREAKING NEWS: APPLE LAUNCHING SMART WATCH
- 11. Apple Watch • Requires the presence of an iPhone – GPS/Cell Data/Wifi – Battery life • Multiple types of application interfaces – App, Glance and Notification – Allows various use cases & variable investment • Easy-to-use APIs for interface between watch & app / device
- 12. Apple Watch
- 13. Communicating with the iPhone
- 14. Responding to the watch request
- 15. Learn More Full Demo (w/ Source Code) available at: bit.ly/CritterDevTest
- 16. General Structure => Hub IOT Device
- 17. Phone App Use Cases (pt1) • Thing generates data – show it! • Managing and connecting user accounts – Somebody’s gotta do it • Thing configuration and updates – Push changes to keep the thing current
- 18. Phone App Use Cases (pt2) • Use the phone to upload and download data to and from the cloud – Data processing, sharing, analysis, etc – Offloads CPU cycles, memory, battery from the thing – Use this data to ‘teach’ the device about the user so it’s customized to them
- 19. Use Case :: SPG (Starwood Hotels) • Get reservation info • Check in • Unlock door
- 20. Use Case :: American Airlines • Flight Status • Check in • Boarding pass
- 21. Use Case :: Nike Running • Start/manage workout • Check times/status • Easy access
- 22. What do these apps have in common? Form – Users should love using your app • A lot of engineers here… hug your designers! – Keep it simple • You have lots of cool content and functionality… highlight it! • Don’t make the user do too much – or squint!
- 23. • Make smart use of space • Swipe instead of a button? Pinch instead of a slider? • Only show what’s necessary! not actual size*
- 24. What do these apps have in common? Function – Quick, easy-to-use information – Alerts and notifications keep interactions fast – Formatted data allows for easy access
- 25. What do these apps have in common? Leverage Data – What do users really want to see/do? – Can’t add it all, so use data tools to see what’s most popular
- 26. What do these apps have in common? Performance How they interact with the outside world
- 27. What happens when things break?
- 28. Performance Monitoring • What happens if your deployed app… – Breaks on a user? – Runs slow? – Drops a connection with your thing? – Crashes? • Left in the dark unless the user tells you – Bad reviews are no good!
- 29. App Store Feedback & Analysis
- 30. SDK for App Performance
- 31. Crittercism • Remotely diagnose issues happening with your app • Make it more stable, faster, more reliable • Provide your users with a great user experience
- 32. Crittercism – Crash Reporting
- 33. Crittercism – Crash Reporting
- 34. Crittercism + Apple Watch SDK automatically monitors connections
- 35. Crittercism – Transaction Monitoring
- 36. Crittercism – Transaction Monitoring
- 37. Make it work! • Connectivity between devices is key – Have a solid layer to manage exceptions, errors and interference or device malfunctions • Test, test, test, test, sleep, test – Devices, settings, configurations, everything
- 38. Breakdown • Leverage smartphones and apps – they’re powerful! • Don’t forget about design • Test until you can’t test anymore – and then test! • Leverage tools to help you get feedback and fix issues
- 39. Finishing Up http://crittercism.com bit.ly/CritterDevTest Chris Beauchamp Developer @WhitewaterLabs Evangelist @Crittercism @cjbeauchamp
Editor's Notes
- #3: Wearables/sensors Could be a beacon, a weather recorder, gps, etc User control Could be home automation, controlling agriculture mechanisms Some of these things can be connected to wifi, etc – but for this case it’s not
- #7: We want the thing to do its thing! Gather data and transmit it to the hub
- #8: We’re in the smartphone age – everyone has one in their pocket and it’s exceedingly powerful In most cases, the best way to do this is via an app
- #9: -
- #10: -
- #11: The hottest IOT device around Ok, not new technology But apple is the king of creating demand. Will this bring the public into the smartwatch space? The demand generated by the iPhone / iPad drove so much innovation – same for the watch? Applications and use cases we couldn’t even conceive are now commonplace
- #16: Technology isn’t new, but demand for this device will be unheard of Excited for innovation to follow
- #17: Knowing that apps & devices will follow this structure
- #18: - Will be different in every app, but…
- #19: - Will be different in every app, but…
- #20: - Will be different in every app, but…
- #21: - Will be different in every app, but…
- #22: - Will be different in every app, but…
- #24: There’s not much space here! Designers and developers had to think about pixels on the phone – now it’s even smaller! WHAT NOT TO DO Too many interactions Items too small
- #28: - IOT Device is so dependent on other services - The most common issue will likely be connections
- #29: -
- #30: // and it’s a problem that every single developer faces. Including these guys
- #31: - And we’re on all the major platforms
- #32: -
- #33: -
- #34: -
- #36: -
- #37: -
- #38: -
- #39: -
- #40: -