Skip to content

Commit 8b731bc

Browse files
committed
new post. status bars matter
1 parent 9367197 commit 8b731bc

5 files changed

Lines changed: 43 additions & 0 deletions

File tree

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
---
2+
layout: post
3+
title: Status bars matter
4+
subtitle: Perfecting your app screenshots for the App Store
5+
excerpt: You have spent countless hours, days, months, or maybe even years perfecting your app. There has been plenty of blood, sweat, and tears. Your relationships and your health have suffered through the development process. You are ready for 1.0 and the time has arrived to prepare all of your content
6+
---
7+
8+
You have spent countless hours, days, months, or maybe even [years](http://www.polygon.com/2014/2/6/5386200/why-it-took-a-year-to-make-and-then-break-down-an-amazing-puzzle-game) perfecting your app. There has been plenty of blood, sweat, and tears. Your relationships and your health have [suffered through](http://blog.jaredsinclair.com/post/93118460565/a-candid-look-at-unreads-first-year) the development process. You are ready for 1.0 and the time has arrived to prepare all of your content for the App Store — app icon, keywords, description, localizations, and screenshots (and soon [app previews](https://developer.apple.com/support/appstore/app-previews/)).
9+
10+
But even with all of Dan Counsell's [excellent advice](http://dancounsell.com/articles) on how to promote your app and refine your App Store presence, I continue to see iOS developers make one glaring mistake in their screenshots. This common flaw is even overlooked in Dan's article on [*Designing Great App Store Screenshots*](http://dancounsell.com/articles/designing-great-app-store-screenshots), which should be required reading for all iOS developers. But what does it fail to mention? **The status bar.**
11+
12+
<img class="img-thumbnail img-responsive center" src="/img/statusbar.jpg" title="iOS status bar" alt="iOS status bar"/>
13+
<small class="text-muted center">iOS status bar</small>
14+
15+
#### Sore thumbs
16+
17+
Status bars matter. If configured well, they go unnoticed. But if they are sloppily ignored, they stick out like a sore thumb. And sadly, there are a lot of sore thumbs in the App Store. Below are actual status bars taken from the screenshots of three different apps curently in the App Store. All apps were on one of the top charts within the top 50.
18+
19+
<img class="img-thumbnail img-responsive center" src="/img/statusbar-bad1.jpg" title="Status bar example 1" alt="Status bar example 1"/>
20+
<small class="text-muted center">Sample 1: status bars seen in the App Store</small>
21+
22+
<img class="img-thumbnail img-responsive center" src="/img/statusbar-bad2.jpg" title="Status bar example 2" alt="Status bar example 2"/>
23+
<small class="text-muted center">Sample 2: status bars seen in the App Store</small>
24+
25+
<img class="img-thumbnail img-responsive center" src="/img/statusbar-bad3.jpg" title="Status bar example 3" alt="Status bar example 3"/>
26+
<small class="text-muted center">Sample 3: status bars seen in the App Store</small>
27+
28+
There's a lot of information in an untamed status bar. In *Sample 1* it looks like someone is from Canada, and working late through the evening. At least she had good reception and an adequate power supply. In *Sample 2* the developer lives in the UK, and has extremly poor reception. She needs to charge her iPhone soon, but at least she knows her current location. *Sample 3* is by far the most interesting. We can see AT&amp;T's typically poor reception, thus the developer is in the US. This guy was up late, but at least he remembered to set his alarm so that he could wake up in the morning to take more screenshots and charge his device.
29+
30+
Status bars seem negligible until you notice how unsightly and distracting they can be. Luckily, the mistakes above can be easily avoided.
31+
32+
#### Preparing your screenshots
33+
34+
We know that screenshots are one of the most important parts of the App Store content for which you are responsible. Users *rarely* read app descriptions in their entirety, but they *always* look at screenshots. If the status bar is visible in the screenshots that you provide, then it better be clean and uniform across every single one. It should have full cell reception bars, no carrier text, full Wi-Fi bars, and a fully charged battery. Each screenshot should also display **the exact same time**. *No exceptions*. Finally, depending on your app's functionality, it might make sense to show the GPS location or Bluetooth indicators, but use sparingly. Also remember that you can remove the status bar altogether.
35+
36+
#### Raising the (status) bar
37+
38+
You can automate all of this with an awesome utility app called [Status Magic](http://shinydevelopment.com/status-magic/), which adds perfect status bars to your screenshots or removes them completely. It is worth every penny, and it will get your screenshots looking clean and consistent in no time.
39+
40+
The only aspect of the status bar that you should customize, aside from the colors, is the time. Apple uses `9:41 AM`. Choose something reasonable &mdash; for example, [Clear](https://itunes.apple.com/us/app/clear-tasks-to-do-list/id493136154) uses `10:00`. I like to use `7:06 AM`. If you cannot decide on a time that is meaningful to you, then Apple's `9:41 AM` will work beautifully and you will fit right in.
41+
42+
Don't let your app be a victim of status bar neglect.
43+
This is about polishing your app and its presentation in the App Store to the highest degree. **Status bars matter**, and every detail counts.

img/statusbar-bad1.jpg

7.33 KB
Loading

img/statusbar-bad2.jpg

7.68 KB
Loading

img/statusbar-bad3.jpg

10.3 KB
Loading

img/statusbar.jpg

3.16 KB
Loading

0 commit comments

Comments
 (0)