iPhone Design Award Winning Projects

Apress - iPhone Design Award-Winning Projects (December 2009) (ATTiCA)......Page 1
Books for Professionals......Page 2
Contents at a Glance......Page 6
Contents......Page 7
About the Authors......Page 9
About the Technical Reviewer......Page 10
Acknowledgements......Page 11
Introduction......Page 12
Part 1: Innovating Beyond Apple’s Design Standards, While Maintaining Apple’s Logic for Consistency, Clarity, and Usability......Page 15
Developer name: Loren Brichter Development Company: Atebits Tags: Layout; Efficient Code; Workflow URL: http://atebits.com......Page 17
A Billion Bad Twitter Apps......Page 18
The Minimalist Flourish......Page 21
Tearing Down Tweetie......Page 26
Organic Marketing......Page 27
Tweetie 2......Page 31
Market Share......Page 34
Developer Name: Joe Hewitt Development Company: Facebook Tags: Layout; Open Source; Client App URL: http://facebook.com......Page 37
How did you become the sole iPhone developer at Facebook?......Page 38
You also use the top nav in an interesting way in this new version. Is the redesign a consequence of implementing the grid?......Page 39
What went into creating Facebook’s view controllers?......Page 40
When the app gets memory warnings from the OS, how does it deal with them?......Page 41
Otherwise, it all stays cached?......Page 42
As the app grows, how will you handle preferences?......Page 44
Are there interesting ways you use Apple’s frameworks?......Page 45
Why did you choose to make Three20 open source?......Page 46
Part 2: Using App Connectivity with Core Location to Make Games Social......Page 47
Developer Name: Bob Stevenson and Allen Ma Development Company: Ngmoco:) Tags: Release Strategy; Fun; Connectivity; Art URL: htt......Page 49
How to Do a Sequel: Conceptually......Page 50
How to Do a Sequel: Technically......Page 53
Designing Apps (and Companies) for the Mass Market......Page 58
PVRTC-It......Page 59
Fun, the Apple Way......Page 61
Bureaucracy and Lightheartedness......Page 63
Free vs. Paid......Page 64
Developer Name: Dennis Crowley and Naveen Selvadurai Development Company: Foursquare Tags: Visual Design; Connectivity; Client A......Page 67
Is there a governing aesthetic?......Page 68
Did any apps serve as inspiration for Foursquare’s interaction design?......Page 69
You use a lot of Apple’s frameworks. Why not source some of the work out to Apple’s built-in apps?......Page 70
Foursquare seems to rely heavily on WebKit. Why?......Page 71
Certain screens of your app contain “help” text. How do you decide where and when to include those instructions?......Page 72
Do you use any wider system for collecting feedback?......Page 73
Do you take user’s real-world behavior into account when you’re adding features?......Page 74
What were some of the fights you had over user experience?......Page 75
Part 3: Using Compression to Cram More Data into a Local App–Large Images, Geo Data, and Lots of It......Page 77
Developer Name: Dave Witonsky and Randall Barnhart Development Company: Intermap Tags: Compression; Efficient Code; Release Stra......Page 79
Unknown......Page 0
Building a Framework......Page 80
Divide and Conquer......Page 82
Building an In-App Store......Page 84
PVRTC or Broke......Page 86
Lazy Loading......Page 87
Memory Diagnostics: Sample Project......Page 88
Dealing with Low Memory Warnings......Page 90
Building Forward......Page 92
URL: http://exitstrategynyc.com/......Page 95
Why is this idea best suited for the iPhone?......Page 96
How do you handle the database of stops and cars?......Page 97
How do you make your app useful to more people?......Page 98
So the app will become something else entirely—a hyperlocal neighborhood transit map.......Page 100
How deep should you drill into the NYC market before moving on to other cities or projects?......Page 101
Do you have an economic theory behind your pricing?......Page 102
How did you get attention for your app?......Page 103
What’s the most important thing you learned making version 1.0?......Page 104
Part 4: Creating a Beautiful App Without Falling Victim to Memory Issues—OpenGL, Skinning, Object Reuse, and Coding Efficiently......Page 105
Developer Name: Chris Parrish and Brad Ellis Development Company: Rogue Sheep Tags: OpenGL ES; Art; Memory Management; Team Deve......Page 107
There Were Sheep......Page 108
Is This One of Them Internets?......Page 109
Coding for Fun......Page 111
The Circling Shark......Page 114
Homegrown Design......Page 116
Building On Postage......Page 121
Developer Name: Wil Shipley Development Company: Delicious Monster Tags: Client App; Visual Design; Memory Management; Efficient......Page 123
Your plan was to get it looking right first and foremost?......Page 124
So skinning was the healthy medium?......Page 125
How did you achieve that speed?......Page 126
You didn’t, um, RTFM?......Page 127
Were you looking to imitate the desktop experience?......Page 128
Delicious Library overlaps a little with iTunes. How did you deal with that paradigm?......Page 129
What would you tell someone starting app tomorrow?......Page 130
What does it do to the logic of code to be so judicious about memory?......Page 132
Did designing the iPhone app change the way you view desktop UI?......Page 133
Part 5: Fitting a Big Idea into a Small Space......Page 135
Developer Name: Elias Pietilä Development Company: Elias Pietilä Tags: Workflow; Fun; Outdoing Copycats URL: http://qvik.fi/......Page 137
The Dropout......Page 139
The Challenge......Page 141
Building the Labyrinth......Page 143
The “Magic” Piece......Page 144
Into the Fray......Page 145
URL: http://prowl.weks.net/......Page 147
How did you first envision people using Prowl?......Page 148
How do you hack it?......Page 149
What’s particularly interesting about the way Prowl works?......Page 150
When building a utility, do you think about usability differently than you would for another kind of app?......Page 151
What do you know now about working with Growl that you wish you knew at beginning?......Page 152
What about genuinely useful stuff, like the Bluetooth proximity feature you mentioned?......Page 153
How important is Prowl\'s Web interface?......Page 154
How did you arrive at that $2.99 price-point?......Page 155
Is there a lesson to other developers in Prowl?......Page 156
Part 6: Making Better Apps and Enfranchising Your Users......Page 157
URL: http://smule.com......Page 159
Why did you bring your research from computers to the iPhone?......Page 160
Why is the iPhone unique that way?......Page 161
How do Smule apps create music?......Page 163
What did you learn doing laptop orchestras that informed your iPhone app design?......Page 165
How have your apps built on each other?......Page 166
How do you know how difficult to make an instrument?......Page 167
What do you have in mind when you set out to build a new Smule app?......Page 168
Developer Name: Alykhan Jetha and Brandon Walkin Development Company: Marketcircle Tags: Iteration; Client App; Team Development......Page 169
The Canadian Way......Page 170
Simply Complex......Page 172
Group Single-mindedness......Page 176
Reverse Engineering Cocoa......Page 179
The Sidebar Solution......Page 185
Enter the iPhone......Page 188
Project Yellow Canary......Page 191
Developer Name: Marco Arment Development Company: Marco Arment/Tumblr Tags: Release Strategy; App Store; Iteration URL: http://m......Page 195
Are free upgrades a good idea? Or should you make users pay again? Let’s use Exit Strategy NYC, featured in Chapter 6, as an exa......Page 196
What happens when the scope of your app changes with a second version, as with Exit Strategy NYC? Should Jonathan have changed t......Page 197
Do you think buyers have price “benchmarks” that developers should attend to?......Page 198
What is the case to be made for apps over $5.00?......Page 199
Why not go lower?......Page 200
Like a lot of iPhone apps, Instapaper has a desktop version. Should you build an iPhone companion app as a standalone?......Page 201
So you can’t assume your users have self-control?......Page 202
Why didn’t you make Instapaper for iPhone a mobile web site instead of an app?......Page 203
¦ C......Page 205
¦......Page 206
¦ G......Page 207
¦ N......Page 208
¦ R......Page 209
¦ T......Page 210
¦ W......Page 211