Typically, it's best to share a screenshot of the full app or at least the main parts of the app. A screenshot of only the bug might not give enough context, though. Instead, crop the screenshot to show just the app-then perhaps add an arrow to point out the problem.ĭon't show too little, either. Trying to point out a bug in an app? Don't share a full-screen screenshot. When it comes to your privacy, the convenience might not be worth the risk.ĭon't show too much. That's handy to share a Google Analytics graph with team members quickly, but be careful about sharing sensitive items.
Some third-party screenshot tools like Droplr can automatically upload screenshots. Be sure the app you're screen capturing doesn't show private data-and if it does, either crop or blur that part out.īe careful with auto-upload. They're usually secure on your device, but if you take a screenshot and share it, anyone can see whatever was on your device when you took the screenshot.
Our devices brim with private info, from phone numbers and email addresses to more sensitive data including ID and credit card numbers. And just-for-fun screenshots should be double-checked to make sure they only have the info you want to share. Bug reports might need to show the broken part of the app. Making a software tutorial? You'll want to show the entire app, and perhaps add an arrow to point out features and guide your readers. Here are a few pointers:Ĭonsider what the screenshot is for. Think carefully about what's on your screen and why you're shooting it, to make sure your screenshots are perfect for their intended purpose. That's why you shouldn't just snap a random screenshot. Screenshots are more than just pictures of software-they're pictures of your workspace, with all the info you might see right now.
0 kommentar(er)
