Pull to Refresh? How about Smile to Fave: This week, Paul Ford and Rich Ziade discuss the building blocks of software development. Why do apps so often look and behave the same? We break down the tension between working within beautifully designed parameters and the need to innovate. What principles do fast food and software share, and does this have anything to do with why Paul had so much trouble ordering his salad?

►iTunes/►SoundCloud/►Overcast/►Stitcher/►MP3 /►RSS

Paul — 2:55: “This is the thing that people don’t know. When you come to us and say ‘write me an app,’ you’re asking us to write as little code as possible. That’s in your best interest.”

Paul — 5:05: “Why do apps look the same? Why do they behave the same? […] It’s because everyone is using the same libraries. It’s really tricky, right, because you’d think if you want to innovate, you’d want to break out of that.”

Paul — 5:45: “This is the great tension in our industry, because you want to innovate and you want to blow everything up, but the cost to do so is unbelievably high. […] I could go to the store, I could buy food, and I could cook from a recipe, or I could grow my own wheat.”

Rich — 9:55: “We’re talking about how these libraries are great for engineers because they get to skip. It’s great for users because the patterns and the gestures become common and becomes so much easier to pick up another app.”

Rich — 10:50: “Isn’t this the model behind fast food? It’s good because it has fat and sugar in it, but consistency is huge. Like people who go on vacations go to McDonalds because they know what they’re going to get.”

Paul — 15:50: “Design — brand focused design and the traditional qualities of design — were always about having a specific kind of voice. Like the work that Paul Rand does, or the work they do down the street at Pentagram. […] I recognize this, it feels familiar, it works within a set of parameters, but it’s original too.”

Paul — 16:10: “There’s a huge tension in technology where [you have to] follow the rules of the SDK, follow the Human Interface Guidelines and make it looks exactly like the other apps […] or you’ll lose the user.”

Rich — 19:35: “Credit to Adobe for giving every single engineer that worked on Photoshop props when you load it. The problem is that it zips by at 180mph.”

Paul — 20:00: “If Adobe Photoshop worked like Mac apps typically worked, it would be a lot easier to learn and adapt to. But it would also be less differentiated and it’s Photoshop and it’s Adobe so it has its own thing going.”

LINKS

• Software Development Kit
• Web Framework
• Creating a Chicken Sandwich From Scratch
• Microsoft Visual Studio
• Why We Fail: A Conversation with Victor Lombardi
• Pull-to-refresh
• Apple’s Human Interface Guidelines
• Google’s Material Design

Track Changes is the weekly technology and culture podcast from Postlight, hosted by Paul Ford and Rich Ziade. Production, show notes and transcripts by EDITAUDIO. Podcast logo and design by Will Denton of Postlight.

 

See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.