Chapter 4. Managing Hardware Platforms
You want the best experience for your users. With a mobile device packed with sensors, why not tap into the raw power of the machine running your code to deliver the best possible interaction? With a little bit of work, you can take advantage of the accelerometer, the GPS, the camera, and the hardware on the device. This chapter will survey some of the more common use cases and lessons learned managing the underlying hardware platform.
4.1 Asking for Permission to Use Device Hardware (iOS)
Whether you are snapping photos for a social media app or scanning a QR code in a corporate lobby, the device’s camera is one of the most powerful sensors at your disposal.
In some cases, a card or a modal screen with a button that triggers the hardware will help someone understand why they need to provide access like the two-step wireframe depicted in Figure 4-1. This permission flow is common in iOS applications, where permission requests can be delayed until they are required by the application.
Hardware Requires Hardware
The simulator can do some hardware testing; however, especially when dealing with camera data, there is no substitute for a real device.
Figure 4-1. A wireframe depicting a two-step user flow for requesting camera permissions
The Apple App Store will review your application and flag any permissions that have not been explicitly declared. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access