Delight.io (YC W10) Lets Developers See What Beta Users Are Doing In Their Apps
techcrunch.com
techcrunch.com
All it takes is for a single customer to leave the software on there and have it get distributed to their customers, and it might turn into a big privacy scandal all over again, with not only the customer but this company being dragged in front of Congress.
I would suggest adding code into your library that either forces a pop-up or gives a message saying that the app is currently using your software, so that it warns developers using your code that it's still activated, before they send it off the the App Store. The last thing you want is for this to get accidentally installed by unsuspecting end-users.
I've never heard of them being dragged to court.
I could see tech like this being useful for submitting with bug reports or something? It's a hard sell though, seems a bit like overkill. You need to have decent testers that will use it, gotta deal with big video files, their's privacy concerns and capturing video will eat up cpu/resources and slow down the app.
So again, potentially useful, but I don't think they've made a good case for why it's worth the hassle.
If this feature or a similar one was added to an app (turned on via user consent or otherwise), would Apple approve it? This is limited to one app and essentially another analytics plugin.
Of course, this isn't a big deal if you're only testing a beta in restricted sessions (and the headline explicitly mentions beta users) but the potential for this in real world testing is huge.
And we agree with you that being able to see real user interaction gives us tons of insights.
That's a great idea. It is possible with starting and stopping Delight manually. (http://www.delight.io/api/Classes/Delight.html#task_Starting...) You can also use [Delight setPropertyValue:forKey:] to include custom property to the recording so you can access them thru search on our dashboard. Custom property is any key value pair.