How do App Vendors Respond to Subject Access Requests? A Longitudinal Privacy Study on iOS and Android Apps
the results of a four-year undercover field study.
Besides a general lack of responsiveness, the observed problems range from malfunctioning download links and authentication mechanisms over confusing data labels and le structures to impoliteness, incomprehensible language, and even serious cases of carelessness and data leakage. It is evident from our results that there are no well-established and standardized processes for subject access requests in the mobile app industry. Moreover, we found that many vendors lack the motivation to respond adequately. Many of the responses we received were not only completely insucient, but also deceptive or misleading. Equally worrisome are cases of unsolicited dissolution of personal data, for instance, due to the
apparently widespread practice of deleting stale accounts without prior notice
One of the most intriguing hidden features of the first Daydream standalone headset — the Lenovo Mirage Solo — is its ability to play normal Android apps in a flat 2D window.
In February, Google added WebVR to Chrome on Daydream-ready phones (like Pixel and ZenFone). The WebVR standard allows users to view virtual reality (VR) experiences in a browser like Chrome by simply tapping a link and putting on a compatible headset. Yesterday, the company revealed it added support for Google Cardboard and launched a new homepage for web-based VR experiments.
WebVR support on Chrome for Oculus Rift and HTC Vive is “coming soon.”
enerally speaking, Google has very limited interest in making hardware in the first place. The cost of building things is high, the margins are low, and Google’s real specialty is in web services like Gmail and search anyway.
the real business opportunity for Google is to compel a broad range of companies to create gadgets and home appliances using its software. The hardware is secondary. In fact, building its own hardware can even work against Google: The more successful Google is at selling its own hardware, the less likely other hardware makers want to use its software, since they view Google as a competitor.
Putting all its efforts behind expanding and extending Android has made Google a top player in the smartphone market, even after its late start against Apple and the iPhone.
Chromebook:
Diigo’s Awesome Screenshot tool. Awesome Screenshot is a simple one step installation
TechSmith’s Snagit. Awesome Screenshot will only capture things that are displayed in your web browser. Snagit download the Snagit Chrome app and the Snagit browser extension. . Both tools allow you to draw and type on top of your screenshot images. Macbook and Windows laptops:
Mac keyboard combination of “Command+shift+4” “Command+shift+3” will capture everything on your screen.
Windows computer Snipping tool
Jing to take screenshots on my Mac and on my Windows laptop.
Skitch If you have an Evernote account, you can save Skitch images in your Evernote account.
iPad and iPhone:
Taking a screenshot on an iPad or iPhone is a simple matter of holding down your “home” button (the big round one) and power button at the same time. The image will save directly to your device’s camera roll. When I need to draw, highlight, or type on an image in my camera roll I turn to Skitch again.
Android phones and tablets:
As long as your device is operating on Android 4.0 or later you can take a screenshot by holding down your home button and power/sleep button at the same time. The screenshot should save to your camera roll unless you’ve designated another place for it to save. Once on your camera roll you can use the image in other apps for drawing, cropping, annotating, and sharing. Some Android devices, depending on manufacturer, include a built-in screenshot image editor. Pixlr and Skitch. Skitch on Android offers all of the same features that are outlined above. Pixlr is a more robust tool that allows you to apply image filters in addition to drawing and typing on your images.
Please consider other IMS blog entries on the topics:
Android Wear (java)
Pebble (C)
Samsung Tizen (HTML5)
Apple Watch WatchKit (Swift, Objective-C support is buggy)
WatchKit is the least mature
limitations: no keyboard, no mouse, no touch screen, battery life, limited usable screen real estate, CPU performance
opportunities: hands-free, speech for text input, sensors (gyro, camera, accelerometer), gesture-based input, BLE (bluetoothSmart)
GOod wearable Design: Recognizes immediacy, leverages context of the wearer
challenging to develop good experiences for these devices.
802.11 will eat short battery life, in addition to bluetooth. Samsung Gear S will get notification even from afar, but usually smartwatch notification is paired only in immediate proximity of the bluetoothed device.
Addon –
industrial uses of wearable: tag and quickmessages, not occupying hands.
keyboard is with swipe gestures.
Frank Schloendorn, Fiberlink, speaker
build in security is limited. Jailbroken / rooted devices are at higher risk> Open to hacking, still in infancy. No real MDM (Mobile Device Management) type solutions available
Do you currently own smartwatch
no management solutions exist today. OS: Tizen, Android, PebbleOS, Apple Watch OS etc
Cameras and other sensors cant be managed, monitored (spy scenario)
Is wearable an independent device or an extension of a smartphone
Best practices:
manage the connected device, not the wearable
be aware of what data can “leak” to a wearable device
if necessary, take more extreme measures (block bluetooth, ban devices)
new security options for mobile devices linked to wearables. bypass lock screen with presence of wearable, content sensitive security.
