Showing posts with label app legal challenges. Show all posts
Showing posts with label app legal challenges. Show all posts

Wednesday, 15 October 2014

iOS8 apps GPS Always privacy battery concern

Why do the majority iOS8 apps access GPS all the time and is this killing battery life.

The short answer must be yes. A parallel example and some context can be found is the now growing by day popularity smart watch scene. The latest 920XT from Garmin battery lasts only 24 hours with GPS on all the time, and this almost doubles to 40 hours when using the GPS in a limited mode every minute rather than constantly. However, if we turn GPS off, but still leave the Bluetooth, WiFi (yes I am also bored of hearing misguided people turning Bluetooth off on their smartphone to save battery, ok it helps, but relativity is important...) and other smart features on, we get months of battery from the 920xt.
Smartwatch battery life varies between hours with GPS enabled, to months with GPS off, but still Bluetooth, etc on.... 
So go to Settings, Privacy, Location Services and prepare to be surprised, and then quite annoyed.

Surprised is first because you notice that pretty much all your apps are using location services always. Indeed I found this from the iOS alert to this very fact.
iOS8 alerts to the fact that all these apps are using GPS in the background
And then you look at the list and see responsible app developers either having "while using" only by default or allowing the option to be only using GPS when needed, the "While Using" option, like the amazing 645Pro camera app and Apple's own App Store by default: as it should be.

Responsible Apps are only using GPS while Using by Default.
So then you look at the long list of apps and see that from, yes admittedly I have a lot of apps on my devices at any given time. Surprise then shifts to annoyance as you try to make the Avis and Addison Lee (taxi) apps only use data when they need to, i.e when using: Why does Avis Car hire and Addison Lee, obviously now on their second app developer and fell out with their first (prey tell why two apps if not???) need to know my position all the time? in Case they want to surprise me with an unsolicited car? I don't think so!

Why do all these apps need constant GPS access?

And it is not just Avis, ist pretty much all except 5 of 55 apps.
Page 2

Page 3

Page 4

Page 5
After going through them all (and one iOS8 crash... #notwhenJobswasabout) I have managed to turn all that I can back (some apps have changed, sorry).

The Good are British Airways, Chrome and the Apple apps.
 I am very bored with clicking through apps now...
Facebook and Google leading the way
 About here is when iOS 8.02 crashed, nice... look for the whole section again...

Instagram, the amazing Manual and the great Netatmo, as well as other FB propoertises and Apple apps: good
 Nice to see Netatmo being responsible, and you can see that "Manual" is a showcase Apple app right here!

Speedtest the only one here other than native apple apps
 No surprise Ryanair not following British Airways's great example... I wonder if they plan to charge me extra for not being close enough to the airport when checking in?

Vivino and Twitter the only responsible app developers here in this last list
So why is this? Well a key part of the problem is that apps, and indeed mobile, are still "something we should do" for most big companies and brands, and they do not have anyone representing good UX reporting all the way up, which is just not a good plan in todays "mobile first" environment where Facebbook clearly does. The next question that comes along after battery life is; are these companies using / processing this info off the app? We all still remember the contacts scandal apps privacy of a few years back I am sure...

Monday, 28 May 2012

App privacy, app contracts, apps legal issues

Apps legal Challenges Conference

I spoke on the closing panel at the apps: legal challenges conference on 24th May, and promised an update so here it is, along with another interesting development as reported by one of my two must read columnists over at wired on apps privacy.
Clueful: An app that tells you what some apps my be hiding...

App data privacy issues

I approach this subject with great interest, as, having spent tens of millions of pounds of other people's budget on 1000's of apps over the last 5+ years, the legal side has always fascinated me: My first encounter of the nitty gritty of this was doing th Nokia festival guides, in association with another 3rd party event organiser, multiple agents, agencies and 3rd party developers it could have been a quagmire. The key, I am not ashamed to add, was me: not for any other reason that I was then the "mobile director" in charge of pulling all elements together, from development to legal, to developers, to agencies, approving the technical and other content of press releases, software releases and even the promotional and other text messages meant that these nasties, like privacy issues, were spotted before they went out of the door.

What is the mobile app privacy issue?

As apps have become more common place, they have been treated more and more as just the same old digital, like the internet but on the mobile, which is right, legally they are, however technically they are not, and while you can visit internet privacy law every so often (every supplier change usually!) mobile is more fluid, and things like the Path (and others) talking data from devices and on happens, and I have seen it do so for the following reasons which make mobile different:
  1. somebody says: "we need to be on these devices by x day" the developers say we cannot because... the report goes back to somebody who cannot be bothered or to be fair is too busy to get their hands dirty as they not just "mobile director" but also "digital director", "innovation director" "all things shiny-and-new director" :) and so he says "make it happen. in this situation good people will usually do what is best from either, a) a timescale point of view, b) a technical point of view,  or c) a user experience point of view, almost always in that order. In the case of Path et al, taking complex user details from the battery, memory, connectivity and CPU constrained handset and putting it in the ever more powerful cloud made technical, time and even User Experience (UE) based sense - this was an all round better experience, however... nobody in legal would have been, nor have a process to be consulted.
  2. lawyers who are consulted very rightly point out these issues and so are either a) not consulted or b) somebody goes over their head and says "make it happen" in which case the lawyer has his options covered (there is a more common term I shall refrain from using). Really, in-house technical staff are usually allowed the luxury of external specialist help for issues mobile, that is what I do for a living, so why are in-house of even external legal not allowed that luxury: you chose your in-house or external legal to cover your core business, its quite reasonable to assume that you or they may benefit from some specialist help as well
  3. The whole process is almost entirely outsourced to 3rd party developers so internal people really do not know even what code that the developer is using could even be accessing other client's data, etc...

Why Mobile App privacy issues arise

In all these cases, no single person, or even team, has full end to end ownership of mobile, or if they do they seldom have the time to keep themselves up to speed with all the developments in legal, technical and more,  as they are often wearing some other digital / technical / legal hats ... and so, there is no "mobile director" who takes responsibility for the end to end process.

A big part of this is that, while mobile is now surpassing web in terms of access even on key social network sites, the team size in any organisation no where near reflects this, and indeed in many parts of the industry (mobile advertising for example) many players are still just relatively dabbling in mobile.

A second part is that, just like companies who provide our services cannot keep up, neither can we the consumers, and we are just dabbling in mobile security most of the time: it's all well and good that we get a bit upset at Path and others for taking our data (or did we, really??? TBH I think my data is probably safer on Path's server, assuming its saved in a PCI compliant way, that it is on my own phone where its impossible for all the data to not be associated with me the user...) we did not mind the better user experience and it probably was in the T&Cs... somewhere: Yes I am talking to you, and me, the iphone user who has never read the 64 pages of T&Cs that apple throw at us every few weeks, the app user on any platform who does not read even the APIs and app wants if we want it badly enough, and so on...
Clueful UE: wot no "privacy" page :)

Avoid & be aware of app privacy issues

So in the meantime, the best we can all have is an app that we may uses every so often to have a peek and see that we are all ship shape, like clueful. Essentially, like now a spyware detector has surpassed the need for an antivirus for the tech savvy, an app (for end users) and a policy for app providers and an app store owners and even mobile operators is probably the safest way forward. Spybot mobile operator edition anyone?

If you like this article, please like us or +1 on Google+ or or tweet, retweet etc, follow me on twitter or whatever social means of showing appreciation takes your fancy... yes, even like me on the fancy if you so wish :)

If you want to discuss issues around privacy, legal issues surrounding apps and app stores (I can only point out issues I have come across, cannot offer legal advice!) of just the trials and tribulations of enabling mobile for your company then use the contactify button above right