Lookback.io - See how people really use your app
lookback.io
lookback.io
What caught my attention was how you managed to snap the keyboard and status bar and get the app past approval (which is what I assumed from the demo). But after giving it a go, it seems that your SDK doesn't actually capture the kbd and status bar.
Being curious, I did some further digging into your SDK and UIKit. I presume for the demo, you must have used a custom SDK build so that you could tap into some private APIs? You can get the UIWindow for the keyboard via public APIs (UIApplication's -windows) but the status bar is private (_statusBar ivar on UIApplication; easily accessible with -valueForKey:@"_statusBar"]). Note that _statusBar is a subclass of UIView (direct subclass of _UIScrollToTopInitiatorView which is a subclass of UIView).
So for anyone else wondering how they capture the full screen, that's the way it seems to be done :)
Oh, by the way, if anyone's doing screen / view capturing, I highly recommend looking into the new iOS7 APIs (-drawViewHierarchyInRect:afterScreenUpdates: and -snapshotViewAfterScreenUpdates:).
I realise that Lookback is mainly geared towards internal testing but it should be easy to aid the support workflow, too. Capturing the status bar is the only private API you actually need to use to fully recreate the screen, although I don't know whether the team behind Lookback is using additional priv APIs for other parts.
Thanks for all the private API hints :D
> Send your app to users using TestFlight and ask them to start recording. You can also ask them to perform certain tasks you've prepared, typically sent via email.
As sksksk noticed there is an interface that comes with Lookback from which the user can turn on and off the recording. In newer versions of our SDK there is also a small indicator in the top menu so the user doesn't forget that the app is currently recording.
On a presentation note:
1. Use a tripod for your camera. 2. please fix your lights! You probably aren't hung over, but the lighting suggests baggy eyes. Lighting is easy. Use window light. Heck, you are even shooting with with a front-facing camera on your phone, so it should be easy to pick some lighting that works nicely :-)
Both of these things are cheap or free, and will drastically improve your presentation, IMO.
Cheers!
I understood that this is the camera display from the phone as the user is using your app...is that not correct? Because I thought it was kinda cool...
EDIT: fellowshipofone's response seems to confirm :)
In this instance I agree that better (less realistic) lighting would show the product in a more favourable light. (excuse the pun).
It's not "deceiving the customer" it's just advertising, and it works, we shouldn't shy away from that because of some notion of "realism".
I'm currently using Reflector to record the screen, along with a separate camera to record the user's face and hands. It's a more complex setup that makes remote testing significantly more difficult, so there is definitely value in this, if the price is right.
puts on tinfoil hat