How can you take privacy seriously[0] when there is the option to capture full screenshots and send them back to the dev team? That is absolutely not an expected behavior of any app. Am I not understanding something here?<p>[0] "We take privacy seriously. You can choose to hide sensitive information, only record certain sections of your app, or even pixelate out all text entirely."<p>Edit: added source of claim<p>Edit 2: To clarify: I don't mean to diminish the hard work of the team. I know how hard it is to put your work out there and I'm sure there was a lot of interesting technical work that went in to it. That said, I really think the premise is troubling, especially if it is intended beyond a "beta tester" group. Even with the best intentions, this is a really powerful tool that could be easily abused.
This could be really great. Watching users interact with your product directly provides a whole different level of insight.<p>A few things that I can think of that they may already be considering:<p>1. Asking the developer to specify explicitly which screens should be recorded. From the article, it seems like it's opt-out (the developer specifies which screens should <i>not</i> be recorded), rather than opt-in.<p>2. Showing long recordings at high speed, slowing down/pausing at "interesting" portions<p>3. Data aggregated across multiple users: for example, a report of places in the app where most users pause the longest<p>4. Displays of multiple users' interactions with a single screen, overlaid on top of each other<p>5. Dealing with user offline scenarios where data may need to be locally stored and then uploaded when a connection is available<p>They must be doing some sort of frame delta on the videos to save bandwidth, I'm assuming.<p>Very cool idea!
Woah. This is going to change the game.<p>Rapid iteration on mobile is tough enough...as long as this doesn't have too big of a hit on performance, this is about to change the way we develop mobile apps.